multi: cleanup docker compose configs, use secrets instead of hard coded credentials, add basic CI configuration#12
Merged
torkelrogstad merged 5 commits intomasterfrom Mar 3, 2026
Conversation
torkelrogstad
force-pushed
the
2026-03-03-cleanup
branch
from
8841d20 to
e12289c
Compare
Avoid hard-coding credentials. Instead, implement RPC auth exclusively through cookie files and Docker secrets.
torkelrogstad
force-pushed
the
2026-03-03-cleanup
branch
from
e12289c to
ba24f64
Compare
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
1 participant
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.
The idea is to interact with the different networks through
just compose-signet <ARG>orjust compose-forknet <ARG>. Other networks should be simple to add.Another principle is to avoid hard coded credentials, but instead rely on RPC cookie files and Docker secrets.