I'm coordinating the development of Quill.org, a web app that provides writing activities to students.<p>We are an active open source project, and we've had over 40 people contribute. We recently moved to Docker to make it easier for new developers to get set up. However, the Docker environment is proving to be problematic, and developers are having a hard time getting the code set up. I'm reaching out to you on HN to get your thoughts on what our install process ought to be.<p>You can get a good sense our code here:<p>https://github.com/empirical-org/Documentation/blob/master/Getting-Started/README.md<p>Here are the questions we are currently facing:<p>1) Is it going to be difficult to maintain Docker? My concern is that we'll need to spend a lot of time re-configuring Docker as the project changes. I'm not sure whether we should stick with Docker for install or simply use it for production.<p>2) Would it be better to simply use a manual install process with Foreman? We were using a manual install process before, and this is where a number of problems sprung up. Our project is somewhat complex, utilizing a SOA with multiple databases and an API. I'm not sure whether it'd be best to stick with the Docker install, or whether we should return to the manual install.<p>3) We could move back to Vagrant for the install process. Would this be the best course of action? We used Vagrant in the past, but the instructions became out of date, and it was dropped.<p>We are trying to bring on board new developers, and we are running into a number of issues. I'd really appreciate your thoughts on how we ought to proceed.