As a manager, I want the S3-browser to be deployable and accessible from a '/some_path' URL

[tloubrieu-jpl]

Checked for duplicates

Yes - I've already checked

🧑‍🔬 User Persona(s)

Engineering Node system administration and overall path organization.

💪 Motivation

...so that I can the s3-browser can share a domain name with other applications, e.g.

• main web site: https://pds.nasa.gov
• api: https://pds.nasa.gov/api
• s3-browser: https://pds.nasa.gov/data

📖 Additional Details

Currently, the application only works if accessible from / for example https://data.pds.nasa.gov We would like to make the application work from a deployment like https://dwfmsppt3a750.cloudfront.net/data/ (in Dev)

Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

No response

🎉 I&T

No response

[eddiesarevalo]

@anilnatha @tloubrieu-jpl I added an environment variable to the webpack config so that the string matching will be what is set. For example here:

It will get it from the webpack config

So in the built code it looks like "/data/"==location.pathname

The problem now is the url itself. For example https://dwfmsppt3a750.cloudfront.net/data/catalina-sky-survey/ Going to this url will attempt to open that location so the javascript will never run. Static website host used to cover this part but now we need a non-javascript solution. We could set a cloudfront function to reroute anything /data/* to /data/ or maybe we can do what @anilnatha mentioned and make some sort of proxy.

[jordanpadams]

Status: @eddiesarevalo is blocked by cloudfront function. code should be updated and ready for this.

[tloubrieu-jpl]

That works perfectly on our MCP Dev account.

[jordanpadams]

Skipping I&T. Tested via inspection during website deployment