10 Replies
You want to host a deno app on premisis? Or you want to open a Deno hosting provider?
Unknown UserOP•3y ago
Message Not Public
Sign In & Join Server To View
@smail4080 I think he meant something similar to cPanel but for Deno...
You could also rent a VPS and set up everything on your own, @Charledeon
Unknown UserOP•3y ago
Message Not Public
Sign In & Join Server To View
deno can be self hosted
Unknown UserOP•3y ago
Message Not Public
Sign In & Join Server To View
@Charledeon did you even read my message? ^
That's how a lot of people do it
Unknown UserOP•3y ago
Message Not Public
Sign In & Join Server To View
One Month of VPS Server, is the equivalent of what I will pay for One Year of WordPress Hostingthat's just bs there's a ton of good hosting providers out there that offer affordable prices plus it's definitely cheaper in comparison for what you get with a wordpress hosting package
I think I see a misunderstanding in this thread about what shared hosting is and how Deno fits into a stack. Shared hosting/Wordpress hosting is where your provider runs a web server (Apache/nginx/the thing that knows how to speak HTTP) and you get to upload some files and scripts to be executed by that server if it receives a request. It’s “shared” because lots of other customers have files and scripts being served by the same server. You don’t get even a single long-running POSIX process to yourself. Same with the database—your db is just one of many hosted on the same database server with other customers.
Shared hosting only really works with languages like PHP which are run by a separate web server that you have no control over besides what the provider lets you configure via cpanel.
When you run a Deno HTTP server, your application IS a long-running process which speaks HTTP, just like Apache or Nginx! So you need a platform that will let you run a long-running process, like a VPS or Digital Ocean droplet or container runtime like Docker or Kubernetes. You trade simplicity and constraints for complexity and flexibility. Also since you are using more server resources, the cost is greater than shared hosting.
“Serverless” means deploying code like node.js or Deno in a way that the platform starts up a new process for every request and the process shuts down immediately after the request is satisfied. You only pay for resources used to serve each request, instead of for a long-running process, so it’s cheap again.
Deno Deploy is the simple and cheap solution for Deno serverless edge functions. Is it Ready for Business? Well, it’s being used by Slack and Netlify and Supabase. But it’s also in beta. So, it depends on your business and your risk tolerance.
Also cheap, but slightly less simple would be a container-based serverless platform, which just starts up a container for each request. You would package your Deno app into a container image and ship that to the platform. I think there are some AWS and GCP services that can do this.
Another option I’ve learned about in a similar vein would be controlplane.com, which deploys containers and supports dynamic scaling to zero. So again, you’re only paying for the resources that you use. But the tradeoff is that you have to learn how to package your Deno app into a container image. If you don’t want that overhead, then Deno Deploy is your simplest solution.
But remember that in all of these, the platform provider is NOT running a web server for you like the shared hosters do with Apache. They’re providing a process runtime, and you’re running the web server (that speaks HTTP, or perhaps even WebSockets) inside your container. (Yes I know there is SSL termination and reverse proxying, but that’s not germane.)