You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,20 +29,39 @@ chmod g+rX -R /path/to/data
29
29
Now you can start the docker compose stack:
30
30
31
31
```bash
32
-
docker compose up -d
32
+
# This will build images and enable docker compose watch (see docker-compose.override.yml instructions below.)
33
+
docker compose up -d --build --watch
33
34
```
34
35
35
36
When the `colocus-django` container starts, it will begin applying django migrations and then load the data located at the `DATA_PATH` specified in your `.env` file.
36
37
37
38
In the future, if you wish to start over and load a new dataset, do the following:
38
39
39
40
```bash
41
+
# If loading data from a new path:
42
+
# Change your `DATA_PATH` in your `.env` file to match the location of your dataset
43
+
# Then restart to force docker to remount DATA_PATH inside the container
44
+
# It's best to recreate the container and build so that your new migrations are included (if any)
45
+
docker compose up -d --build --force-recreate django
46
+
47
+
# If you're just reloading an existing dataset in the same DATA_PATH as before, you can start here:
40
48
docker compose exec db bash -c 'psql -U colocus -c "DROP DATABASE core WITH (FORCE)"'
41
49
docker compose exec db bash /docker-entrypoint-initdb.d/init-db.sh
While developing you may want the containers to rebuild or resync with your source files changing automatically. The following can be placed in a `docker-compose.override.yml` file:
0 commit comments