unoverse 0.1.82 → 0.1.83

package/operator/lib/deploy.sh

@@ -429,11 +429,17 @@ EOF
   # install.yml creates. The remedy was to know that `unoverse deploy init` exists, which
   # is exactly the kind of knowledge this CLI is supposed to remove: deploy owns the whole
   # journey, so it asks the server what it is and picks the right playbook itself.
+  # THE MARKER IS "SETUP FINISHED", NOT "A DIRECTORY EXISTS". Testing for /opt/gravity
+  # looked right and was not: install.yml creates that directory as its seventh task, so a
+  # first-time setup that then FAILED at the database step still left it behind. The next
+  # deploy saw it, decided the server was ready, shipped images onto a database that had
+  # never been migrated, and reported success. The stamp is written only after install,
+  # database and verify have all passed, so an interrupted setup resumes as a setup.
   if [ -z "$subcommand" ]; then
     if ! ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -o ConnectTimeout=15 \
-         "$deploy_user@$deploy_host" 'test -d /opt/gravity' >/dev/null 2>&1; then
+         "$deploy_user@$deploy_host" 'test -f /opt/gravity/.setup-complete' >/dev/null 2>&1; then
       echo ""
-      info "New server. Running the full first-time setup ${DIM}(install, database, verify)${NC}"
+      info "This server's setup has not finished. Running it ${DIM}(install, database, verify)${NC}"
       subcommand="init"
     fi
   fi
@@ -478,6 +484,9 @@ EOF
         "$ansible_dir/playbooks/test-connectivity.yml" \
         -e "universe_root=$ROOT" \
         -e "env_file=$env_prod" || { rm -f "$tmp_inventory"; fail "verification failed — inspect and re-run: unoverse deploy test"; exit 1; }
+      # Only now. Every step passed, so the next deploy can safely be an image push.
+      ssh -o BatchMode=yes -o StrictHostKeyChecking=accept-new -o ConnectTimeout=15 \
+        "$deploy_user@$deploy_host" 'touch /opt/gravity/.setup-complete' >/dev/null 2>&1
       echo ""
       ok "Your universe is up. From now on, deploys are just: unoverse deploy"
       info "Keeping it? Harden the VM when you're ready: unoverse deploy harden"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.82",
+  "version": "0.1.83",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",