You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some changes that I think might affect the YNH build.
You can now specify a LIMA_LABS_TOKEN API token from https://maps.lima-labs.com/ to enable the new Lima Labs default map style.
The app backend now needs to be aware of its own URL for some functionality. There are different ways how FacilMap can detect the base URL:
Either it auto-detects it from the Host header
Or it detects it from the X-Forwarded-* headers. For this to work, TRUST_PROXY needs to be true or a comma-separated list of trusted IP subnets.
Or the base URL is specified manually using BASE_URL.
I don't know the details of how the YNH reverse proxy works, but usually I would say that option 2 is the most suitable one. You can test whether the configuration works by running curl https://facilmap.org/_app/opensearch.xml (under whatever URL your FacilMap runs) and see whether the right base URL is returned in <moz:SearchForm>.
The text was updated successfully, but these errors were encountered:
FacilMap 4.0.0 has been released.
There are some changes that I think might affect the YNH build.
You can now specify a
LIMA_LABS_TOKEN
API token from https://maps.lima-labs.com/ to enable the new Lima Labs default map style.The app backend now needs to be aware of its own URL for some functionality. There are different ways how FacilMap can detect the base URL:
Host
headerX-Forwarded-*
headers. For this to work,TRUST_PROXY
needs to betrue
or a comma-separated list of trusted IP subnets.BASE_URL
.I don't know the details of how the YNH reverse proxy works, but usually I would say that option 2 is the most suitable one. You can test whether the configuration works by running
curl https://facilmap.org/_app/opensearch.xml
(under whatever URL your FacilMap runs) and see whether the right base URL is returned in<moz:SearchForm>
.The text was updated successfully, but these errors were encountered: