Repository navigation
Conversation
This was referenced Oct 24, 2026
Open
Open
Open
wax911
marked this pull request as ready for review
October 25, 2026 22:36
wax911
enabled auto-merge (rebase)
October 25, 2026 22:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AniTrend's current deployment path combines generated Swarm stacks, service-local Compose configuration and a Doco-CD runner. This proposal defines the phased move to Pulumi, a small Ansible baseline and Dokploy, with private administration, repeatable releases and tested data recovery.
Tracks #652. The linked roadmap contains 15 core implementation issues (#653 through #667) and one optional gateway evaluation (#668).
Source of truth
The documentation includes the source-verified baseline, ownership ADR, local Docker and full-host validation contracts, secret/network boundaries, release gates, backup/restore requirements and data-safe cutover/rollback. Each issue includes context, prerequisites, source paths, deliverables, acceptance tests, evidence and downstream links.
APISIX stays in place for the core migration. Local Docker validation and a disposable real Hetzner rehearsal precede production cutover. Service-local sources remain authoritative through their ownership handoff.
Validation
Runtime acceptance is explicitly pending: Docker CLI/context were detected but this session could not access the daemon socket, and Pulumi/Ansible were unavailable on PATH. Issue #654 establishes the real local lab. No production migration or cloud provisioning was performed.