chore: route cubex deployment through Dockerloid
This commit is contained in:
1 parent
af5261c644
commit
ac735a627e
2 files changed
+44
-45
No files matched your search
@@ -1,7 +1,8 @@
|
||||
# Canonical internal MySQL for the Jorge Cuadros platform.
|
||||
#
|
||||
# Target: Portainer "local" endpoint on cubex (192.168.4.212:9443), which is a
|
||||
# 3-node Docker Swarm. This is the source-of-truth database from the plan's
|
||||
# Target: cubex local endpoint, a 3-node Docker Swarm. The cubex workflow deploys
|
||||
# through Dockerloid; the separate Galactus workflow uses its own Portainer. This
|
||||
# is the source-of-truth database from the plan's
|
||||
# "internal server" — the migration transform+load and the NestJS API both
|
||||
# point at it, and (later) it becomes the replication SOURCE for the VPS.
|
||||
#
|
||||
@@ -25,7 +26,7 @@
|
||||
# and MySQL will always run there, reusing the same volume.
|
||||
#
|
||||
# Secrets (MYSQL_ROOT_PASSWORD, MYSQL_PASSWORD) are injected at deploy time via
|
||||
# Portainer env_data / stack environment, not committed here.
|
||||
# The stack action env_data / stack environment, not committed here.
|
||||
|
||||
version: "3.8"
|
||||
|
||||
|
||||
Reference in new issue
Block a user