- Clarify that setting `entrypoint` overrides both the entrypoint and
the command on the image
- Fix the incorrect examples in the doc on startup order, which assumed
that the default command would not be overridden
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
Constraints for Swarm scheduling are defined as an **environment** option, according to the example in the section *Manual scheduling*, and not as a **label** option
* Update to Rails 5, Ruby 2.3.3, remove therubyracer
Update packages to latest versions. The actual nodejs is installed on line 18. Changed to a general comment regarding the need to rebuild images when adding gems.
* update rails welcome screenshot to 5.0.0.1
In this example, database.yml uses the default value of `postgres` for the `database` key.
The database postgres is normally not used for user data, but for administrative purposes. This means people following this example will not be able to drop the database, and in general it's just not a great idea.
- Some wording and formatting tweaks
- Use Python 3.4, because it's 2016
- Use Alpine-based images for faster downloads and less disk space usage
- Use the list form of `CMD` in the Dockerfile, so it's not wrapped in
sh
- Remove the `depends_on` from `docker-compose.yml`, as it's not really
needed - the web app connects to Redis when it's visited, not on
startup
- Add a section on updating the app and seeing the changes, because
that's the point of mounting the code in!
- Add a note about `docker-compose down`
Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
added more changes
updated per Nathan's comments on properly documenting directories formats for all platforms
incorporated Daniel's review comments, and added a clarification re: users' dir
copyedits
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
Update the compose example:
* Remove the `links` directive. This allows swarm to distribute containers across available nodes. (with the `links` directive, swarm will be forced to run both containers on the same node.) Note that the `depends_on` directive is sufficient to ensure correct container start up sequence.
* Use a docker volume instead of bind mounting a local directory.
* Give docker-compose commands for shutting down the Wordpress app, showing how to preserve or remove the persisted data in the volume.
Verified proposed change works correctly in both a swarm and a non-swarm environment.
