Skip to content

deploy.yml: preserve sidecar broker + its nginx route on every VM deploy#81

Merged
Alexgodoroja merged 1 commit into
mainfrom
deploy/insforge-broker-durable-ci
Jul 8, 2026
Merged

deploy.yml: preserve sidecar broker + its nginx route on every VM deploy#81
Alexgodoroja merged 1 commit into
mainfrom
deploy/insforge-broker-durable-ci

Conversation

@Alexgodoroja

Copy link
Copy Markdown
Collaborator

Completes the durability fix. The on-merge VM deployer (deploy.yml) rebuilt only publish-server+broker and called setup-broker-tls.sh without broker-extra-locations, so every deploy regenerated broker.conf with just location / and dropped the signup broker's /insforge/signup route.

  • The deploy step now also rebuilds + restarts cmd/insforge-signup-broker (guarded on its unit being installed).
  • The HTTPS step now reads the broker-extra-locations metadata and passes it to setup-broker-tls.sh, which re-injects the route.

Verified by dispatching deploy.yml and confirming /insforge/signup survives the redeploy.

The on-merge VM deployer rebuilt only publish-server + broker and ran
setup-broker-tls.sh WITHOUT broker-extra-locations, so setup-broker-tls.sh
regenerated broker.conf with just `location /` and dropped the signup broker's
/insforge/signup route on every deploy. Now the deploy step also rebuilds +
restarts cmd/insforge-signup-broker (when its unit is installed) and passes the
broker-extra-locations metadata to setup-broker-tls.sh so the route is re-injected.
@Alexgodoroja Alexgodoroja merged commit efd59db into main Jul 8, 2026
6 checks passed
@Alexgodoroja Alexgodoroja deleted the deploy/insforge-broker-durable-ci branch July 8, 2026 04:19
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