home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 449445715

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association pull_request body repo type active_lock_reason performed_via_github_app reactions draft state_reason
449445715 MDU6SXNzdWU0NDk0NDU3MTU= 491 Figure out how to use Firebase with cloudrun to enable vanity URLs and CDN caching 9599 open 0     0 2019-05-28T19:48:06Z 2019-05-28T19:48:35Z   OWNER  

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 firebase command or should it instead be implemented as additional custom options to datasette publish cloudrun?
  • How much harder does it become to do account setup?
  • How much will this option cost users?
107914493 issue    
{
    "url": "https://api.github.com/repos/simonw/datasette/issues/491/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   

Links from other tables

  • 2 rows from issues_id in issues_labels
  • 0 rows from issue in issue_comments
Powered by Datasette · Queries took 0.854ms · About: github-to-sqlite