Add borgmatic-ui-community deployment on homeauto

[Copilot]

• Create borgmatic-ui/docker-compose.yaml using NFS volumes, Traefik labels, docker.sock and host filesystem mounts
• Pin image to ghcr.io/speedbitsinfinitytools/borgmatic-ui:1.0.42 (latest release, was :latest)
• Add borgmatic-ui to up.sh (homeauto section)
• Add borgmatic-ui to pull.sh (homeauto section)
• Validate compose file syntax

[kylegordon]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved. The conflicts in up.sh and pull.sh have been merged — keeping the borgmatic-ui lines from this branch alongside the new nautobot/selenium/immich lines from master. Pushed in f7ee363.

[gitguardian]

⚠️ GitGuardian has uncovered 9 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
33739063	Triggered	Generic Password	d636468	pixelfed/archive/native/.env.docker	View secret
33739063	Triggered	Generic Password	d636468	pixelfed/archive/native/.env.docker	View secret
33739067	Triggered	Generic Password	d636468	pixelfed/archive/attempt_2_env	View secret
33739066	Triggered	Generic Password	d636468	pixelfed/.env-kg-old	View secret
33739068	Triggered	Generic Password	d636468	pixelfed/archive/pixelfed.yaml	View secret
33739069	Triggered	Username Password	d636468	pixelfed/archive/attempt_2_env	View secret
33739067	Triggered	Generic Password	d636468	pixelfed/archive/native/.env.docker	View secret
33739065	Triggered	SMTP credentials	d636468	pixelfed/.env-kg-old	View secret
33739064	Triggered	Generic Password	d636468	pixelfed/archive/pixelfed.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.}