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

gwc - provided configuration assumes postgresql hostname to be "database" #16

Open
pmauduit opened this issue Dec 23, 2022 · 3 comments

Comments

@pmauduit
Copy link
Member

pmauduit commented Dec 23, 2022

Introduced with #14, this leads to some questions which wheren't an issue when previously using h2 db:

  • shall we have a seperate branch considering docker (compose) vs non docker setups in this repository ?
  • In a kubernetes context, it won't probably be valid either
  • do we consider this repo as an example that has to be adapted anyway ?
@fvanderbiest
Copy link
Member

We currently provide this datadir with 2 flavors (geofence / native security), for each major geOrchestra release.
I think it would complicate things a lot if we were to take into account all deployment possibilities with branches.
Instead, I think the deployment should take care of updating the provided files to their needs (eg geoserver running on docker does it here: https://github.com/georchestra/georchestra/blob/master/geoserver/webapp/src/docker/docker-entrypoint.d/00-geoserver-bootstrap

@fvanderbiest
Copy link
Member

By default though, this repository should not assume we're running on docker but on a plain old "standard" install like the one we provide instructions for on https://github.com/georchestra/georchestra/blob/master/docs/setup.md.
As a result, the provided GWC config should not use "database" as db host by default.

@fvanderbiest
Copy link
Member

Good catch ! Thanks Pierre

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

No branches or pull requests

2 participants