I just want to test this feature and see what it takes to get it working specifically for nodeJS web repls to see if Replit Deployments are a viable option for hosting my various low traffic nodejs APIs.
After a bit of work (and 15 failed deployments), I got the repl to deploy with a success.
However, the routing server on the deployment does not seem to work.
Frankly, I have no idea, I don’t know how deployments work at all really. My best guess would be maybe if your using like 4 vCPUs for example, it might create four ‘virtual machines’… But I’m just grasping at straws here and I really have no idea (the team may be able to clarify that too).
4 vCPUs would still run on 1 VM otherwise the service wouldn’t be able to intercommunicate between threads to take advantage of the multithreading. Also I’m using 0.5vCPU (shared CPU) so that def shouldn’t be a problem.
Looking forward to the team’s response. Seems like they may be the only ones who can shed light on what the heck’s going on and what more I have to do to give them more of my money XD
All traffic to your Deployment (and Repls in the Workspace work this same way) will be plain HTTP, regardless of which port it comes in on. We handle the HTTPS aspect of it with our reverse proxies and then forward just the plain HTTP requests to your server.
Glad it works now! If you don’t mind, go ahead and accept the answer so the topic will auto-close.