Repository navigation
feat(local): port check and a shared-host port block next to other stacks - #6
Merged
Merged
Conversation
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.
NETRA can now run on one machine next to Taksu, the Molly dashboard and the server monitoring without taking their ports. Replaces #1, now on top of dev.
scripts/local.sh upandstartcheck the ports NETRA publishes (LAN port, and the tunnel port with the tunnel overlay) before starting, and stop with the compose project or program that holds a port. Ports already published by NETRA's own Caddy pass.scripts/local.sh portslists those ports and who holds them;doctorhas the same check..env.local.example: the commented shared-host settings (NETRA_TUNNEL_PORT=4490,NETRA_LAN_PORT=4491,NETRA_LAN_BIND=127.0.0.1).Defaults are unchanged (LAN 80, tunnel 8088), so a laptop at a site and the current tunnel keep working.
The LOCAL.md conflict with dev: the commands table keeps the new
portsrow and dev'slogs [api|db|caddy|...].Checked: shellcheck of every script the validate workflow checks;
docker compose configof the local and tunnel files.