1 # Using Docker and Docker Compose for Development and Testing
3 These instructions are designed for setting up `openstreetmap-website` for development and testing using [Docker](https://www.docker.com/). This will allow you to install the OpenStreetMap application and all its dependencies in Docker images and then run them in containers, almost with a single command.
9 1. Use Docker Desktop via [docker.com Download](https://www.docker.com/products/docker-desktop/).
11 2. You have to enable git symlinks before cloning the repository.
12 This repository uses symbolic links that are not enabled by default on Windows git. To enable them, [turn on Developer Mode](https://windowsreport.com/windows-11-developer-mode/) on Windows and run `git config --global core.symlinks true` to enable symlinks in Git. See [this StackOverflow question](https://stackoverflow.com/questions/5917249/git-symbolic-links-in-windows) for more information.
16 - Use Docker Desktop via [docker.com Download](https://www.docker.com/products/docker-desktop/).
17 - Or [Homebrew](https://formulae.brew.sh/cask/docker).
21 Use [Docker Engine](https://docs.docker.com/engine/install/ubuntu/) with the [docker-compose-plugin](https://docs.docker.com/compose/install/linux/)
25 The first step is to fork/clone the repo to your local machine:
28 git clone https://github.com/openstreetmap/openstreetmap-website.git
31 Now change working directory to the `openstreetmap-website`:
34 cd openstreetmap-website
42 cp config/example.storage.yml config/storage.yml
48 cp config/docker.database.yml config/database.yml
51 ## Prepare local settings file
53 This is a workaround. [See issues/2185 for details](https://github.com/openstreetmap/openstreetmap-website/issues/2185#issuecomment-508676026).
56 touch config/settings.local.yml
59 **Windows users:** `touch` is not an available command in Windows so just create a `settings.local.yml` file in the `config` directory, or if you have WSL you can run `wsl touch config/settings.local.yml`.
63 To build local Docker images run from the root directory of the repository:
69 If this is your first time running or you have removed cache this will take some time to complete. Once the Docker images have finished building you can launch the images as containers.
71 To launch the app run:
77 This will launch one Docker container for each 'service' specified in `docker-compose.yml` and run them in the background. There are two options for inspecting the logs of these running containers:
79 - You can tail logs of a running container with a command like this: `docker compose logs -f web` or `docker compose logs -f db`.
80 - Instead of running the containers in the background with the `-d` flag, you can launch the containers in the foreground with `docker compose up`. The downside of this is that the logs of all the 'services' defined in `docker-compose.yml` will be intermingled. If you don't want this you can mix and match - for example, you can run the database in background with `docker compose up -d db` and then run the Rails app in the foreground via `docker compose up web`.
84 Run the Rails database migrations:
87 docker compose run --rm web bundle exec rails db:migrate
92 Prepare the test database:
95 docker compose run --rm web bundle exec rails db:test:prepare
101 docker compose run --rm web bundle exec rails test:all
105 > If you encounter errors about missing assets, ensure your asset pipeline is correctly configured for your environment.
107 > In production, assets must be precompiled for better performance:
110 > docker compose run --rm web bundle exec rake assets:precompile
113 >In development, missing assets usually indicate a configuration or dependency issue.
114 > Precompiling assets in *development* will disable dynamic compilation and make debugging harder due to fingerprinted assets.
115 > To clean the assets you can run:
118 > docker compose run --rm web bundle exec rake assets:clobber
121 ### Loading an OSM extract
123 This installation comes with no geographic data loaded. You can either create new data using one of the editors (Potlatch 2, iD, JOSM etc) or by loading an OSM extract. Here an example for loading an OSM extract into your Docker-based OSM instance.
125 For example, let's download the District of Columbia from Geofabrik or [any other region](https://download.geofabrik.de):
128 wget https://download.geofabrik.de/north-america/us/district-of-columbia-latest.osm.pbf
131 You can now use Docker to load this extract into your local Docker-based OSM instance:
134 docker compose run --rm web osmosis \
136 --read-pbf district-of-columbia-latest.osm.pbf \
140 database="openstreetmap" \
141 user="openstreetmap" \
142 validateSchemaVersion="no"
145 **Windows users:** Powershell uses `` ` `` and CMD uses `^` at the end of each line, e.g.:
148 docker compose run --rm web osmosis `
150 --read-pbf district-of-columbia-latest.osm.pbf `
154 database="openstreetmap" `
155 user="openstreetmap" `
156 validateSchemaVersion="no"
159 Once you have data loaded for Washington, DC you should be able to navigate to [`http://localhost:3000/#map=12/38.8938/-77.0146`](http://localhost:3000/#map=12/38.8938/-77.0146) to begin working with your local instance.
161 ### Additional Configuration
163 See [`CONFIGURE.md`](CONFIGURE.md) for information on how to manage users and enable OAuth for iD, JOSM etc.
167 If you want to get into a web container and run specific commands you can fire up a throwaway container to run bash in via:
170 docker compose run --rm web bash
173 Alternatively, if you want to use the already-running `web` container then you can `exec` into it via:
176 docker compose exec web bash
179 Similarly, if you want to `exec` in the db container use:
182 docker compose exec db bash