Slavi Pantaleev

Does FreshRSS ask you for the database password explicitly as some part of setup wizard? If so, sounds like we need to update its installation docs and likely advise people...

In that case it seems like: - `group_vars/mash_servers` should not try to auto-generate a password for FreshRSS (`freshrss_database_password`) - validation tasks in the FreshRSS role should ensure that `freshrss_database_password` is...

Try `docker exec --user $(id -u mash) mash-nextcloud-server php occ`

From what I remember, you're supposed to do the `adjust-config` thing **only after** going through the installation steps via the web UI. This is also documented here: https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/nextcloud.md#usage

Using the [Gitea role](https://github.com/mother-of-all-self-hosting/ansible-role-gitea) and overriding a few variables in your `vars.yml` file should work. Most importantly, you should override the `gitea_container_image` variable: https://github.com/mother-of-all-self-hosting/ansible-role-gitea/blob/a75e575ecdec6a734e772b9df94d24dc54f1fb7f/defaults/main.yml#LL19C1-L19C112 Perhaps this way: ```yaml # Not...

The [mattermost/focalboard](https://hub.docker.com/r/mattermost/focalboard) image published to Docker Hub only supports the `amd64` architecture. Our [focalboard Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-focalboard) does not yet support self-building of container images when the required architecture does not...

This label merely defines a middleware. To actually use it, it needs to be added to the middlewares list for the service. Not all roles define variables for doing this,...

The recommended way is to have only one of those playbooks install Traefik. Preferrably `matrix-docker-ansible-deploy`, because its Traefik setup is more involved (handling the custom port `tpc/8448` for federation, etc.)....

It's possible to use a single Postgres instance, but easiest if you run a Postgres instance for each playbook. By default, both playbooks automatically wire components to use their own...

Sound slike you're proposing some tighter coupling between the roles. In [matrix-docker-ansible-deploy](https://github.com/spantaleev/matrix-docker-ansible-deploy) we did stuff like this - you enable some component and via group vars it becomes automatically wired...