Open angelocordon opened 6 years ago
Have you used Vagrant before? If not, I'd prefer docker because I have used it already. It might be quite a challenge to get postgres setup in a container so the installation required for a new user is as minimal as possible, but it would really be good. I'm all for doing as much as possible via containers.
I'd like to experiment with how that goes with docker. Maybe we can work on that together some time, I'll probably be totally lost without help there :grin:
Ha yeah same here :D
I'm currently using Vagrant + Docker in some projects (though I didn't implement it myself). I know a little bit but would need some serious research. The reason why Vagrant + Docker is that synching files from OSX to Docker isn't fast enough but synching to Vagrant + Docker cuts down on the sync time.
Definitely open to ideas here though.
I don't think there's a reason we need both, docker works fine on my mac for the big projects we work on. It's just in extreme cases I think.
Some users might not have the prerequisite tools needed to get up and going with this project. For example, installing and getting up and running ruby, rails and postgres could potentially be a roadblock for new developers. (Note: there is http://installrails.com/)
Perhaps, we can containerize the project (Vagrant, Docker or both?) we can set up a .bin/setup script to help devs get up and running quickly and easily.
I.e.: running
./bin/setup
could launch Vagrant with hook scripts that installs the project in a VM along with necessary tools and libraries or runningvagrant up
can launch the project simply.