ChilliCream / ChilliCream/graphql-platform
Change Nitro to fetch from CDN in the browser, not the server
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.8k
- Forks
- 810
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 98
Description
Product
Nitro
Is your feature request related to a problem?
When the Nitro app is requested from the server, the server calls out to cdn.chillicream.com (previously cdn.bananacakepop.com). In some environments, this requires these URLs to be explicitly whitelisted for outgoing traffic. This originally caused us some confusion and wasted hours with HotChocolate 13, and now with the latest 14 RC, it caused us some confusion again since the UI stopped working due to switching to cdn.chilicream.com (which we then had to whitelist).
The solution you'd like
Instead of the server fetching the UI from CDN, it would be easier if the browser did it. That would avoid these issues.
Contributor guide
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
No files, tests, or entry points are named in the issue. Start by locating Nitro's current UI/CDN loading path and trace whether the server or browser performs the request. Done means the browser fetches the UI from the CDN and the server no longer makes that outbound request.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100