PR #216 deleted .nixpacks/ and git-ignored it; both dev2 deploy workflows
build from .nixpacks/Dockerfile, so every deploy of master since has failed
before the build (lstat app/.nixpacks: no such file or directory). Restored
from f478025.
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* ops: deploy app.logicsrc.com to dev2 on merge
Railway deployed this on push; dev2 does not by itself. The workflow ssh's
to the box and runs /home/anthony/www/app.logicsrc.com/deploy-app.sh, which builds
the image from this checkout and restarts the compose stack. Generated by
cli-tools dev2/dev2-site scaffold.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* ops: stop committing the nixpacks build plan
`railway up` writes .nixpacks/ into the working tree: a Dockerfile, a
nixpkgs pin, and a build.sh that hard-codes the absolute path of the
worktree it ran in plus a one-off image tag. None of it is reusable and
no workflow reads it, so every branch that deploys regenerates it and
conflicts with the last one -- which is exactly how this branch ended up
CONFLICTING against master.
Drop it and ignore it.
* ops: drop the nixpacks build plan master picked up in #215
Same detritus, same stale absolute path (a worktree that no longer
exists). Now ignored, so it will not come back.
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Railway deployed this on push; dev2 does not by itself. The workflow ssh's
to the box and runs /home/anthony/www/logicsrc.com/deploy-app.sh, which builds
the image from this checkout and restarts the compose stack. Generated by
cli-tools dev2/dev2-site scaffold.
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
