Same server deployment: put code editor and deployment together

Feature Requests
1

A type of deployment that uses the same server as the code editor. The old hosting was like this.
Why add it:

  • Only one instance of the server
  • Can update files faster and file persistence
  • Some apps can only use the file system
  • Useful for using the console of the server when deployed
  • Easier to deploy some existing apps
2

Basically, a new type of deployment, where the server in the deployment is the same server in the development environment.

1server
1server800×400 18.3 KB

One way to add it: When there are requests at this type of deployment and the server is not running, boot and run the server (similar to opening the development environment and clicking run). Route the requests to the server’s port.

3

Hey, that’s how the old “always on” repls worked but we deprecated that. It’s extremely dangerous to let the Agent work against the production filesystem and code. That’s why we do the separate deployment container that snapshots your current code and moves it to a different machine for production deployment.

You can do this by deploying through something like Digital Ocean or an EC2 instance and ssh-ing into the box.

4

Alternatively you can separate out and deploy just the backend server, then have a different repl where you’re doing the client code that’s hitting against the production backend even in dev.