mirror of
https://github.com/profullstack/logicsrc.git
synced 2026-10-01 20:33:50 +00:00
ops: deploy app.logicsrc.com to dev2 on merge (#216)
* 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>
This commit is contained in:
parent
f4780259fd
commit
587c073f72
5 changed files with 65 additions and 58 deletions
5
.gitignore
vendored
5
.gitignore
vendored
|
|
@ -11,3 +11,8 @@ test-results
|
|||
.commandboard
|
||||
.logicsrc
|
||||
supabase/.temp
|
||||
|
||||
# Nixpacks build plan generated by `railway up`. It bakes absolute paths to the
|
||||
# worktree it was generated in and a one-off image tag, so it is never reusable
|
||||
# and every regeneration conflicts with the last one.
|
||||
.nixpacks/
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue