Skip to content

feat: deploy to yupanki CT 127 + repoint Conectividad#1

Merged
Fede654 merged 1 commit into
mainfrom
deploy/yupanki
Apr 23, 2026
Merged

feat: deploy to yupanki CT 127 + repoint Conectividad#1
Fede654 merged 1 commit into
mainfrom
deploy/yupanki

Conversation

@Fede654

@Fede654 Fede654 commented Apr 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replaces the GitHub Pages deploy workflow with a self-hosted deploy to the new AlterMundi static-sites host (yupanki CT 127). The runner already lives on yupanki PVE host (AlterMundi org self-hosted, label yupanki); this PR just uses it.
  • Adds SITE.yml declaring this repo as the first tenant of the platform (slug altermundi-website, domain altermundi.net).
  • Repoints the Conectividad project card from libremesh.org to https://conectividad.altermundi.net/ — the legacy AlterMundi WordPress, re-exposed at a subdomain during the apex cutover.

Why

The apex of altermundi.net is moving from WordPress (CT 118) to this Next.js static export, per the infra design spec. The legacy WP content becomes the "Conectividad" destination; no WP content migration is required, only a new URL.

Deploy mechanics

Runner builds with npm ci && npm run build, then streams out/ into CT 127 via tar | sudo pct exec -- tar -x and calls /usr/local/bin/promote altermundi-website for the atomic swap. No secrets. No inbound SSH on CT 127. Previous release retained at /srv/www/altermundi-website.prev for one-command rollback.

Cutover sequence

Merging this PR is not the cutover moment. Order (coordinated with Alter-infra PR):

  1. Merge this PR OR trigger workflow_dispatch on deploy/yupanki → build lands on CT 127 (invisible to the public).
  2. Verify CT 127 serves the site internally.
  3. Flip the altermundi.net edge symlink on CT 112 from the WordPress proxy to CT 127 — user-visible cutover.
  4. Run the WP DB siteurl/home UPDATE so conectividad.altermundi.net serves clean canonical URLs.

Rollback: restore the previous edge vhost symlink + symmetric WP UPDATE. Both one-command.

Related

  • Infra spec: AlterMundi/Alter-infra docs/superpowers/specs/2026-04-22-altermundi-static-sites-platform-design.md
  • Infra plan: AlterMundi/Alter-infra docs/superpowers/plans/2026-04-22-altermundi-static-sites-phase-1.md

Test plan

  • gh workflow run deploy.yml --ref deploy/yupanki succeeds end-to-end
  • /srv/www/altermundi-website/index.html exists on CT 127 after run
  • Internal curl -H 'Host: altermundi-website.internal' http://10.1.1.15/ returns 200
  • After edge symlink flip, https://altermundi.net/ serves the new site (Next.js, not WordPress)
  • Conectividad card navigates to https://conectividad.altermundi.net/
  • Rollback drill passes (second deploy, .prev exists, swap works)

- Replace GH Pages workflow with self-hosted runner deploy on yupanki
  (runs-on: [self-hosted, yupanki]). Streams `out/` into CT 127 via
  `sudo pct exec` tar-pipe, then calls /usr/local/bin/promote for the
  atomic release swap. No secrets; the runner's scoped sudoers on the
  yupanki host is the trust boundary.
- Add SITE.yml declaring slug/domain for the Alter-infra registry.
- Update "Conectividad" project card URL from libremesh.org to
  https://conectividad.altermundi.net/, which is the legacy WordPress
  re-exposed at a subdomain during the altermundi.net cutover.

Infra spec: Alter-infra docs/superpowers/specs/2026-04-22-altermundi-static-sites-platform-design.md
Infra plan: Alter-infra docs/superpowers/plans/2026-04-22-altermundi-static-sites-phase-1.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Fede654
Fede654 marked this pull request as ready for review April 23, 2026 00:49
@Fede654
Fede654 merged commit 0daaf99 into main Apr 23, 2026
1 check passed
@Fede654
Fede654 deleted the deploy/yupanki branch April 23, 2026 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant