fix: Staging directory permission error
Some checks failed
Deploy to Staging / Build Images (push) Successful in 20s
Deploy to Staging / Deploy to Staging (push) Failing after 5s
Deploy to Staging / Verify Staging (push) Has been skipped
Deploy to Staging / Notify Staging Ready (push) Has been skipped
Deploy to Staging / Notify Staging Failure (push) Successful in 5s
Some checks failed
Deploy to Staging / Build Images (push) Successful in 20s
Deploy to Staging / Deploy to Staging (push) Failing after 5s
Deploy to Staging / Verify Staging (push) Has been skipped
Deploy to Staging / Notify Staging Ready (push) Has been skipped
Deploy to Staging / Notify Staging Failure (push) Successful in 5s
This commit is contained in:
@@ -119,7 +119,7 @@ jobs:
|
|||||||
sudo chmod 755 data/backups data/documents
|
sudo chmod 755 data/backups data/documents
|
||||||
# Traefik acme.json requires 600 permissions
|
# Traefik acme.json requires 600 permissions
|
||||||
if [ ! -f data/traefik/acme.json ]; then
|
if [ ! -f data/traefik/acme.json ]; then
|
||||||
touch data/traefik/acme.json
|
sudo touch data/traefik/acme.json
|
||||||
fi
|
fi
|
||||||
chmod 600 data/traefik/acme.json
|
chmod 600 data/traefik/acme.json
|
||||||
|
|
||||||
|
|||||||
@@ -22,16 +22,17 @@ You are a senior software engineer specializsing in NodeJS, Typescript, front en
|
|||||||
- Make no assumptions.
|
- Make no assumptions.
|
||||||
- Ask clarifying questions.
|
- Ask clarifying questions.
|
||||||
- Ultrathink
|
- Ultrathink
|
||||||
- You will be fixing a bug the system backup and restore function.
|
- You will be implementing a staging environment for this application.
|
||||||
|
|
||||||
*** CONTEXT ***
|
*** CONTEXT ***
|
||||||
- This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s.
|
- This is a modern web app for managing a vehicle fleet. It has both a desktop and mobile versions of the site that both need to maintain feature parity. It's currently deployed via docker compose but in the future will be deployed via k8s.
|
||||||
- Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change.
|
- Read README.md CLAUDE.md and AI-INDEX.md and follow relevant instructions to understand this code repository in the context of this change.
|
||||||
- There are permission errors with the backup files.
|
- Currently the application is setup to run only production at the URL https://motovaultpro.com
|
||||||
- The backup directory is mapped from the filesystem of the host
|
- We are adding a staging workflow where first changes are pushed to a stage environment at https://staging.motovaultpro.com
|
||||||
- The app is deployed as the gitlab-runner user and group which is a different UID then the nodejs user
|
- The gitea workflow is working for this.
|
||||||
- Start with the files in this directory /Users/egullickson/Documents/Technology/coding/motovaultpro/backend/src/features/backup/api
|
- The Let's Encrypt certificates are working for this.
|
||||||
- The docker file is located at /Users/egullickson/Documents/Technology/coding/motovaultpro/backend/Dockerfile
|
- We need to ensure that the application can handle the routes/callbacks
|
||||||
|
- Recommend what changes need to be made to auth0 to allow this.
|
||||||
|
|
||||||
*** CHANGES TO IMPLEMENT ***
|
*** CHANGES TO IMPLEMENT ***
|
||||||
- Research this code base and ask iterative questions to compile a complete plan.
|
- Research this code base and ask iterative questions to compile a complete plan.
|
||||||
|
|||||||
Reference in New Issue
Block a user