Figure out how to use Firebase with cloudrun to enable vanity URLs and CDN caching
Open
Nobody has claimed this yet.
datasette-publish
medium
- Dominant language
- Python
- Stars
- 11.5k
- Forks
- 904
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 18
Description
It looks like Firebase can solve a couple of problems with the existing datasette publish cloudrun hosting mechanism:
- The URLs it produces aren't pretty enough. Firebase offers more control over vanity URLs.
- CDN caching (as seen in
datasette publish now) is great for improving performance and saving money on Cloud Run execution time.
https://firebase.google.com/docs/hosting/cloud-run looks like it can help with both of these.
Lots of interesting questions:
- Should this be a new
datasette publish firebasecommand or should it instead be implemented as additional custom options todatasette publish cloudrun? - How much harder does it become to do account setup?
- How much will this option cost users?
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
Start with the Firebase Hosting for Cloud Run documentation linked in the issue, then inspect the existing datasette publish cloudrun entry point. Determine whether Firebase integration belongs in a new publish command or custom Cloud Run options, and document the account setup, CDN caching, vanity URL, and cost implications as the definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, google-cloud
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100