You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker-compose.override.yml was not meant to be used for having multiple docker-compose for the same docker-compose project.
include file could be used for including more Docker compose services in the docker-compose without touching the main docker-compose.yml file, this would be easier to upgrade to a newer georchestra version, but currently we can't use this functionality.
The text was updated successfully, but these errors were encountered:
edevosc2c
changed the title
[Enhancement] Use docker extends instead of docker-compose.override.yml
[Enhancement] Use docker include instead of docker-compose.override.yml
Feb 6, 2025
We could use Docker include to have more services in the docker composition, but without having them enabled by default.
We could say that the main docker-compose is for major services (database, ldap, cas, gateway, header, geoserver, console, geonetwork, datahub, analytics, mapstore, datafeeder, ogc-api-records).
And for web server stuff we have a separate docker-compose file.
Finally, we can have another docker-compose file for optional services like data-api, gaia, superset, metadata-editor and more to come.
I think we should use docker extends functionalities instead of using .override file for having a separate docker-compose.yml: https://docs.docker.com/compose/how-tos/multiple-compose-files/include/
docker-compose.override.yml
was not meant to be used for having multiple docker-compose for the same docker-compose project.include
file could be used for including more Docker compose services in the docker-compose without touching the maindocker-compose.yml
file, this would be easier to upgrade to a newer georchestra version, but currently we can't use this functionality.The text was updated successfully, but these errors were encountered: