cariconnect.de: DNS zone + edge/gateway vhosts for the project's own domain

erwin commented

2026-08-02 16:08:34 +00:00

Collaborator

cariconnect.de gets deployed on our existing rails: Cloudflare-managed DNS (IONOS stays registrar only), TLS at edge, WG to gateway, same Django upstream as cariconnect-bremen.gierz.xyz (which stays live as an alias during cutover). Apex canonical, www 301s at edge.

Operator steps before merge/converge (Paul):

Store the IONOS panel login: pass insert ionos/info@cariconnect.de
Add the cariconnect.de zone to the Cloudflare account (dashboard, one-time) and note the assigned nameserver pair.
Re-scope the vault Cloudflare API token to include the new zone (Zone:DNS:Edit + Zone:Read) — or confirm the token is account-wide.
In the IONOS panel, set the domain nameservers to the Cloudflare pair. Propagation up to 24h; the gierz.xyz alias keeps serving meanwhile.
Then, in order: ansible-playbook playbooks/cloudflare.yml → ansible-playbook -K playbooks/edge.yml → ansible-playbook -K playbooks/gateway.yml

Follow-up (separate PR after cutover): point the workshop manifest row at https://cariconnect.de/ and consider a 301 from cariconnect-bremen.gierz.xyz.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Q7CoB792p7kvDHmUX3ygXJ

cariconnect.de gets deployed on our existing rails: Cloudflare-managed DNS (IONOS stays registrar only), TLS at edge, WG to gateway, same Django upstream as cariconnect-bremen.gierz.xyz (which stays live as an alias during cutover). Apex canonical, www 301s at edge. **Operator steps before merge/converge (Paul):** 1. Store the IONOS panel login: `pass insert ionos/info@cariconnect.de` 2. Add the `cariconnect.de` zone to the Cloudflare account (dashboard, one-time) and note the assigned nameserver pair. 3. Re-scope the vault Cloudflare API token to include the new zone (Zone:DNS:Edit + Zone:Read) — or confirm the token is account-wide. 4. In the IONOS panel, set the domain nameservers to the Cloudflare pair. Propagation up to 24h; the gierz.xyz alias keeps serving meanwhile. 5. Then, in order: `ansible-playbook playbooks/cloudflare.yml` → `ansible-playbook -K playbooks/edge.yml` → `ansible-playbook -K playbooks/gateway.yml` **Follow-up (separate PR after cutover):** point the workshop manifest row at https://cariconnect.de/ and consider a 301 from cariconnect-bremen.gierz.xyz. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Q7CoB792p7kvDHmUX3ygXJ

erwin added 1 commit

2026-08-02 16:08:34 +00:00

cariconnect.de: DNS zone + edge/gateway vhosts for the project's own domain 8d072a21af

The domain is registered at IONOS (info@cariconnect.de) but IONOS is
registrar only: nameservers point at Cloudflare so the zone joins
gierz.xyz/gierz.eu/höring.eu in cloudflare_dns. Apex canonical, www
301s at edge. Gateway proxies to the same Django upstream as
cariconnect-bremen.gierz.xyz, which stays live during the cutover.

Not yet done (operator steps, in the PR description): add the zone to
the Cloudflare account, re-scope the API token to cover it, flip the
IONOS nameservers.

Co-Authored-By: LLM <noreply@invalid>
Claude-Session: https://claude.ai/code/session_01Q7CoB792p7kvDHmUX3ygXJ

This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin erwin/cariconnect-de:erwin/cariconnect-de

git switch erwin/cariconnect-de

Rows
Columns

cariconnect.de: DNS zone + edge/gateway vhosts for the project's own domain #11

Checkout