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:09:43 +02:00
parent 2144a1fcb2
commit 720e83f833
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -13,8 +13,8 @@ Mailman 3 setup using Podman Quadlets. Containers are supposed to run in rootles
```bash $ cp mailman/* ~mailman/.config/containers/systemd/``` ```bash $ cp mailman/* ~mailman/.config/containers/systemd/```
1. Now we have to generate some secrets which the various components use to talk to each other: 1. Now we have to generate some secrets which the various components use to talk to each other:
```bash $ pwgen -1 32 | | podman secret create HYPERKITTY_API_KEY - ```bash $ 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_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. 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: 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```