/collections redirecting to bad URL

[TWDBrob]

I set up stac-fastapi-pgstac using the Joplin data and when I go to the /collections endpoint, I get a 404. Note that /collections/joplin/items works fine.

From the docker logs:

INFO: 172.18.0.1:39068 - "GET /api/v1/pgstac/collections/joplin/items HTTP/1.1" 200 OK <-- trying to get all items works fine
INFO: 172.18.0.1:55638 - "GET /api/v1/pgstac/collections/ HTTP/1.1" 307 Temporary Redirect
INFO: 172.18.0.1:55638 - "GET /api/v1/pgstac/api/v1/pgstac/collections HTTP/1.1" 404 Not Found <-- /collections goes to this messed up URL

I have been trying to figure out where the request enters the code (it doesn't reach CoreCrudClient.all_collections), but I've been unsuccessful so far.

[TWDBrob]

The issue turns out to be that the --root-path parameter found in docker-compose.yml:90 is set to /api/v1/pgstac. When I went to the items url, it must have been http://0.0.0.0:8082/collections/joplin/items and not http://0.0.0.0:8082/api/v1/pgstac/collections/joplin/items like I thought it was. Going to http://0.0.0.0:8082/ shows the data link as http://0.0.0.0:8082/api/v1/pgstac/collections and that is what I was pasting into the address bar. Changing it to http://0.0.0.0:8082collections fixed the issue and modifying docker-compose.yml to have the root parameter set to just / changed the links.

That said, is what's found in docker-compose.yml an error?

[vincentsarago]

@TWDBrob What you're seeing is the behavior when we launch the application behind a proxy (nginx).

When you do docker compose up it will launch all services (including nginx) and thus you shouldn't use localhost:8082 port but localhost:8080