For production environments it is recommended to activate and secure the Docker HTTP API. You can read more [here](https://gitlab.ub.uni-bielefeld.de/sfb1288inf/opaque_daemon).
For production environments it is recommended to activate and secure the Docker HTTP API. You can read more [here](https://gitlab.ub.uni-bielefeld.de/sfb1288inf/opaque_daemon).
``` bash
``` bash
$ mkdir logs
mkdir logs
$ cp nopaque.env.tpl nopaque.env
cp nopaque.env.tpl nopaque.env
$ <YOUR EDITOR> nopaque.env # Fill out the empty variables within this file.
<YOUR EDITOR> nopaque.env # Fill out the empty variables within this file. For the gitlab login either use your credentials (not recommended) Or create a gitlab token
```
```
5.**Start your instance**
5. Further development instructions
Use the following command to allow docker to pull images from your gitlab registry. TODO: Check if this could also work wit a token?
```bash
docker login gitlab.ub.uni-bielefeld.de:4567
```
6.**Start your instance**
``` bash
``` bash
# Execute the following 3 steps only on first startup
# Execute the following 3 steps only on first startup
$ docker-compose run web flask db upgrade
docker-compose run web flask db upgrade
$ docker-compose run web flask insert-initial-database-entries
docker-compose run web flask insert-initial-database-entries