The /services paths were the adopted-node pattern doing its job: take replaced containers over the predecessor's data without moving a byte (gitea set it — "its data never moved"). With every cutover done the exception has no reason left, and the operator called it: a nox module's world is /var/lib/<module>, data included.
Six modules repathed: gitea (/var/lib/gitea/data), mailu (/var/lib/mailu/data/*), nextcloud (/var/lib/nextcloud-module/html), only-office (/var/lib/only-office/*), portainer (/var/lib/portainer/data), mongodb (/var/lib/mongodb/data). mssql keeps its /services path deliberately — still held, HAL-run, moves at its own take. Both trees are one filesystem, so each data move on the node is an instant rename done in the module's own stop→rename→push window.
The `/services` paths were the adopted-node pattern doing its job: take replaced containers over the predecessor's data without moving a byte (gitea set it — "its data never moved"). With every cutover done the exception has no reason left, and the operator called it: a nox module's world is `/var/lib/<module>`, data included.
Six modules repathed: gitea (`/var/lib/gitea/data`), mailu (`/var/lib/mailu/data/*`), nextcloud (`/var/lib/nextcloud-module/html`), only-office (`/var/lib/only-office/*`), portainer (`/var/lib/portainer/data`), mongodb (`/var/lib/mongodb/data`). mssql keeps its `/services` path deliberately — still held, HAL-run, moves at its own take. Both trees are one filesystem, so each data move on the node is an instant rename done in the module's own stop→rename→push window.
The /services paths were the adopted-node pattern doing its job: take
replaced containers over the predecessor's data without moving a byte
(gitea set it — 'its data never moved'). With every cutover done the
exception has no reason left, and the operator called it: a nox
module's world is /var/lib/<module>, data included. Six modules
repathed; mssql keeps its /services path deliberately — it is still
held, HAL-run, and moves at its own take. Both trees are one
filesystem, so each move is a rename.
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
/servicespaths were the adopted-node pattern doing its job: take replaced containers over the predecessor's data without moving a byte (gitea set it — "its data never moved"). With every cutover done the exception has no reason left, and the operator called it: a nox module's world is/var/lib/<module>, data included.Six modules repathed: gitea (
/var/lib/gitea/data), mailu (/var/lib/mailu/data/*), nextcloud (/var/lib/nextcloud-module/html), only-office (/var/lib/only-office/*), portainer (/var/lib/portainer/data), mongodb (/var/lib/mongodb/data). mssql keeps its/servicespath deliberately — still held, HAL-run, moves at its own take. Both trees are one filesystem, so each data move on the node is an instant rename done in the module's own stop→rename→push window.