Status: In Progress
Fix Version/s: None
The RSP is being deployed at multiple sites.
While this would be easy to change in a fork, or in an entirely custom site-specific application, it would be simpler for the remote sites, and (I suspect) possibly less likely to produce confusion and support requests in deployments, if the server list (and perhaps other application parameters - Firefly calls them "properties") could be overridden via some mechanism layered on top of the Rubin-built container images for the Portal.
Configurations on the Firefly server side of the client-server pair are easier to override in this way because of the ability to set up filesystem contents visible inside the running container at the time the container is started (e.g., via content in Helm charts).
This will undoubtedly be useful beyond the remote-site deployments - it's easy to see how this would be helpful just in managing the O(10) internal deployments and their different features.
Shadowed by https://jira.ipac.caltech.edu/browse/FIREFLY-995 at IPAC.
Copied from that ticket:
[Other] top items for Helm-chart configuration would be:
- The image dataset(s) to be used for context/coverage images
- In particular, the HiPS image to be used, and control over whether or not any source of FITS images is used instead of HiPS when zooming in
- The "curated" list of HiPS image maps available in the "Change HiPS" menu
These items will be essential to be changeable between different Rubin deployments, because:
- The "Data Preview 0" deployment(s) will need to have access to HiPS image maps created and hosted by Rubin and based on simulated data, and coverage images should never zoom in to 2MASS or any other real-sky images
- The Rubin summit-related deployments (e.g., for AuxTel and ComCam) should default to real-sky images
Supported by Firefly 2022.2, currently in pre-release testing on the IDF RSP.
Note that subsequently DM-33531 and DM-34492 have been filed covering essentially the same point.