11–20 of 29 posts
It looks like you're going to eventually build a company around this and maybe you will think about releasing the source then? In which case, the title is still misleading.
I do appreciate that you've released documentation ahead of the product, it does indicate that you understand how important that aspect of the business will be.
How is it different than Dokku?
See also: CapRover. Beats dokku all to hell, in my experience. https://github.com/caprover/caprover Be careful, their (CapRover) embedded NetData image has the NetData upstream defaults for spyware, so you are advised not to enable it (use of their embedded NetData is optional). https://github.com/caprover/caprover/issues/553 It is straightforward to set up CapRover with an ssh deploy key and a webhook for deploying…
In the meantime, if you want something that is simple enough that you can read the entire code base in one sitting, check out Piku:
How is it different than Dokku?
Perhaps to answer the question, one might ask: How is Heroku different from Dokku?
Heroku is easy, but expensive. Dokku is more work/management, but cost-effective.
Convox's business model is selling you the managed version of their open source rack. We've been using Convox in production for over 3 years now and we've had pretty good success with it. It's not perfect but the UX improvement for developers when building docker images, promoting new builds or rolling back cannot be understated.
Remind101 has built Empire[2] which is not a product they actually sell but rather the tool they use internally and have decided to open-source it. Empire is a little less managed and while it allows you to run services on it it requires you to have your own solution for building and hosting docker images.
See also: CapRover. Beats dokku all to hell, in my experience. https://github.com/caprover/caprover Be careful, their (CapRover) embedded NetData image has the NetData upstream defaults for spyware, so you are advised not to enable it (use of their embedded NetData is optional). https://github.com/caprover/caprover/issues/553 It is straightforward to set up CapRover with an ssh deploy key and a webhook for deploying…
The github issue you linked to and the discussion it contains is the reason I am sticking with dokku. The CapRover maintainer seems to argue in bad faith and not have the users best interest at heart.
And dokku works well for my use cases.