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.

Sign up for GitHub

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

Jump to bottom

[Regression] GEOSERVER_PUBLIC_LOCATION is not set properly in a docker deployment #3893

Closed
francbartoli opened this issue Sep 5, 2018 · 0 comments
Closed

[Regression] GEOSERVER_PUBLIC_LOCATION is not set properly in a docker deployment #3893

francbartoli opened this issue Sep 5, 2018 · 0 comments
Assignees
@francbartoli
Labels
blocker Critical issue blocking next major release and/or (People are badly blocked with no workaround) regression Issues related to regressions.

Comments

@francbartoli
Copy link
Member

It is maintaining the default value GEOSERVER_PUBLIC_LOCATION=http://geonode/geoserver/ regardless GEONODE_LB_HOST_IP and GEONODE_LB_PORT are set or not
@francbartoli francbartoli mentioned this issue Sep 5, 2018
Closed
@francbartoli francbartoli self-assigned this Sep 5, 2018
@francbartoli francbartoli added the blocker Critical issue blocking next major release and/or (People are badly blocked with no workaround) label Sep 5, 2018
@francbartoli francbartoli changed the title GEOSERVER_PUBLIC_LOCATION is not set properly in a docker deployment [Regression] GEOSERVER_PUBLIC_LOCATION is not set properly in a docker deployment Sep 5, 2018
@afabiani afabiani added the regression Issues related to regressions. label Sep 5, 2018
francbartoli added a commit to francbartoli/geonode that referenced this issue Sep 6, 2018
@francbartoli
Revert "Fix GeoNode#3893 "
4340b3d 
This reverts commit eb3081b.
francbartoli added a commit to francbartoli/geonode that referenced this issue Sep 6, 2018
@francbartoli
Fix GeoNode#3893
8c18da9 
* Remove duplicates from allowed_hosts

* Fix GeoNode#3893
francbartoli added a commit that referenced this issue Sep 6, 2018
@francbartoli
Revert and then apply Fix #3893 again (#3903)
c8182e7 
* Revert "Fix #3893 "

This reverts commit eb3081b.

* Fix #3893

* Remove duplicates from allowed_hosts

* Fix #3893
francbartoli added a commit that referenced this issue Sep 6, 2018
@francbartoli
[2.7.x] Backport issue #3893 (#3904)
66e3c7e 
* Backport #3903

* Fix migrate issue during build with no inputs
afabiani pushed a commit that referenced this issue Sep 7, 2018
@francbartoli
Fix #3893
c9a78a9 
* Remove duplicates from allowed_hosts

* Fix #3893
afabiani pushed a commit that referenced this issue Sep 7, 2018
@francbartoli
Revert and then apply Fix #3893 again (#3903)
c96584f 
* Revert "Fix #3893 "

This reverts commit eb3081b.

* Fix #3893

* Remove duplicates from allowed_hosts

* Fix #3893
@afabiani afabiani modified the milestone: 2.10 Jun 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@francbartoli francbartoli

Labels
blocker Critical issue blocking next major release and/or (People are badly blocked with no workaround) regression Issues related to regressions.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@francbartoli @afabiani