issue_comments

Table actions

1 row where issue = 457201907 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 1 ✖

issue 1

  • Is it possible to publish to Heroku despite slug size being too large? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
503199253 https://github.com/simonw/datasette/issues/513#issuecomment-503199253 https://api.github.com/repos/simonw/datasette/issues/513 MDEyOklzc3VlQ29tbWVudDUwMzE5OTI1Mw== simonw 9599 2019-06-18T15:56:29Z 2019-06-18T15:56:29Z OWNER

Unfortunately not - I really wish this was possible. I have not yet found a great serverless solution for publishing 1GB+ databases - they're too big for Heroku, Cloud Run OR Zeit Now. Once databases get that big the only option I've found is to run a VPS (or an EC2 instance) with a mounted hard drive volume and execute datasette serve on that instance, with an nginx running on port 80 that proxies traffic back to Datasette.

I'd love to figure out a way to make hosting larger databases as easy as it currently is to host small ones.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Is it possible to publish to Heroku despite slug size being too large? 457201907  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);