The deploy repository is for customers installing netOrk on their own hosts.
README: dropped the Development section, the internal build tags (latest-dev, main-<sha>, feature-<name>), CI wording, issue references and the pointer into netOrk's technical docs. Documents only latest and release numbers; the per-server steps are described in user terms (order as of #11).
deploy.env.example: same tag list, override example now 0.37.0 instead of latest-dev.
deploy.sh itself is unchanged and still accepts the internal tags; its comments and error messages still name them.
The deploy repository is for customers installing netOrk on their own hosts.
- README: dropped the Development section, the internal build tags (`latest-dev`, `main-<sha>`, `feature-<name>`), CI wording, issue references and the pointer into netOrk's technical docs. Documents only `latest` and release numbers; the per-server steps are described in user terms (order as of #11).
- `deploy.env.example`: same tag list, override example now `0.37.0` instead of `latest-dev`.
`deploy.sh` itself is unchanged and still accepts the internal tags; its comments and error messages still name them.
The repository is meant for customers who run netOrk on their own
hosts. Drop the development section, the internal build tags
(latest-dev, main-<sha>, feature-<name>), CI wording and issue
references from the README and deploy.env.example; only latest and
release numbers are documented.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The deploy repository is for customers installing netOrk on their own hosts.
latest-dev,main-<sha>,feature-<name>), CI wording, issue references and the pointer into netOrk's technical docs. Documents onlylatestand release numbers; the per-server steps are described in user terms (order as of #11).deploy.env.example: same tag list, override example now0.37.0instead oflatest-dev.deploy.shitself is unchanged and still accepts the internal tags; its comments and error messages still name them.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.