feat(service): add PeerTube

[maebahesioru]

Changes

Adds a one-click deployment template for PeerTube, a free and open-source decentralized video platform (Fediverse / ActivityPub).

The template includes:

• peertube (port 9000) — main app (chocobozzz/peertube:production)
• postgres:17-alpine — database (matches official docker-compose.yml)
• redis:8-alpine — cache (matches official docker-compose.yml)
• postfix — mail relay for notifications

The official webserver/certbot/webserver-reloader services are omitted since Coolify handles reverse proxying. PEERTUBE_SECRET is auto-generated via SERVICE_HEX_32_*. PEERTUBE_WEBSERVER_HOSTNAME and PEERTUBE_ADMIN_EMAIL are required.

Note: Set the domain in Coolify with port included (e.g. http://peertube.example.com:9000) so Traefik can correctly route traffic. Cloudflare or other reverse proxies in front will still serve on port 80/443.

Issues

• Fixes

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Preview

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: Kiro
• How extensively: Template structure and environment variables verified against official Chocobozzz/PeerTube docker-compose.yml, .env sample, and custom-environment-variables.yaml. Deployed and tested on a live Coolify instance.

Testing

Deployed and verified on a live Coolify instance:

• All services (peertube, postgres, redis, postfix) reached running state
• PeerTube web UI accessible and functional at the configured domain
• Database initialized successfully on first boot
• Verified PEERTUBE_SECRET uses SERVICE_HEX_32 (matches openssl rand -hex 32 format)
• Domain must include port 9000 for Traefik routing to work correctly

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this is not a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.

[github-actions]

Hi @maebahesioru! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation