4 ms·

If you are building a PHP/MySQL app, I'm not sure that I would start with docker. Actually, I know I wouldn't start with docker. Very few apps will ever get to

If you are building a PHP/MySQL app, I'm not sure that I would start with docker. Actually, I know I wouldn't start with docker. Very few apps will ever get to the point where they have millions of users, and even fewer will need to use docker to orchestrate what should amount to < 5 servers (1 proxy, 2 web fronts, 1 cache, 1 db) to start to handle that kind of load. Once you are at that kind of scale, where you are handling 5+ containers/machines, then it might make sense to look at docker, chef, puppet, etc... but for the rest of us, starting with docker feels like premature optimization for scale that will likely never happen. The only sensible part of docker at small scale is if you are inside a larger org and you are deploying a lot of apps and you are using docker to simplify deployment (sort of like WAR files in javaland...sort of), but even then for php/mysql a git checkout or rsync works like a champ.

ponyous 12y ago
Docker is not only useful for scaling problems, but also for another reasons such as sharing development environment.
- programminggeek 12y ago
  Why not use Vagrant for that?
aemadrid 12y ago
The point of docker here is to make your dev environment the same as your production env as much as possible. If you develop on osx and deploy to linux sooner rather than later you will get bitten by env differences.
- larrybolt 12y ago
  The biggest advantage of docker I've seen so far is Dokku [1]. If I want to get a dev-instance up and running to show to coworkers (or the client) I just can do "git remote add dokku dokku@example.com && git push dokku master" and share the link with them. And with very little modifications the same can be deployed at Heroku (though I don't use heroku personally). And if you follow the dokku instructions it's fairly easy to setup, while doing something similar without Dokku but nginx/apache+php/passenger would take a fair amount of time to setup and config to run like that. [1] https://github.com/progrium/dokku https://github.com/progrium/dokku
gizzlon 12y ago
I'm starting a smallish project, using Docker, for two reasons: - It helps containing all the dependences on my laptop and on the server, to not "pollute" it with things I won't need later. - It makes it easier to move the whole system around, from my laptop to the cloud.. and to another cloud, etc. Docker adds complexity as well, so I don't yet know if it's worth it.

ponyous 12y ago

Docker is not only useful for scaling problems, but also for another reasons such as sharing development environment.

programminggeek 12y ago
Why not use Vagrant for that?

aemadrid 12y ago

The point of docker here is to make your dev environment the same as your production env as much as possible. If you develop on osx and deploy to linux sooner rather than later you will get bitten by env differences.

larrybolt 12y ago
The biggest advantage of docker I've seen so far is Dokku [1]. If I want to get a dev-instance up and running to show to coworkers (or the client) I just can do "git remote add dokku dokku@example.com && git push dokku master" and share the link with them. And with very little modifications the same can be deployed at Heroku (though I don't use heroku personally). And if you follow the dokku instructions it's fairly easy to setup, while doing something similar without Dokku but nginx/apache+php/passenger would take a fair amount of time to setup and config to run like that. [1] https://github.com/progrium/dokku https://github.com/progrium/dokku

gizzlon 12y ago

I'm starting a smallish project, using Docker, for two reasons: - It helps containing all the dependences on my laptop and on the server, to not "pollute" it with things I won't need later. - It makes it easier to move the whole system around, from my laptop to the cloud.. and to another cloud, etc. Docker adds complexity as well, so I don't yet know if it's worth it.