8. Register your account. The first account is an admin-account with access to the application settings.
9. Alternatively can you configure the application using the `settings.cfg`. For all configuration options please see [[Configuration]].
10. Create a service file e.g. `/etc/systemd/system/otterwiki.service`
@@ 187,8 187,8 @@
[Install]
WantedBy=multi-user.target
```
-
-
make sure to adapt the `/path/to` and that the configured User can read and write the database and the repository folder.
+
+
Make sure to adapt the `/path/to` and that the configured user can read and write the database and the repository folder.
11. Run `systemctl daemon-reload` and `systemctl start otterwiki.service`, check `systemctl status otterwiki.service` for errors.
@@ 204,13 204,15 @@
when hosting multiple services on a host and make it much easier to configure
https. Neither An Otter Wiki itself nor the in the docker image provides https.
-
Mini how-tos for configuring Apache, NGINX and Caddy are provided below. For complete documention please check the corresponding software documention.
+
Mini how-tos for configuring Apache, NGINX and Caddy are provided below. For
+
more detailed informations please check the corresponding software documentation.
## NGINX
-
This is a minimal example of a config that configures NGINX as a reverse proxy. The full documentation about NGINX as reverse proxy can be found [here](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/).
+
This is a minimal example of a config that configures NGINX as a reverse proxy.
+
The full documentation about NGINX as reverse proxy can be found [here](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/).
-
It's assumed that An Otter Wiki is running either in a docker container or as a uwsgi process and listening on port 8080.
+
It's assumed that An Otter Wiki is running either in a docker container or as a `uwsgi` process and listening on port 8080.
```nginx
server {
@@ 296,4 298,4 @@
}
```
-
With a server accessible from the internet, `domain.tld` beeing a proper domain name with A/AAAA DNS records pointing to the server, caddy will [automatically](https://caddyserver.com/docs/automatic-https) serve HTTPS.
+
With a server accessible from the internet, `domain.tld` being a proper domain name with A/AAAA DNS records pointing to the server, caddy will [automatically](https://caddyserver.com/docs/automatic-https) serve HTTPS.
