chore(nginx): stop tracking the generated site config
Some checks failed
Deploy to Production / Trigger production update (push) Failing after 11s
Some checks failed
Deploy to Production / Trigger production update (push) Failing after 11s
nginx/conf.d/pvemanager.conf is not source: setup_nginx_config() writes it
on every deploy by copying one of the .template files and substituting the
domain. Tracking it meant the repository carried one deployment's hostname,
and every deploy showed the file as modified.
Untrack it and ignore it. The templates it is generated from stay tracked,
so nothing is lost — a missing copy is restored by re-running deploy.sh, or
by hand:
cp nginx/conf.d/pvemanager.conf.template nginx/conf.d/pvemanager.conf
sed -i "s/DOMAIN_NAME/<domain>/g" nginx/conf.d/pvemanager.conf
Note for existing checkouts: this commit deletes the path, so a deployed
host that pulls it will lose its live config unless the file is regenerated
afterwards.
This commit is contained in:
3
.gitignore
vendored
3
.gitignore
vendored
@@ -29,6 +29,9 @@ systemd/
|
||||
|
||||
# Let's Encrypt state written by certbot (contains private keys — never commit)
|
||||
nginx/certbot/
|
||||
# Generated per deployment by setup_nginx_config() from the .template files,
|
||||
# with the domain substituted in — deployment state, not source.
|
||||
nginx/conf.d/pvemanager.conf
|
||||
|
||||
# Environment
|
||||
.env
|
||||
|
||||
Reference in New Issue
Block a user