- Change the default admin password. Login as `plop@plop.com`, password `1234`
and go to <https://your-hostname/vidjil/default/user/change_password>
- Change the ssl certificates. When building the image vidjil-server
which creates a self-signed certificate for the sake of convenience to
ensure the HTTPS queries work from the start, but this may not be
acceptable for a production environment.
In order to replace certificates the current method is to mount the
certificates to /etc/nginx/ssl with docker volumes in
docker-compose.yml.
certificates to `/etc/nginx/ssl` with docker volumes in
`docker-compose.yml`.
- Change the FROM<sub>EMAIL</sub> and ADMIN<sub>EMAILS</sub> variables in conf/defs.py. These
- Change the `FROM_EMAIL` and `ADMIN_EMAILS` variables in `conf/defs.py`. These
represent the sender email address and the destination email addresses,
used in reporting patient milestones and server errors.
- Change the database password. In the mysql directory you will find an
- Change the database password. In the `mysql` directory you will find an
entrypoint script which creates the database, the user and set that
user's password.
This is the password you need to match in the defs.py file in the
vidjil configuration.
This is the password you need to match in `defs.py`.
- Change the volumes in docker-compose.yml. By default all files that
- Change the volumes in `docker-compose.yml`. By default all files that
require saving outside of the containers (the database, uploads, vidjil
results and log files) are stored in /opt/vidjil, but you can change
results and log files) are stored in `/opt/vidjil`, but you can change
this by editing the paths in the volumes.
- Configure the reporter. Ideally this container should be positioned
...
...
@@ -194,13 +191,16 @@ Here are some notable configuration changes you should consider:
### Starting the environment
Ensure your docker-compose.yml contains the correct reference to the
vidjil image you want to use. Usually this will be vidjil/vidjil:latest,
Ensure your `docker-compose.yml` contains the correct reference to the
vidjil image you want to use. Usually this will be `vidjil/vidjil:latest`,
but more tags are available at <https://hub.docker.com/r/vidjil/vidjil/tags/>.
You may also want to uncomment the volume in the fuse volume block "-
./vidjil/conf:/etc/vidjil" this will provide easier access to all of the
configuration files, allowing for tweaks. From this location, it will be easier to enable more softwaer or pipelines by putting the binary in this location taht will be see by the docker instance.
You may also want to uncomment the volume in the fuse volume block
`./vidjil/conf:/etc/vidjil`.
This will provide easier access to all of the
configuration files, allowing for tweaks.
From this location, it will be easier to enable more software or pipelines
by putting their binaries in this location taht will be see by the docker instance.
Running the following command will automatically download any missing
images and start the environment:
...
...
@@ -237,6 +237,10 @@ If needed, the MYSQL database will be updated to match the newest format.
this step is automaticly done by web2py.
XXX TODO XXX (****demande confirmation par test****)
# Plain server installation
## Requirements
``` bash
...
...
@@ -252,7 +256,7 @@ pip install enum34
pip install ijson cffi
```
## Vidjil server installation and initialization
## Server installation and initialization
Enter in the `server/` directory.
...
...
@@ -260,8 +264,6 @@ If you just want to do some tests without installing a real web server,
then launch `make install_web2py_standalone`. In the other case, launch
`make install_web2py`.
The process for installing Vidjil server together with a real web server
will be detailed in the future.
## Detailed manual server installation and browser linking
