deploy/single-vm scaffolding never end-to-end tested; multiple gaps #72
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_slides#72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bringing up
deploy/single-vm(branchdevelopment_feat_deploy_single_vm) end-to-end againstdevgrid required ~10 patches. Each is a blocker for a cleanmake all ENV=dev.Scaffolding bugs:
tf/main.tfmissingyggdrasilarg ingrid_scheduler.requests— required bythreefoldtech/gridv1.11.6.scripts/setup.shwrites a systemd unit and callssystemctl, but the TFGrid VM entrypoint is/sbin/zinit init. Replace with a zinit unit + wrapper script that sources/root/app.env(zinit YAML can'tEnvironmentFile).envs/{dev,prod}/app.env.examplepinsHERO_PROC_VERSION=0.5.0-rc1, but those registry artifacts are named-x86_64-unknown-linux-musl, whilesetup.shfetches-linux-amd64. Pin to 0.4.4 or align names.envs/dev/app.env.examplepinsHERO_DB_VERSION=dev, but only the CLI is published atdev; no_serverartifact. Pin to 0.3.2.scripts/{setup,update}.shfetcheshero_db_admin-linux-amd64— registry only hashero_db_ui-linux-amd64and slides doesn't use it. Drop the fetch.hero_slides_adminonly binds a unix socket, but the TFGrid gateway proxies HTTPS→VM:8883 → gateway returns 502. Add a socat zinit unit on:8883 → /data/hero/var/sockets/hero_slides/admin.sock+apt-get install -y socat.hero_db0.3.2 SDK uses old socket namehero_proc_server.sock; hero_proc 0.4.4+ createshero_proc/rpc.sock. Add a transitional symlink in setup.sh.hero_slides_serverexpects/data/hero/var/sockets/hero_db/rpc.sock, but hero_db 0.3.2 publishes flathero_db_server.sock→/rpcreturnsBackend unavailable. Second transitional symlink needed.envs/*/app.env.exampledoesn't documentFORGE_TOKEN+WEBROOT— hero_proc 0.4.4 hard-refuses to start without them (see hero_proc issue)..forgejo/workflows/. Thedevbinaries used here were published manually; CI would catch (3)–(5) immediately.Deployed successfully after applying all patches manually: https://devslides.gent02.dev.grid.tf/