SSWConsulting / SSWConsulting/SSW.Walrus
Serve the dashboards from a custom SSW domain (optional)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 21m
- Merged PRs (30d)
- 1
Description
Problem
Dashboards are served from the raw storage static-website host (https://sawalrusstagingweb.z8.web.core.windows.net/{survey}/). A branded SSW domain would read better in the result email.
Goal
(Optional / nice-to-have) Serve the reports from a custom SSW domain.
Acceptance criteria
- A domain chosen (e.g.
walrus.ssw.com.au) and DNS delegated. - Fronted via Azure Front Door / CDN with managed TLS over the
$webcontainer. -
DASHBOARD_BASE_URLupdated soDEPLOYED_URL+ the email link + the web-root logo use the custom domain. - Existing survey URLs still resolve (or are acceptably broken, since each week is new).
Notes
- Low priority — not required for the migration. Purely cosmetic; the raw host works fine.
- Depends on the Azure move.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the Azure move and the configuration for DASHBOARD_BASE_URL, DEPLOYED_URL, the email link, and the web-root logo. Review how the $web container is currently exposed, then investigate Azure Front Door or CDN, DNS delegation, and managed TLS. Done means a chosen SSW domain serves the dashboards and all generated links use it, while existing survey URLs are handled according to the stated criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100