Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Use docker include instead of docker-compose.override.yml #277

Open
edevosc2c opened this issue Mar 15, 2024 · 1 comment
Open

Comments

@edevosc2c
Copy link
Member

edevosc2c commented Mar 15, 2024

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 main docker-compose.yml file, this would be easier to upgrade to a newer georchestra version, but currently we can't use this functionality.

@edevosc2c 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
@edevosc2c
Copy link
Member Author

edevosc2c commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant