Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker/compose/split/db/docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ services:
ports:
- "127.0.0.1:6379:6379"
volumes:
- ./../../../../../../data:/data
- ./../../../../../../data/redis:/data
blazegraph:
build:
args:
Expand Down
12 changes: 12 additions & 0 deletions docs/docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,8 @@ The monolithic image was split into images for the databases Whyis relies on (_r
#### Prerequisites
* Docker
* `docker-compose`
* A data folder alongside your `/apps` folder is in with permissions 777
* See other notes

### Use

Expand All @@ -102,6 +104,16 @@ Further, `docker/compose/split/app-dev` references a version of `whyis-server` t

## Other notes

### Data directory

By default, the split `docker-compose.yml` will mount a directory named `data` in the same directory as your `/apps` folder on the host machine. Due to how Docker allocates volumes, this folder will have the wrong permissions and cause Blazegraph to fail on the first setup. To avoid this, run the following instructions before running `docker-compose`:

cd /
mkdir data
chmod ugo+rwx data

You should then be able to start and stop the containers without further permission issues.

### Whyis image tags

By default the `docker-compose.yml` use `latest` tags for the whyis images. This can be overriden by specifying the environment variable `WHYIS_IMAGE_TAG`.