Files deployed via CI/CD have incorrect permissions #2

New issue

Open

opened 2026-05-18 20:05:32 -06:00 by Xeplosion · 0 comments

Xeplosion commented

2026-05-18 20:05:32 -06:00

Owner

When new files are pushed to a repo and deployed via CI/CD, they are owned by the xeplosion user and may not be readable by the service user running the program (e.g. bungeecord, nginx, etc.).
Steps to reproduce:

Add a new config file to a repo.
Push tomaster and merge to release and let CI/CD deploy it.
Restart the service — it fails with Permission denied.

Proposed fix:

Add a permission fix step to the deploy workflow in deploy.yml that sets the correct permissions on the repo folder after pulling:

chmod -R 644 ~/REPO_NAME/
find ~/REPO_NAME -type d -exec chmod 755 {} \;

Additional notes:

The README should be updated to document the expected permissions setup for each repo.
Each repo should document which user runs the service and what permissions are needed.

When new files are pushed to a repo and deployed via CI/CD, they are owned by the `xeplosion` user and may not be readable by the service user running the program (e.g. `bungeecord`, `nginx`, etc.). Steps to reproduce: 1. Add a new config file to a repo. 2. Push to`master` and merge to `release` and let CI/CD deploy it. 3. Restart the service — it fails with `Permission denied`. Proposed fix: Add a permission fix step to the deploy workflow in `deploy.yml` that sets the correct permissions on the repo folder after pulling: ```bash chmod -R 644 ~/REPO_NAME/ find ~/REPO_NAME -type d -exec chmod 755 {} \; ``` Additional notes: - The README should be updated to document the expected permissions setup for each repo. - Each repo should document which user runs the service and what permissions are needed.

Rows
Columns