fix(apps): use working HTTPS Forgejo remote in onboarding templates #11

Merged
janpeter merged 1 commit from fix/app-template-forgejo-remote into main 2026-05-21 09:19:40 +02:00
Owner

The new-app manifest example + runbook used git@forgejo.jp-visser.nl:... which does not match this host (remote is git.jp-visser.nl, SSH on :2222). Every repo here clones over https://git.jp-visser.nl/janpeter/<repo>.git. Align the templates.

🤖 Generated with Claude Code

The new-app manifest example + runbook used `git@forgejo.jp-visser.nl:...` which does not match this host (remote is git.jp-visser.nl, SSH on :2222). Every repo here clones over `https://git.jp-visser.nl/janpeter/<repo>.git`. Align the templates. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
The new-app manifest example and runbook used git@forgejo.jp-visser.nl:...
which does not match this host: the Forgejo remote is git.jp-visser.nl and
SSH runs on :2222, so scp-style git@host:path (port 22) would fail. Every
existing repo here clones over https://git.jp-visser.nl/janpeter/<repo>.git,
which the ops-agent git_* flows already pull over. Align the templates with
that working convention.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
janpeter/Ops-dashboard!11
No description provided.