Feat: New services part 3

[peaklabs-dev]

Note

• All templates with (tested and works) have been tested and fixed by myself and are now fully functional
• This PR does not only include PRs from contributors, I also added some templates myself.
• Templates form myself are: Freshrss Postgres, Freshrss MariaDB, Freshrss MySQL, Nextcloud MariaDB, Nextcloud MySQL

Changes

• Fix: Nexctcloud
• Fix: Glitchtip
• Update Plausible
• Add CloudBeaver (fixed + tested and works)
• Add Freshrss sqlite (fixed + tested and works)
• Add Freshrss Postgres (fixed + tested and works)
• Add Freshrss MariaDB (fixed + tested and works)
• Add Freshrss MySQL (fixed + tested and works)
• Add Traccar (fixed + tested and works)
• Add Vvvweb (fixed + tested and works)
• Add Vvvweb MariaDB (fixed + tested and works)
• Add Vvvweb MySQL (fixed + tested and works)
• Add Nextcloud with Postgres (fixed + tested and works)
• Add Nextcloud with MariaDB (fixed + tested and works)
• Add Nextcloud with MySQL (fixed + tested and works)
• Add Kimai (fixed + tested and works)
• Add ntfy (fixed + tested and works)
• Add qbittorrent (fixed + tested and works)
• Add Homebox (fixed + tested and works)
• Add Owncloud (fixed + tested and works) -> I have disabled it for now as it also needs an FQDN (PR will fix this soon, it is the same problem as Azimut, you can leave it as it is for now, PR is in cooking in the Peak kitchen).
• Add Immich (fixed + tested and works)
• Add Cryptgeon (fixed + tested and works) -> The app itself throws and error when using but that is not our issue i think (@cupcakearmy see comment).
• Add Affine (fixed + tested and works)
• Add flowise
• Add flowise with postgres
• Add Unsend

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
14098696	Triggered	Generic Password	e1bcae7	templates/compose/resend.yaml	View secret
14098696	Triggered	Generic Password	8095453	templates/compose/resend.yaml	View secret
14098696	Triggered	Generic Password	aa2e170	templates/compose/resend.yaml	View secret
14100542	Triggered	Generic Password	77b3a3f	templates/compose/owncloud.yaml	View secret
14100542	Triggered	Generic Password	5d7d717	templates/compose/owncloud.yaml	View secret
14100542	Triggered	Generic Password	7da6b01	templates/compose/owncloud.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}