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

Some fixes for the Docker setup #397

Merged
merged 5 commits into from
Sep 24, 2020
Merged

Conversation

JeanFred
Copy link

Giving an other try at #32, I ran into a couple of issues and here are fixes. Hope this helps!

There is no sudo available in the Docker environment.

Let's just move the `apt-get` call command to a variable,
and override it in Makefile call in the Dockerfile.
There was a breaking change recently in Postgres Docker image:
```
Error: Database is uninitialized and superuser password is not specified.
       You must specify POSTGRES_PASSWORD for the superuser. Use
       "-e POSTGRES_PASSWORD=password" to set it in "docker run".

       You may also use POSTGRES_HOST_AUTH_METHOD=trust to allow all connections
       without a password. This is *not* recommended. See PostgreSQL
       documentation about "trust":
       https://www.postgresql.org/docs/current/auth-trust.html
```

This may not be the best setting, but let's go for this.

See docker-library/postgres#681
Without it, the step `compilemessages` fails.
@JeanFred JeanFred mentioned this pull request Apr 14, 2020
4 tasks
This is one of the few requirements for whitenoise to just work.

See http://whitenoise.evans.io/en/stable/django.html

(This had been done in cdcb34f, but probably lost in a master merge)
@JeanFred
Copy link
Author

JeanFred commented May 5, 2020

Are there concerns with this PR? It would definitely take #32 further along

jgrocho added a commit to jgrocho/mygpo that referenced this pull request Aug 4, 2020
Using (gpodder#32) and
(gpodder#397) as a starting point, we
implement some changes to get mygpo to run correctly under Docker.

To actually make use of this, we need an as-yet-unpublished `Dockerfile`
and `docker-compose.yaml`.
jgrocho added a commit to jgrocho/mygpo that referenced this pull request Aug 4, 2020
Using (gpodder#32) and
(gpodder#397) as a starting point, we
implement some changes to get mygpo to run correctly under Docker.

To actually make use of this, we need an as-yet-unpublished `Dockerfile`
and `docker-compose.yaml`.
@clementsjosh clementsjosh merged commit 06a1b80 into gpodder:docker Sep 24, 2020
@JeanFred
Copy link
Author

Thanks for merging!

@clementsjosh
Copy link

No problem... apologies for it taking so long. I'm trying to catch up with everything and hope to push it to prod soon!

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

Successfully merging this pull request may close these issues.

2 participants