Add DNS and Caddy config for myvibes.world #457

Open
opened 2026-06-19 01:55:45 +00:00 by ldraney · 0 comments
Owner

Type

Feature

Lineage

Standalone — new domain provisioning for the my-vibes-world application.

Repo

ldraney/pal-e-platform

User Story

As a platform operator
I want myvibes.world to resolve to the Hetzner edge VPS and be reverse-proxied to the my-vibes-world Tailscale service
So that the application is publicly accessible at its custom domain

Context

The my-vibes-world application needs a public domain. The platform already manages DNS and Caddy config for palinks.app and landscaping-assistant.app using the same pattern: a GoDaddy A record pointing to the Hetzner edge server, plus a Caddy site entry in Salt pillar that proxies to the Tailscale hostname. This issue adds the same configuration for myvibes.world.

File Targets

Files the agent should modify:

  • terraform/dns.tf -- add GoDaddy A record for myvibes.world
  • salt/pillar/caddy.sls -- add caddy site entry for my-vibes-world

Files the agent should NOT touch:

  • terraform/main.tf -- no provider or module changes needed
  • salt/pillar/top.sls -- caddy pillar is already included

Feature Flag

none — infrastructure config only

Acceptance Criteria

  • tofu validate passes with the new DNS record in dns.tf
  • caddy.sls includes my-vibes-world site entry with domain myvibes.world, proxy target my-vibes-world.tail5b443a.ts.net, and www_redirect true
  • Follows existing patterns established by palinks.app and landscaping-assistant.app entries

Test Expectations

  • tofu fmt -check passes
  • tofu validate passes
  • YAML lint on caddy.sls passes
  • Run command: cd terraform && tofu init && tofu validate

Constraints

  • Follow existing resource naming pattern in dns.tf (snake_case domain name + _a suffix)
  • Follow existing site key naming pattern in caddy.sls (kebab-case)
  • TTL must be 600 to match existing records

Checklist

  • PR opened
  • Tests pass
  • No unrelated changes
  • pal-e-platform -- infrastructure project
### Type Feature ### Lineage Standalone — new domain provisioning for the my-vibes-world application. ### Repo `ldraney/pal-e-platform` ### User Story As a platform operator I want myvibes.world to resolve to the Hetzner edge VPS and be reverse-proxied to the my-vibes-world Tailscale service So that the application is publicly accessible at its custom domain ### Context The my-vibes-world application needs a public domain. The platform already manages DNS and Caddy config for palinks.app and landscaping-assistant.app using the same pattern: a GoDaddy A record pointing to the Hetzner edge server, plus a Caddy site entry in Salt pillar that proxies to the Tailscale hostname. This issue adds the same configuration for myvibes.world. ### File Targets Files the agent should modify: - `terraform/dns.tf` -- add GoDaddy A record for myvibes.world - `salt/pillar/caddy.sls` -- add caddy site entry for my-vibes-world Files the agent should NOT touch: - `terraform/main.tf` -- no provider or module changes needed - `salt/pillar/top.sls` -- caddy pillar is already included ### Feature Flag none — infrastructure config only ### Acceptance Criteria - [ ] `tofu validate` passes with the new DNS record in dns.tf - [ ] caddy.sls includes my-vibes-world site entry with domain myvibes.world, proxy target my-vibes-world.tail5b443a.ts.net, and www_redirect true - [ ] Follows existing patterns established by palinks.app and landscaping-assistant.app entries ### Test Expectations - [ ] `tofu fmt -check` passes - [ ] `tofu validate` passes - [ ] YAML lint on caddy.sls passes - Run command: `cd terraform && tofu init && tofu validate` ### Constraints - Follow existing resource naming pattern in dns.tf (snake_case domain name + `_a` suffix) - Follow existing site key naming pattern in caddy.sls (kebab-case) - TTL must be 600 to match existing records ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `pal-e-platform` -- infrastructure project
Sign in to join this conversation.
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
ldraney/pal-e-platform#457
No description provided.