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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dockerfile has typo in server proxy uri variable #968

Merged
merged 3 commits into from Sep 9, 2017
Merged

Conversation

begriffs
Copy link
Member

@begriffs begriffs commented Sep 9, 2017

I'm writing docs today and am adding a section to our installation section about running postgrest from docker. I encountered this:

$ docker pull postgrest/postgrest
$ docker run postgrest/postgrest
postgrest: ParseError "" "no such variable \"PGRST_SERVER_PROXY_URI\""

The problem was that the dockerfile was providing a default value for PGRST_SERVER_PROXY_URL instead.

When we merge this our build process will automatically rebuild the :latest tag, right? I guess we'll have to release v4.3.1 as well... 馃槥

Docker always provides it, by default as blank
@begriffs
Copy link
Member Author

begriffs commented Sep 9, 2017

I pushed another commit to ignore the proxy uri if it is present but blank, as it is by default in Docker. Otherwise I get:

$ docker run -e PGRST_SERVER_PROXY_URI="" postgrest/postgrest
postgrest: FatalError {fatalErrorMessage = "Malformed proxy uri, a correct example: https://example.com:8443/basePath"}

@steve-chavez
Copy link
Member

steve-chavez commented Sep 9, 2017

Why not just manually replace the v0.4.3.0/latest docker images with the PGRST_SERVER_PROXY_URI fix now, is not working anyway and I see this more as a flaw of the build process, I think it would be better to leave the version bumping for changes in the PostgREST application codebase. After that we could include this PR commits in v0.4.4.0 with the other recently merged PR's.

@ruslantalpa
Copy link
Contributor

yes, rebuild the docker images manually (both tags, just like the build script) and push. no need for a new version

@begriffs
Copy link
Member Author

begriffs commented Sep 9, 2017

What about my change in Config.hs though?

@ruslantalpa
Copy link
Contributor

that can be a 4.3.1, along with other small changes, it's too small to merit a .1 i think.

@rvernica
Copy link

I just pulled the latest image from Docker Hub and followed the instructions but I still get the Malformed proxy uri error. The Docker Hub image seems to have been pushed 4 days ago. This patch was merged 6 days ago. I guess this patch did not make it into the Docker image.

@abbapappa
Copy link

I tried with postgrest/postgrest:latest (cd5df30b4a7e435aafe9abeac0e4158b98df03182de5bce93823c843293223c1), same result. When can this be merged into master?

@ruslantalpa
Copy link
Contributor

it is in master, :latest does not mean master, it means the latest release, which is 4.3

@abbapappa
Copy link

Sorry, my bad. I did not see it was already merged. I'll await the next release :).

@wolfgangwalther wolfgangwalther deleted the docker-typo branch December 28, 2020 20:43
monacoremo pushed a commit to monacoremo/postgrest that referenced this pull request Jul 17, 2021
* s/URL/URI/ in dockerfile

* Treat blank proxy uri as missing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants