henning/mailman-podman-setup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Henning Oschwald
2024-04-06 16:21:07 +02:00
parent 4fcc10d6df
commit 775c5e1a2b
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -11,13 +11,15 @@ Mailman 3 setup using Podman Quadlets. Containers are supposed to run in rootles
$ mkdir -p ~mailman/.config/containers/systemd
1. Then copy the files from the *mailman/* subdirectory in this repository into the quadlet directory:
```bash $ cp mailman/* ~mailman/.config/containers/systemd/```
$ cp mailman/* ~mailman/.config/containers/systemd/
1. Now we have to generate some secrets which the various components use to talk to each other:
``` $ pwgen -1 32 | | podman secret create HYPERKITTY_API_KEY -
$ pwgen -1 32 | | podman secret create HYPERKITTY_API_KEY -
$ pwgen -1 32 | podman secret create MAILMAN_REST_PASSWORD -
$ pwgen -1 32 | podman secret create MAILMAN_WEB_SECRET_KEY - ```
$ pwgen -1 32 | podman secret create MAILMAN_WEB_SECRET_KEY -
1. Next adapt the environment variable definitions in mailman-core.container and mailman-web.container to your needs. You may want to customize at least the variable *SERVE_FROM_DOMAIN*, which is set to lists.example.com by default.
1. Finally run ```$ systemctl --user daemon-reload``` to trigger the systemd unit generator and start the services:
```$ systemctl --user start mailman-core mailman-web```
$ systemctl --user start mailman-core mailman-web
1. By default Systemd launches user services only when the user logs in. To create a user session when the system boots, enable the automatic user session creation on boot with the following command as root:
```# systemctl enable-linger mailman```
# systemctl enable-linger mailman