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

Postgres support broken #161

Closed
juliusknorr opened this issue Mar 16, 2023 · 6 comments
Closed

Postgres support broken #161

juliusknorr opened this issue Mar 16, 2023 · 6 comments
Labels

Comments

@juliusknorr
Copy link
Owner

No description provided.

@zak39
Copy link
Collaborator

zak39 commented Mar 20, 2023

I have the same issue for me

@juliusknorr
Copy link
Owner Author

We need to figure out a way that we can dynamically create new databases named by the instance that is starting as it is done with mysql.

We may need to create a user with the relevant permissions or the individual databases manually through https://github.com/docker-library/docs/blob/master/postgres/README.md#initialization-scripts

@juliusknorr
Copy link
Owner Author

Possibly related nextcloud/server#38750

@juliusknorr
Copy link
Owner Author

https://github.com/nextcloud/all-in-one/blob/main/Containers/postgresql/init-user-db.sh and https://github.com/nextcloud/all-in-one/blob/46f4136d30315d8538c6de29821bcd496ac0c1c5/Containers/postgresql/Dockerfile#L21 as reference

If possible I'd like to avoid to pressed databases as previously creating individual ones per stable container worked nicely.

@juliusknorr
Copy link
Owner Author

Turns out it was enough to just disable user creation using nextcloud/server#36428 and just use the superuser which is fine here since this is a insecure dev env anyways.

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

No branches or pull requests

3 participants