Repository navigation
chore(infra): node2 and node3 Fly configs as deployed for 0.8.1 - #614
Merged
Merged
Conversation
The live configs had never received TWIGPINE_P2P_KEY (added to these files in #324 but not deployed). 0.8.1 keeps the libp2p key in a file, so both nodes now set it to /data/keys/p2p.key on their volume, and cap the new connection pools for their 100-connection Postgres: 30 main, 24 lock pool, 16 concurrent pushes. Deployed with the released ghcr.io/twigpine/node:0.8.1 image on 2026-11-18.
Contributor
Member
Author
|
@coderabbitai approve |
Contributor
Action performed
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brings
infra/fly/gitlawb-node-2.fly.tomlandgitlawb-node-3.fly.tomlin line with what node2 and node3 actually run since the 0.8.1 upgrade on 2026-11-18.Motivation & context
The repo copies had drifted from the live apps.
GITLAWB_P2P_KEYwas added to these files in #324 but never deployed, and 0.8.1 needs two settings that weren't in either file:TWIGPINE_P2P_KEYeach deploy would mint a new PeerId.Kind of change
None of these fit: this is infra config only, with no code changes.
What changed
Both files, as saved from the live apps with
fly config saveafter the deploy:TWIGPINE_P2P_KEY = '/data/keys/p2p.key', on the volume (new PeerId once at the upgrade, stable after). It replaces the never-deployedGITLAWB_P2P_KEYline.TWIGPINE_DB_MAX_CONNECTIONS = '30',TWIGPINE_DB_LOCK_POOL_MAX_CONNECTIONS = '24',TWIGPINE_MAX_CONCURRENT_GIT_PUSHES = '16', about 54 connections at most. The lock pool stays at least 8 above the push limit.The other
GITLAWB_*settings are unchanged; 0.8.x still reads the old names. node1's config stays out of the repo (.gitignore).How a reviewer can verify
Checked on 2026-11-19: both files match the live configs apart from line order and comments.
Before you request review
cargo test --workspacepasses locallycargo fmt --allandcargo clippy --workspace --all-targets -- -D warningsare cleanfeat(...),fix(...),docs(...)).env.exampleupdated if behavior or config changed (or N/A)The unchecked boxes are N/A: no Rust changes.
Protocol & signing impact
did:key, Ed25519 / RFC 9421 signatures, UCAN, ref certs, or P2P wire formatsNotes for reviewers
*.gitlawb.cominGITLAWB_PUBLIC_URLandGITLAWB_BOOTSTRAP_PEERS. Moving them totwigpine.comis a separate change.Summary by CodeRabbit