The adopted node still runs the predecessor's mongo container, and it must keep running: invoicing points at novox.be:27017 and is not migrating in this window. A module container named mongo would be held at assign and would replace the predecessor at take, cutting invoicing off its database.
The mesh's server coexists instead — fresh data directory (/services/mongodb/db-data, distinct from the predecessor's /services/mongodb/data, which also keeps the minted root secret honest — mongo only applies MONGO_INITDB_ROOT_* to an empty data dir), its own name, auto-allocated machine port. The predecessor retires with its last consumer.
The runtime's MESH_PROVISION_MONGODB follows the rename: container names double as DNS on the module's network.
The adopted node still runs the predecessor's `mongo` container, and it must keep running: invoicing points at `novox.be:27017` and is not migrating in this window. A module container named `mongo` would be held at assign and would replace the predecessor at take, cutting invoicing off its database.
The mesh's server coexists instead — fresh data directory (`/services/mongodb/db-data`, distinct from the predecessor's `/services/mongodb/data`, which also keeps the minted root secret honest — mongo only applies `MONGO_INITDB_ROOT_*` to an empty data dir), its own name, auto-allocated machine port. The predecessor retires with its last consumer.
The runtime's `MESH_PROVISION_MONGODB` follows the rename: container names double as DNS on the module's network.
The adopted node still runs the predecessor's mongo container, and it must
keep running: invoicing points at novox.be:27017 and is not migrating in
this window. A module container named 'mongo' would be held at assign and
would replace the predecessor at take, cutting invoicing off its database.
The mesh's server coexists instead — fresh data directory, its own name,
auto-allocated machine port — and the predecessor retires with its last
consumer.
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 adopted node still runs the predecessor's
mongocontainer, and it must keep running: invoicing points atnovox.be:27017and is not migrating in this window. A module container namedmongowould be held at assign and would replace the predecessor at take, cutting invoicing off its database.The mesh's server coexists instead — fresh data directory (
/services/mongodb/db-data, distinct from the predecessor's/services/mongodb/data, which also keeps the minted root secret honest — mongo only appliesMONGO_INITDB_ROOT_*to an empty data dir), its own name, auto-allocated machine port. The predecessor retires with its last consumer.The runtime's
MESH_PROVISION_MONGODBfollows the rename: container names double as DNS on the module's network.cc7c7fe5eatoccb6e7500e