Update peertube config #17

Open
opened 2025-09-17 14:44:49 +00:00 by 3wordchant · 6 comments
Owner

The upstream config file has had a LOT of additions https://github.com/Chocobozzz/PeerTube/blob/develop/config/production.yaml.example

CC @rscmbbng

The upstream config file has had a LOT of additions https://github.com/Chocobozzz/PeerTube/blob/develop/config/production.yaml.example CC @rscmbbng
Owner

There is also a default.yml that probably should be shipped in the recipe.

There is also a `default.yml` that probably should be shipped in the recipe.
Author
Owner

There is also a default.yml that probably should be shipped in the recipe.

Yes! I wonder how this relates to #16; which files should we include as docker configs directly, which should be "initial deploy only" configs (e.g. production-initial.yml which is only copied to production.yml if it doesn't exist), and which should be entirely operator-managed 🤔

> There is also a `default.yml` that probably should be shipped in the recipe. Yes! I wonder how this relates to #16; which files should we include as docker configs directly, which should be "initial deploy only" configs (e.g. `production-initial.yml` which is only copied to `production.yml` if it doesn't exist), and which should be entirely operator-managed 🤔
Owner

Related: https://docs.joinpeertube.org/maintain/configuration#peertube-configuration

Not exactly applicable but what I did with the beast that is matrix-synapse is just go through the base config for each update and decide if the new config deserves to be Packaged In The Recipe By Default ™️ and otherwise, I left it to the default settings: https://git.coopcloud.tech/coop-cloud/matrix-synapse/src/branch/main/homeserver.yaml.tmpl

Related: https://docs.joinpeertube.org/maintain/configuration#peertube-configuration Not exactly applicable but what I did with the beast that is `matrix-synapse` is just go through the base config for each update and decide if the new config deserves to be Packaged In The Recipe By Default ™️ and otherwise, I left it to the default settings: https://git.coopcloud.tech/coop-cloud/matrix-synapse/src/branch/main/homeserver.yaml.tmpl
Owner

@3wordchant and me looked at the issue in a bit more detail and for now we tell people to manually copy the default.yml for every release in to their config volume. That is because the local production.yml often needs manual editing as well, depending on your local circumstances.

Eventually, it would be good to track and ship those default.yml though.

@3wordchant and me looked at the issue in a bit more detail and for now we tell people to manually copy the `default.yml` for every release in to their config volume. That is because the local `production.yml` often needs manual editing as well, depending on your local circumstances. Eventually, it would be good to track and ship those `default.yml` though.
Author
Owner

@rscmbbng wild idea: abra command (defined in abra.sh which:

  1. Downloads dyff
  2. Runs it (with some pleasant options?) between /config/default.yml (old) and /app/config/default.yml (new)

Then either offers to copy the new default.yml into /config, or a separate command to do that.

@rscmbbng wild idea: abra command (defined in `abra.sh` which: 1. Downloads [`dyff`](https://github.com/homeport/dyff) 2. Runs it (with some pleasant options?) between `/config/default.yml` (old) and `/app/config/default.yml` (new) Then either offers to copy the new `default.yml` into `/config`, or a separate command to do that.
Owner

Also I noticed this change in the docker release notes:

The entire PeerTube configuration can be set using environment variables.
Keep in mind that environment variable configuration keys override web admin configuration

Which means future recipe versions could be more tailored towards integrating with object storage recipes etc

Also I noticed this change in the [docker release notes](https://github.com/Chocobozzz/PeerTube/releases/tag/v8.2.0): > The entire PeerTube configuration can be set using environment variables. > Keep in mind that environment variable configuration keys override web admin configuration Which means future recipe versions could be more tailored towards integrating with object storage recipes etc
Sign in to join this conversation.
No Label
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/peertube#17