5 ms·
Yeah, what Solomon said. For the moment, Dokku is focusing on the same sort of stateless apps Heroku supports and considers running databases a separate concern
by progrium 13y ago
Yeah, what Solomon said. For the moment, Dokku is focusing on the same sort of stateless apps Heroku supports and considers running databases a separate concern. For now you can run your databases, etc on the same host, in Docker containers, somewhere else, just out of band from Dokku.
But I'd love to hear your thoughts on how Dokku could better support datastores.
- shykes 13y agoI think it would be really cool to have Dokku "add-ons" which behind the scenes map to the docker containers of your choice :)
- progrium 13y agoYes. :) That and more are some exciting things on my mind.
- thelarry 13y agoIsn't running a database in a container sort of bad practice? Especially if it does a lot of io
- shykes 13y agoNo. In terms of io and other kinds of overhead, you are always better off running your database on a container rather than a VM. The majority of public cloud database services are either running inside containers, or in the process of migrating to containers. An additional advantage of containers is that you can start running them on top of a VM, and then migrate to bare metal later, as your infrastructure requirements evolve.
- thelarry 13y agoI think in my head I had container ON A VM. Which just inherits the problem of running it on a VM. Is there a good linux tool for limiting the IO of a process or user?
- wmf 13y agoNetworking uses tc and disk uses the block I/O controller. https://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt https://www.kernel.org/doc/Documentation/cgroups/blkio-contr...