Commit 0e455184 authored by paz's avatar paz
Browse files

Fix URLs, names, outdated information.

parent 4ffd3a12
# [Webschleuder](https://git.codecoop.org/schleuder/webschleuder3) on `docker`
This repo contains `docker` configuration for `schleuder-web`, a web interface for an encrypted group email system `schleuder3`.
This repo contains `docker` configuration for `schleuder-web`, a web interface for an encrypted group email system `schleuder`.
Uses `schleuder3 beta`, because it seems to actually be installable on modern systems. See:
See:
* https://git.codecoop.org/schleuder/schleuder3
* https://git.codecoop.org/schleuder/schleuder
* https://git.codecoop.org/schleuder/schleuder-conf
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!
## Running and testing
......@@ -25,7 +24,7 @@ $ docker build -t 'webschlocker3' webschlocker3/
$ docker run --rm --name webschlocker-test --link schlocker-test -e WEBSCHLOCKER_CONFIG_SCHLEUDERD_URI="http://schlocker-test:4443/" webschlocker3
```
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
Hostname (or IP address) and port to bind to.
- `WEBSCHLOCKER_CONFIG_SCHLEUDERD_URI` (default: `http://localhost:4443/`)
- `WEBSCHLOCKER_CONFIG_API_HOST` (default: `localhost`)
URI the `schleuderd` daemon can be reached at.
Host the `schleuderd` daemon can be reached at.
- `WEBSCHLOCKER_CONFIG_API_PORT` (default: `4443`)
Port the `schleuderd` daemon can be reached at.
- `WEBSCHLOCKER_CONFIG_MAILER_FROM` (default: `noreply@$WEBSCHLOCKER_CONFIG_HOSTNAME`)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment