창 하나, 버전 아님

#!/usr/bin/env bash
# One command, one window. Every manual step lengthens the interval
# during which the system is in a state nobody designed for.
set -euo pipefail

# 1. the OWNER first - it defines the contract. Two lines, not
#    "deploy && restart": set -e ignores a failure in any command
#    of an && list except the last, so a failed deploy there would
#    roll straight on into the consumers.
deploy owner-service
restart owner-service

# 2. the shared layer - vendored copies into every consumer
python sync/kit_sync.py

# 3. each consumer engine
for app in app-a app-b app-c; do deploy "$app"; done

# 4. RESTART THEM TOGETHER. The step people skip, and the one that
#    makes the previous three real: a running process holds the code
#    it imported at STARTUP, so files on disk change nothing until
#    this line runs.
for app in app-a app-b app-c; do restart "$app"; done

# Only now is it meaningful to look at anything.
for app in app-a app-b app-c; do healthcheck "$app"; done


# THE STATE THAT IS NOT SUPPORTED - and why it is worse than broken:
#
#   owner    deployed   speaks the NEW vocabulary
#   shared   deployed   translates for the NEW vocabulary
#   app-a    deployed   but NOT RESTARTED -> still runs the OLD code
#   app-b    not yet deployed
#
# Nothing crashes. Requests go through, responses parse, and one
# field means something slightly different than the receiver
# assumes. Any test run here describes a configuration that will
# not exist in five minutes.


# THE DIAGNOSTIC for "landed but not deployed", which is the same
# failure at rest: compare the process start time against the
# modification time of the file whose behavior you are expecting.
#
#   ps -o lstart= -p "$(pgrep -f app-a)"
#   stat -f '%Sm' app-a/registry.py
#
# A file NEWER than the process is the whole explanation, and it is
# the fastest way out of an argument with your own source code.