4 ms·
I (my company) use a similar approach: a single dedicated server with docker containers, by using dokku [0], for an heroku-like self-hosted PaaS. Most of our a
by throwaway744678 5y ago
I (my company) use a similar approach: a single dedicated server with docker containers, by using dokku [0], for an heroku-like self-hosted PaaS.
Most of our applications are either:
- app developped in-house (django/flask): Procfile + deploy with git push
- standard app with a docker image available: deploy directly
Dokku comes with useful "service" plugins for databases, auto https (letsencrypt), virtual hosts... Overall, a good experience.
[0] https://dokku.com/ https://dokku.com/
- password4321 5y agoPardon my curiosity, but do you pay for Dokku Pro?
- throwaway744678 5y agoI do not.
- throwaway77384 5y ago+1 for Dokku here. Been running 10 containers on the second-cheapest Hetzner instance available for years now. Never had any issues. My only, tiny gripe would be excessive space consumption on the somewhat small 20gb SSDs you get with Hetzner VPSs.
- jakswa 5y agoMy only, tiny gripe would be excessive space consumption on the somewhat small 20gb SSDs you get with Hetzner VPSs. I was trying to imagine the reason for this. Is it that dokku is similar to heroku, and does a build step upon git-push-to-deploy? So assets/compilation/etc have artifacts and a cache that sticks around to help speed up future pushes/builds?
- conradfr 5y agoSame here (not a company but some paying users) but with CapRover. Multiple webapps (Symfony, Phoenix, Magento) on a 20€/m OneProvider server. Databases backups are done by a cron bash script which uploads to a ftp. It works fine, only real downside for my use case is the small downtime after a deploy. I probably would use something else for a frequently deployed pro webapp.