- It configures the base path (`nomad-oasis`) at multiple places. It needs to be changed, if you use a different base path.
- You can use the server to server additional content if you like.
-`client_max_body_size` sets a limit to the possible upload size.
- If you operate the GUI container behind another proxy, keep in mind that your proxy should not buffer requests/responses to allow streaming of large requests/responses for `../api/uploads` and `../api/raw`.
## Starting and stopping
If you prepared the above files, simply use the usual `docker-compose` commands to start everything.
In the beginning and for debugging problems, it is recommended to start services separately:
```
docker-compose up -d mongodb elastic rabbitmq
docker-compose up app worker gui
```
The `-d` option runs container in the background as *daemons*. Later you can run all at once:
```
docker-compose up -d
```
You can also use docker to stop and remove faulty containers that run as *daemons*:
```
docker stop nomad_oasis_app
docker rm nomad_oasis_app
```
If everything works, the gui should be available under:
```
http://<your host>/nomad-oasis/gui/
```
If you run into troubles, use the dev-tools of you browser to check the javascript logs
or monitor the network traffic for HTTP 500/400/404/401 responses.
To see if at least the api works, check
```
http://<your host>/nomad-oasis/alive
http://<your host>/nomad-oasis/api/info
```
To see logs or 'go into' a running container, you can access the individual containers
with their names and the usual docker commands:
```
docker logs nomad_oasis_app
```
```
docker exec -ti nomad_oasis_app /bin/bash
```
If you want to report problems with your OASIS. Please provide the logs for
