4 ms·
Looks interesting. What are your plans for the backend - will self-hosting be an option? Right now this looks fine for a hobby project, but massive lock-in/ris
by e12e 3y ago
Looks interesting. What are your plans for the backend - will self-hosting be an option?
Right now this looks fine for a hobby project, but massive lock-in/risk for production (what if you shut down, get bought up etc?).
- dillonnys 3y agoGreat points. My immediate plan for reducing lock-in is to provide the option to deploy into a cloud account you manage. This has the upside of making your deployed infrastructure independent of Celest and letting you use your cloud credits. Self-hosting is another option I'm considering, but I don't have a good sense yet of what that could look like. Any thoughts? Is spitting out a binary/Dockerfile sufficient to alleviate risk? If I get shut down, I'll be open-sourcing all my code. And regardless, I plan to open source more and more of the platform over time.
- marcglasberg 3y agoCommitting to open-source the code (and provide detailed instructions on how to run the code) in case the company shuts down is the most important. It could be part of the service contract. I've read all parts of the Celest code which are public, and I can attest it's very well-written and easy to understand.
- dillonnys 3y ago> It could be part of the service contract. Agreed. I'll look into how we can add that.
- deleted 3y ago[deleted]