New files added to repo are not symlinked to the service directory #3

New issue

Open

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

Xeplosion commented

2026-05-18 20:09:23 -06:00

Owner

When a new config file is added to a repo and deployed via CI/CD, it is not automatically symlinked to the directory the service reads from (e.g. /opt/bungeecord/, /etc/nginx/sites-available/). This means the service won't pick up the new file even after a successful deploy.
Steps to reproduce:

Add a new config file to a repo.
Push to master and merge into release and let CI/CD deploy it.
The file exists in ~/REPO_NAME/ but not in the service directory.

Proposed fix:

Each repo should document a symlinking script or the README setup instructions should include a reminder to manually create symlinks for any new files added to the repo. A future improvement could be a scripts/symlink.sh script that handles this automatically and is run as part of the deploy workflow.

Additional notes:

Consider adding a scripts/symlink.sh to the template that each repo customizes
The deploy workflow could call scripts/symlink.sh after pulling and before restarting

When a new config file is added to a repo and deployed via CI/CD, it is not automatically symlinked to the directory the service reads from (e.g. `/opt/bungeecord/`, `/etc/nginx/sites-available/`). This means the service won't pick up the new file even after a successful deploy. Steps to reproduce: 1. Add a new config file to a repo. 2. Push to `master` and merge into `release` and let CI/CD deploy it. 3. The file exists in ~/REPO_NAME/ but not in the service directory. Proposed fix: Each repo should document a symlinking script or the README setup instructions should include a reminder to manually create symlinks for any new files added to the repo. A future improvement could be a `scripts/symlink.sh` script that handles this automatically and is run as part of the deploy workflow. Additional notes: - Consider adding a scripts/symlink.sh to the template that each repo customizes - The deploy workflow could call scripts/symlink.sh after pulling and before restarting

Rows
Columns