2026-08-20 - 2026-11-20
Overview
10 Pull requests merged by 1 user
Merged
#15 fix: hand ssl_certs to netork before the swap (NetOrk/netork#1389)
Merged
#14 feat: the bundled database on every deploy, and --infra-db to move it (NetOrk/netork#1308)
Merged
#13 feat: reconcile the broker before the engine (NetOrk/netork#1308)
Merged
#11 fix: record the version in .env before starting the containers
Merged
#10 feat: refuse a tag without an image for the host's platform
Merged
#9 fix: report only the retired services a host actually had
Merged
#8 docs: a target server needs at least 4 GB of RAM
Merged
#5 fix: remove the bundled registry from every host, and stop starting it
Merged
#4 fix: one deploy per host at a time, under a lock the host frees on its own
Merged
#2 fix: a failed container recreate is tried once more before the deploy gives up
2 Pull requests proposed by 1 user
Proposed
#12 docs: write the README for people installing netOrk themselves
Proposed
#16 fix: remove only the images the deploy replaced, never every unused one
4 Issues closed from 1 user
Closed
#6 Containers start with the previous deploy's NETORK_VERSION in their environment
Closed
#7 deploy.sh reports removing netork-registry-1 on every deploy, also when it is not there
Closed
#1 deploy.sh: two deploys to one host at once recreate each other's containers
Closed
#3 deploy.sh: two deploys to the same host at once collide on the compose files
4 Issues created by 0 users
Opened
#1 deploy.sh: two deploys to one host at once recreate each other's containers
Opened
#3 deploy.sh: two deploys to the same host at once collide on the compose files
Opened
#6 Containers start with the previous deploy's NETORK_VERSION in their environment
Opened
#7 deploy.sh reports removing netork-registry-1 on every deploy, also when it is not there