unoverse 0.1.79 → 0.1.81

package/operator/ansible/playbooks/deploy-images.yml

@@ -30,9 +30,16 @@
     # server's existing compose, so a new env var (e.g. MEMORY_SERVICE_URL) silently never
     # reached prod even though the image had the code. `.env` (per-server values) is left
     # untouched — only the canonical compose is refreshed from the repo.
+    #
+    # THE COMPOSE LIVES IN THE UNIVERSE, NOT NEXT TO THIS PLAYBOOK. `playbook_dir/../..`
+    # is the monorepo, where ansible/ and docker-compose.yml are siblings. Installed from
+    # npm they are not: the playbook sits in node_modules/unoverse/operator/ansible, and
+    # that path resolved to node_modules/unoverse/docker-compose.yml, which does not exist
+    # — so every deploy from an installed CLI died here on "Could not find or access". The
+    # deploy passes universe_root; the default keeps the monorepo working.
     - name: "[1/4] Sync docker-compose.yml (config travels with the deploy)"
       copy:
-        src: "{{ playbook_dir }}/../../docker-compose.yml"
+        src: "{{ universe_root | default(playbook_dir + '/../..') }}/docker-compose.yml"
         dest: "{{ gravity_dir }}/docker-compose.yml"
 
     - name: "[2/4] Pull latest platform images"

package/operator/ansible/playbooks/install.yml

@@ -121,7 +121,7 @@
 
     - name: "[7/12] Copy docker-compose.yml"
       copy:
-        src: "{{ playbook_dir }}/../../docker-compose.yml"
+        src: "{{ universe_root | default(playbook_dir + '/../..') }}/docker-compose.yml"
         dest: "{{ gravity_dir }}/docker-compose.yml"
         owner: "{{ ansible_user }}"
         mode: "0644"
@@ -137,7 +137,10 @@
 
     - name: "[8/12] Copy .env file"
       copy:
-        src: "{{ env_file | default('../../.env.production') }}"
+        # Same trap as the compose above: a path relative to the playbook is the monorepo's
+        # layout, not an installed CLI's. deploy always passes env_file, so this default is
+        # a fallback only — anchored to the universe rather than to node_modules.
+        src: "{{ env_file | default(universe_root | default(playbook_dir + '/../..') + '/.env.production') }}"
         dest: /opt/gravity/.env
         owner: "{{ ansible_user }}"
         mode: "0600"

package/operator/lib/deploy.sh

@@ -415,6 +415,21 @@ EOF
   export ANSIBLE_CONFIG="$ansible_dir/ansible.cfg"
   local subcommand="${1:-}"
 
+  # A FIRST DEPLOY TO A NEW SERVER IS A PROVISION, NOT AN IMAGE PULL. Bare `deploy` meant
+  # only "pull the latest images and restart", which on a freshly built droplet fails on
+  # "Destination directory /opt/gravity does not exist" — /opt/gravity being the directory
+  # 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.
+  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
+      echo ""
+      info "New server. Running the full first-time setup ${DIM}(install, database, verify)${NC}"
+      subcommand="init"
+    fi
+  fi
+
   case "$subcommand" in
     ""|deploy)
       # THE deploy: the server takes the latest platform images (pull + restart).
@@ -426,6 +441,7 @@ EOF
       ansible-playbook \
         -i "$tmp_inventory" \
         "$ansible_dir/playbooks/deploy-images.yml" \
+        -e "universe_root=$ROOT" \
         -e "env_file=$env_prod"
       ;;
     init|full)
@@ -438,18 +454,21 @@ EOF
       ansible-playbook \
         -i "$tmp_inventory" \
         "$ansible_dir/playbooks/install.yml" \
+        -e "universe_root=$ROOT" \
         -e "env_file=$env_prod" || { rm -f "$tmp_inventory"; fail "install failed — fix and re-run: unoverse deploy init"; exit 1; }
       echo ""
       info "[2/3] Database setup..."
       ansible-playbook \
         -i "$tmp_inventory" \
         "$ansible_dir/playbooks/db-setup.yml" \
+        -e "universe_root=$ROOT" \
         -e "env_file=$env_prod" || { rm -f "$tmp_inventory"; fail "db setup failed — fix and re-run: unoverse deploy db"; exit 1; }
       echo ""
       info "[3/3] Verifying..."
       ansible-playbook \
         -i "$tmp_inventory" \
         "$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; }
       echo ""
       ok "Your universe is up. From now on, deploys are just: unoverse deploy"
@@ -461,6 +480,7 @@ EOF
       ansible-playbook \
         -i "$tmp_inventory" \
         "$ansible_dir/playbooks/db-setup.yml" \
+        -e "universe_root=$ROOT" \
         -e "env_file=$env_prod"
       ;;
     test|check)
@@ -469,6 +489,7 @@ EOF
       ansible-playbook \
         -i "$tmp_inventory" \
         "$ansible_dir/playbooks/test-connectivity.yml" \
+        -e "universe_root=$ROOT" \
         -e "env_file=$env_prod"
       ;;
     harden)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.79",
+  "version": "0.1.81",
   "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",