Closed eloiferrer closed 3 weeks ago
With the current configuration, the prefixes.conf for the production server are applied by default when one runs portal-compose locally.
This is problematic because volumes cannot be deleted in docker-compose.override.yml once they have been declared in docker-compose.yml as in https://github.com/MaRDI4NFDI/portal-compose/blob/8c7d284ba87f2ccc1f0f34da829bb083b52808b0/docker-compose.yml#L213
Instead of declaring an additional prefixes.conf file for development, I think it is better to move back prefixes.conf into the configuration for the production server in srv-mardi02.
Changes:
Instructions for PR review:
Checklist for this PR:
See https://github.com/MaRDI4NFDI/portal-compose/pull/538/files
MaRDI Pull Request
With the current configuration, the prefixes.conf for the production server are applied by default when one runs portal-compose locally.
This is problematic because volumes cannot be deleted in docker-compose.override.yml once they have been declared in docker-compose.yml as in https://github.com/MaRDI4NFDI/portal-compose/blob/8c7d284ba87f2ccc1f0f34da829bb083b52808b0/docker-compose.yml#L213
Instead of declaring an additional prefixes.conf file for development, I think it is better to move back prefixes.conf into the configuration for the production server in srv-mardi02.
Changes:
Instructions for PR review:
Checklist for this PR: