eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Enforce unique doc filenames and simple wiki-links

Browse source 
Rename section index files to match their titles (tutorials.md,
reference.md, how-to.md, explanation.md) so all filenames are unique.
Convert all path-based wiki-links to simple filename format for better
obsidian.nvim compatibility.

Update doc-filenames task to no longer skip index.md files.
Update doc-links task to reject path-based links containing '/'.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-02-04 17:13:35 -08:00
commit ed24ffdd64
19 changed files with 78 additions and 58 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/tutorials/replication/core-services.md
View file

@ -10,7 +10,7 @@ tags:
> **Audiences:** Replicator
>
> **Prerequisites:** [[tutorials/replication/tailscale-setup | Tailscale Setup]]
> **Prerequisites:** [[tailscale-setup|Tailscale Setup]]
This tutorial walks through setting up the foundational services that your GitOps infrastructure depends on: a git forge and optionally a container registry.
@ -29,7 +29,7 @@ Forgejo runs directly on your server (not in Kubernetes) because Kubernetes depe
### Using Ansible (BlumeOps Approach)
BlumeOps manages Forgejo via an Ansible role. See [[reference/ansible/roles | Ansible Roles]].
BlumeOps manages Forgejo via an Ansible role. See [[roles|Ansible Roles]].
### Manual Installation
@ -101,7 +101,7 @@ For getting started, you can skip this and use public registries.
## Next Steps
- [[tutorials/replication/kubernetes-bootstrap | Bootstrap Kubernetes]] - Now that you have a git repo, set up your cluster
- [[kubernetes-bootstrap|Bootstrap Kubernetes]] - Now that you have a git repo, set up your cluster
- Configure Forgejo webhooks for ArgoCD (after ArgoCD is running)
## BlumeOps Specifics