-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Other]: Self-hosting Shuttle on own server or own cloud #1584
Comments
Heroku/ Dokku-style deployment of Rust Web apps would definitely be a game-changer, as currently, it involves a lot of manual work, even cross-linking of the binary to use in a docker container in some cases. Having a PaaS-Tool like Shuttle to self-host (cases 2 and 3 mentioned above) and quickly deploy and update Rust apps would thus be very nice. I understand this would potentially be orthogonal to your business interests at the moment though. |
True. This is why I’m a proponent of the source-available Polyform NonCommercial license for this kind of work, since it resolves the disincentive that otherwise prevents the work from being shared at all. It helps proprietary layers go from closed to minimally open. For some similar prior art, see https://element.io/blog/element-starter-open-source-meets-on-premise-collaboration/ |
"Self-hosting" Shuttle is a common question we get, and it has many interpretations:
cargo shuttle run --release --external
with Docker integration for databases is currently possible and might be enough for some.Related: #976 (comment)
This issue is a part of the Product Feature Poll (all issues). React with 👍 if you want this feature. Comment if you have suggestions related to this feature.
The text was updated successfully, but these errors were encountered: