unoverse 0.1.152 → 0.1.153
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/operator/operator.sh +11 -0
- package/package.json +1 -1
package/operator/operator.sh
CHANGED
|
@@ -157,6 +157,17 @@ case "${1:-}" in
|
|
|
157
157
|
if [ -n "$(docker compose -f "$ROOT/docker-compose.yml" ps -q 2>/dev/null)" ]; then
|
|
158
158
|
docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" up -d --remove-orphans >/dev/null 2>&1 \
|
|
159
159
|
&& ok "Running services moved to the new images"
|
|
160
|
+
# MIGRATIONS RUN ON UPDATE, same as deploy and start. An update is exactly when a
|
|
161
|
+
# new migration arrives (it ships inside the image just pulled), and this was the
|
|
162
|
+
# one path that skipped db-setup: a universe could run new code against a schema
|
|
163
|
+
# missing the columns that code expects, silently, until something read them.
|
|
164
|
+
# Additive-by-rule until Retire and idempotent, so re-running costs nothing.
|
|
165
|
+
# Subshell because cmd_db_setup exits rather than returns on failure.
|
|
166
|
+
if ! (cmd_db_setup) >/dev/null 2>&1; then
|
|
167
|
+
warn "Migrations did not apply. Run ${BOLD}unoverse check${NC} to see why"
|
|
168
|
+
else
|
|
169
|
+
ok "Database migrations are current"
|
|
170
|
+
fi
|
|
160
171
|
echo ""
|
|
161
172
|
echo -e " ${GREEN}unoverse where${NC} Links to your Canvas and API"
|
|
162
173
|
echo ""
|
package/package.json
CHANGED