blumeops/docs/how-to/authentik/mirror-authentik-build-deps.md
Erich Blume f46a04b902
All checks were successful
Build Container (Nix) / detect (push) Successful in 2s
Build Container / detect (push) Successful in 2s
Restructure docs: consolidate, recategorize, and extract
- Consolidate 4 Authentik Nix derivation docs into one card
  (authentik-nix-build-components.md)
- Merge build-grafana-container + build-grafana-sidecar into
  build-grafana-images.md
- Move agent-change-process from how-to/ to explanation/ (it's a
  methodology doc, not a task guide)
- Extract Caddy custom build section from reference card into
  how-to/deployment/build-caddy-with-plugins.md
- Move expose-service-publicly from how-to/ to tutorials/ (it's a
  comprehensive walkthrough, not a quick task reference)
- Update all wiki-link references across affected docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 19:55:59 -07:00

1.3 KiB

title modified last-reviewed tags
Mirror Authentik Build Dependencies 2026-03-02 2026-03-02
how-to
authentik

Mirror Authentik Build Dependencies

Mirror the external repositories needed to build authentik from source onto the forge, ensuring full supply chain control.

Context

Building authentik from source requires fetching code from two GitHub repositories. The main goauthentik/authentik repo is already mirrored, but one companion repo needed mirroring:

  • goauthentik/client-go — Go API client bindings, versioned in lockstep with authentik (e.g. v3.2026.2.0 matches version/2026.2.0). Used by the Go server build.

Previously, authentik-community/django-rest-framework (a DRF fork) was also needed. As of authentik 2026.2.0, standard djangorestframework from PyPI is used instead — the fork mirror (authentik-django-rest-framework) can be archived.

What to Do

  1. Mirror goauthentik/client-go:
    mise run mirror-create https://github.com/goauthentik/client-go.git \
      --name authentik-client-go \
      --description "Go API client for authentik (lockstep versioned)"
    
  2. Verify mirror syncs: check tags appear on forge