[mortik]

Stacked on #44. Merge only after #44 is applied and web-1 is healthy on cx43.

Moves the second live web server to cx43, finishing the rollout #44 started. The live entry becomes ["cx43", "cx43"].

Expected live plan

• hcloud_server.web_server[1]: server_type cx33 → cx43 and its http label coming back (removed in rollout step 1), an in-place update.
• Nothing else. No deletes or replacements.

Rollout

Keep this in draft until web-1 is healthy on cx43. If this reaches main before #44 is applied, one apply powers off both web servers. Retarget it to main before merging, which also makes CI run on it.

The steps are in MAINTENANCE.md, under "Rescaling Web Servers (Live)", this time for web-2 (178.104.119.84). Keep merges held in the app repo, and stay clear of the heavy scheduled jobs:

1. hcloud server-type describe cx43.
2. Mark this ready, retarget it to main, and merge.
3. kamal app version -d live --hosts 178.104.119.84, from the app repo, and note the version.
4. hcloud server remove-label fltyrd-live-web-2 http.
5. kamal app stop -d live --hosts 178.104.119.84. This also stops the Discord bot, which was on this server on 2026-11-04; check before starting, as it follows the first IP the server list returns.
6. hcloud server shutdown fltyrd-live-web-2, then wait for it to be off.
7. Run Deploy with target live, check the plan against the list above, and apply.
8. hcloud server poweron fltyrd-live-web-2, then wait for SSH.
9. kamal app start -d live --hosts 178.104.119.84 --version=<version>, then wait for the target to report healthy.

Testing

terraform fmt -check, terraform validate and terraform test pass.

🤖