If a valid database is not found, `rake db:setup` is run inside the container to set-up a basic valid database.
## Communication with `schleuderd`
## Communication with `schleuder-api-daemon`
This image requires a `schleuderd` running somewhere and accessible via `TCP/IP` -- one option is to run the [`schlocker3` docker image](https://git.occrp.org/libre/schlocker3/). You can configure the `schleuderd` URI with the `WEBSCHLOCKER_CONFIG_SCHLEUDERD_URI` environment variable described below.
This image requires a `schleuder-api-daemon` running somewhere and accessible via `TCP/IP` -- one option is to run the [`schlocker3` docker image](https://git.occrp.org/libre/schlocker3/). You can configure the `schleuder-api-daemon` host with the `WEBSCHLOCKER_CONFIG_API_HOST` environment variable described below.
**Please be advised that `schleuderd` does not, at this time, offer authentication, nor does it support `TLS`-encrypted connections. This means that `schleuder-web` should be run on the same physical machine, or at least on a connection that precludes the possibility of malicious connections being made to `schleuderd`.** You have been warned!
By default `weschleuder3` listens on port `3000` (you can change this by setting `$WEBSCHLOCKER_BIND_PORT` docker envvar) and will inform you about the IP address it is running on in the output.
By default `schleuder-web` listens on port `3000` (you can change this by setting `$WEBSCHLOCKER_BIND_PORT` docker envvar) and will inform you about the IP address it is running on in the output.
Once you have that, navigate your browser to `http://<IP-of-the-container>:3000/` and log-in with user `root@localhost`, password `slingit!`.
...
...
@@ -40,9 +39,13 @@ The hostname `schleuder-web` will run under, used among others in confirmation l