It's not really a problem and we can keep it like this but while investigating failing deployment of contrib, I found it weird that git status gave a not clean folder and I got a bit confused.
In fact, the deployment process
- creates a
pm2.config.cjs file
- creates a
.env file
- replace the name of package-lock with the name of the folder
that are then not versioned files in git.
This could be fixed if need be by
- adding a
.gitignore (either in declarations repo or through ansible by appending those rules to existing ones)
- changing the name inside
package-lock.json of declarations repo with ${instance} instead of ${instance}-declarations
It's not really a problem and we can keep it like this but while investigating failing deployment of contrib, I found it weird that
git statusgave a not clean folder and I got a bit confused.In fact, the deployment process
pm2.config.cjsfile.envfilethat are then not versioned files in git.
This could be fixed if need be by
.gitignore(either in declarations repo or through ansible by appending those rules to existing ones)package-lock.jsonof declarations repo with${instance}instead of${instance}-declarations