Monorepo for Aesthetic.Computer
aesthetic.computer
lith/deploy.fish: build notepat.com amxd on every deploy
Mirrors ac-os upload's "always rebuild first" pattern for the M4L
distribution: after pulling the deployed commit, install oven deps
(with PUPPETEER_SKIP_DOWNLOAD so Chromium doesn't bloat the droplet),
then run \`node ac-m4l/build-notepat.mjs\` on the server. This
regenerates /m4l/notepat.com/<commit>.amxd plus latest.json with the
real deployed hash — no more "-dirty" suffixes, and the commit the
amxd was built from matches the commit lith is serving.
+8
-1
+8
-1
lith/deploy.fish
+8
-1
lith/deploy.fish
···
175
175
176
176
# Install deps
177
177
echo -e "$GREEN-> Installing dependencies...$NC"
178
-
ssh -i $SSH_KEY $LITH_USER@$TARGET_HOST "cd $REMOTE_DIR/lith && npm install --omit=dev && cd $REMOTE_DIR/system && npm install --omit=dev"
178
+
ssh -i $SSH_KEY $LITH_USER@$TARGET_HOST "cd $REMOTE_DIR/lith && npm install --omit=dev && cd $REMOTE_DIR/system && npm install --omit=dev && cd $REMOTE_DIR/oven && PUPPETEER_SKIP_DOWNLOAD=1 npm install --omit=dev --omit=optional"
179
+
180
+
# notepat.com amxd build stream.
181
+
# Modeled after `ac-os upload`'s "always rebuild first" pattern so
182
+
# notepat.com/amxd + /m4l/notepat.com/latest.json always reflect the
183
+
# commit we just deployed (no "dirty" hashes from dev machine state).
184
+
echo -e "$GREEN-> Building notepat.com.amxd from deployed commit...$NC"
185
+
ssh -i $SSH_KEY $LITH_USER@$TARGET_HOST "cd $REMOTE_DIR && node ac-m4l/build-notepat.mjs"
179
186
180
187
# Install service file + Caddy config from the deployed checkout
181
188
echo -e "$GREEN-> Updating service + Caddy config...$NC"