spencerm/PacketStation
1
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases Wiki Activity

Move the test stack files from ~/packetstation/test to /etc/packetstation/test #38

New Issue
Closed
opened 2026-10-19 02:50:24 +00:00 by spencerm · 2 comments
spencerm commented 2026-10-19 02:50:24 +00:00
Owner
Copy Link
Copy Source

The test stack was set up under /home/spencerm/packetstation/test because the session had no sudo. DEPLOY.md describes /etc/packetstation/ with secrets root:10001 mode 0440. The test secrets are world-readable inside the home folder until moved.

To do: move stack.env, secrets/, ca/ and backups/, fix ownership and modes, update ENV_FILE, SECRETS_DIR, CA_BUNDLE_FILE and BACKUP_DIR in stack.env, restart the stack.

Plan reference: OPS2 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.

The test stack was set up under /home/spencerm/packetstation/test because the session had no sudo. DEPLOY.md describes /etc/packetstation/<stack> with secrets root:10001 mode 0440. The test secrets are world-readable inside the home folder until moved. **To do:** move stack.env, secrets/, ca/ and backups/, fix ownership and modes, update ENV_FILE, SECRETS_DIR, CA_BUNDLE_FILE and BACKUP_DIR in stack.env, restart the stack. --- Plan reference: OPS2 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.
spencerm added the decision: IT label 2026-10-19 02:50:24 +00:00
spencerm commented 2026-10-19 02:56:11 +00:00
Author
Owner
Copy Link
Copy Source

This actually is fine because it matches the other docker compose setups that are on that server. So leave it as is under /home/spencerm

This actually is fine because it matches the other docker compose setups that are on that server. So leave it as is under /home/spencerm
spencerm commented 2026-10-19 14:09:33 +00:00
Author
Owner
Copy Link
Copy Source

Applied: the test stack stays under /home/spencerm/packetstation/test, and the docs and test.env.example now say so. One thing this issue does not settle: should the production stack follow the same layout (/home/spencerm/packetstation/prod, with stack.env, secrets/, ca/ and backups/), or stay at /etc/packetstation/prod with secrets root:10001 mode 0440 as DEPLOY.md describes? The docs keep /etc/packetstation/prod until you answer.

Applied: the test stack stays under /home/spencerm/packetstation/test, and the docs and test.env.example now say so. One thing this issue does not settle: should the production stack follow the same layout (/home/spencerm/packetstation/prod, with stack.env, secrets/, ca/ and backups/), or stay at /etc/packetstation/prod with secrets root:10001 mode 0440 as DEPLOY.md describes? The docs keep /etc/packetstation/prod until you answer.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
decision: Clerical
decision: IT
decision: Q.C.
decision: Seth
phase 10
phase 3
phase 4
phase 5
phase 6
phase 7
phase 8
phase 9
production
No labels decision: IT
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
SethD (Seth Dostaler) spencerm (Spencer McGuire)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: spencerm/PacketStation#38