Running STAC Browser with URL at startup breaks on links to items

[alexgleith]

I'm running STAC Browser and using the entrypoint to configure a starting STAC API, like this:

          env:
            - name: SB_catalogUrl
              value: "https://stac-api.staging.digitalearthpacific.org"

This works great, it loads up and clicking around works fine.

But, if I follow the links to an item, like this https://stac-browser.staging.digitalearthpacific.org/collections/dep_ls_wofs/items/dep_ls_wofs_TV_008_2022_mean and copy and paste that into a browser, I get this error:

The console logs this:

Uncaught SyntaxError: Unexpected token '<' (at config.js:1:1)

It's trying to parse HTML as JSON, for some reason...

Any ideas what's going on?

[alexgleith]

Self links are fine, I think: https://stac-api.staging.digitalearthpacific.org/collections/dep_ls_wofs/items/dep_ls_wofs_VU_016_2022_mean

I guess you're right, we need to set up the web server in the Dockerfile so that it handles the SPA properly: https://github.com/radiantearth/stac-browser/blob/main/Dockerfile

I can mess around the the Nginx config tomorrow.

[m-mohr]

I thought I had it 3 times, but it was never really the issue. So no, I don't have a clue right now. I'd need to dig deeper for it but don't really have the time for it (STAC Browser is unfunded).

It requests from https://stac-browser.staging.digitalearthpacific.org/collections/dep_ls_wofs/items/collections/dep_ls_wofs/items/collections/dep_ls_wofs/items/dep_ls_wofs_TV_008_2022_mean, which looks like the catalogUrl doesn't really gets applied on reload?! But really just guessing, I have no real indication for what it could be right now. Could also be the rewrite, but I thought we had it added to the Dockerfile recently.

The other issue is that I also don't manage the Docker stuff, it's others that maintain that. I'm not using Docker myself.

[alexgleith]

Yeah, it seems the catalog URL isn't loaded. Or that something is attempted before the right JS is loaded... maybe an async race?

[m-mohr]

Could be. The config in Docker as it is right now is new and pretty untested. I'm not using Docker myself, so can't help with it. Maybe provide the config via the config.js file instead of via env variables. If that helps, I'd assume a race condition indeed.

[alexgleith]

I'm going to wait until someone complains and then dive in and tackle it! Hash-based routing will probably sort it. Maybe nginx config changes in the Dockefile. Will get to it one day.