# Docker readme
* fixes typo * adds more info
This commit is contained in:
parent
44033c18fe
commit
9ea47fcc83
13
README.md
13
README.md
@ -59,7 +59,18 @@ container, which wants to write/read on this database**.
|
|||||||
6. Build and run the docker setup using `docker-compose build` and `docker-compose start` from the main directory of this project (where the docker-compose.yml lives)
|
6. Build and run the docker setup using `docker-compose build` and `docker-compose start` from the main directory of this project (where the docker-compose.yml lives)
|
||||||
7. Run migrations! To do so, get into the konova service container (`docker exec -it konova-docker bash`) and run the needed commands (`python manage.py makemigrations LIST_OF_ALL_MIGRATABLE_APPS`, then `python manage.py migrate`)
|
7. Run migrations! To do so, get into the konova service container (`docker exec -it konova-docker bash`) and run the needed commands (`python manage.py makemigrations LIST_OF_ALL_MIGRATABLE_APPS`, then `python manage.py migrate`)
|
||||||
8. Run the setup command `python manage.py setup` and follow the instructions on the CLI
|
8. Run the setup command `python manage.py setup` and follow the instructions on the CLI
|
||||||
9. To enable **SMTP** mail support, make sure your host machine (the one where the docker container run) has the postfix service configured properly. Make sure the `mynetworks` variable is extending using the docker network bridge ip, created in the postgis container and used by the konova services.
|
9. To enable **SMTP** mail support, make sure your host machine (the one where the docker container run) has the postfix service configured properly. Make sure the `mynetworks` variable is xtended using the docker network bridge ip, created in the postgis container and used by the konova services.
|
||||||
1. **Hint**: You can find out this easily by trying to perform a test mail in the running konova web application (which will fail, of course). Then take a look to the latest entries in `/var/log/mail.log` on your host machine. The failed IP will be displayed there.
|
1. **Hint**: You can find out this easily by trying to perform a test mail in the running konova web application (which will fail, of course). Then take a look to the latest entries in `/var/log/mail.log` on your host machine. The failed IP will be displayed there.
|
||||||
2. **Please note**: This installation guide is based on SMTP using postfix!
|
2. **Please note**: This installation guide is based on SMTP using postfix!
|
||||||
3. Restart the postfix service on your host machine to reload the new configuration (`service postfix restart`)
|
3. Restart the postfix service on your host machine to reload the new configuration (`service postfix restart`)
|
||||||
|
10. Finally, make sure your host machine webserver passes incoming requests properly to the docker nginx webserver of konova. A proper nginx config for the host machine may look like this:
|
||||||
|
```
|
||||||
|
server {
|
||||||
|
server_name konova.domain.org;
|
||||||
|
|
||||||
|
location / {
|
||||||
|
proxy_pass http://localhost:KONOVA_NGINX_DOCKER_PORT/;
|
||||||
|
proxy_set_header Host $host;
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
Loading…
Reference in New Issue
Block a user