issue_comments

Table actions

13 rows where "updated_at" is on date 2019-07-08 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, reactions, updated_at (date)

These facets timed out: user

author_association 2

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
509431603 https://github.com/simonw/datasette/issues/514#issuecomment-509431603 https://api.github.com/repos/simonw/datasette/issues/514 MDEyOklzc3VlQ29tbWVudDUwOTQzMTYwMw== chrismp 7936571 2019-07-08T23:39:52Z 2019-07-08T23:39:52Z NONE

In datasette.service, I edited

User=chris

To...

User=root

It worked. I can access http://my-server.com. I hope this is safe. Thanks for all the help, everyone.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation with recommendations on running Datasette in production without using Docker 459397625  
509280196 https://github.com/simonw/datasette/issues/510#issuecomment-509280196 https://api.github.com/repos/simonw/datasette/issues/510 MDEyOklzc3VlQ29tbWVudDUwOTI4MDE5Ng== simonw 9599 2019-07-08T15:44:50Z 2019-07-08T15:44:50Z OWNER

Part of #551 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Ability to facet by delimiter (e.g. comma separated fields) 456569067  
509279790 https://github.com/simonw/datasette/issues/531#issuecomment-509279790 https://api.github.com/repos/simonw/datasette/issues/531 MDEyOklzc3VlQ29tbWVudDUwOTI3OTc5MA== simonw 9599 2019-07-08T15:43:57Z 2019-07-08T15:43:57Z OWNER

Including foreign keys here will let me build a plugin for visualizing table relationships based on https://observablehq.com/@d3/force-directed-graph

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 /database/-/inspect 462117311  
509278616 https://github.com/simonw/datasette/issues/553#issuecomment-509278616 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3ODYxNg== simonw 9599 2019-07-08T15:41:05Z 2019-07-08T15:41:55Z OWNER

Having a "more link" is very interesting. I could do that by generating a custom SQL query link, but that wouldn't play well in instances that disable custom SQL.

This may be a case where a new URL is needed under the proposed /database/table/-/namespace namespace - #296

Compatibility with datasette-vega is useful, since then anyone can get a chart by starting with a facet of some sort.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  
509277853 https://github.com/simonw/datasette/issues/553#issuecomment-509277853 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3Nzg1Mw== simonw 9599 2019-07-08T15:39:08Z 2019-07-08T15:39:15Z OWNER

My reply on Twitter:

https://twitter.com/simonw/status/1148254258900262913

Huh I hadn't thought about order-by-date - that's really useful. Not sure what I'll do for data that's spread over e.g. 1,000 days (other facets only return up to 30 data points right now) - maybe 30 most recent plus a link to view more than that?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  
509277577 https://github.com/simonw/datasette/issues/553#issuecomment-509277577 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3NzU3Nw== simonw 9599 2019-07-08T15:38:26Z 2019-07-08T15:38:26Z OWNER

One thing that's clear is I need to add a demo to the fixtures that illustrates the feature, ideally with a thousand generated rows in it to give a better example of how it works.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  
509154312 https://github.com/simonw/datasette/issues/514#issuecomment-509154312 https://api.github.com/repos/simonw/datasette/issues/514 MDEyOklzc3VlQ29tbWVudDUwOTE1NDMxMg== JesperTreetop 4363711 2019-07-08T09:36:25Z 2019-07-08T09:40:33Z NONE

@chrismp: Ports 1024 and under are privileged and can usually only be bound by a root or supervisor user, so it makes sense if you're running as the user chris that port 8000 works but 80 doesn't.

See this generic question-and-answer and this systemd question-and-answer for more information about ways to skin this cat. Without knowing your specific circumstances, either extending those privileges to that service/executable/user, proxying them through something like nginx or indeed looking at what the nginx systemd job has to do to listen at port 80 all sound like good ways to start.

At this point, this is more generic systemd/Linux support than a Datasette issue, which is why a complete rando like me is able to contribute anything. 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Documentation with recommendations on running Datasette in production without using Docker 459397625  
509067403 https://github.com/simonw/datasette/issues/549#issuecomment-509067403 https://api.github.com/repos/simonw/datasette/issues/549 MDEyOklzc3VlQ29tbWVudDUwOTA2NzQwMw== simonw 9599 2019-07-08T03:36:45Z 2019-07-08T03:36:45Z OWNER

Pull request sent.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Send pull request to the repo that the _table.html template will break 465001185  
509066738 https://github.com/simonw/datasette/issues/547#issuecomment-509066738 https://api.github.com/repos/simonw/datasette/issues/547 MDEyOklzc3VlQ29tbWVudDUwOTA2NjczOA== simonw 9599 2019-07-08T03:31:54Z 2019-07-08T03:31:54Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Release notes for 0.29 464990184  
509066513 https://github.com/simonw/datasette/issues/478#issuecomment-509066513 https://api.github.com/repos/simonw/datasette/issues/478 MDEyOklzc3VlQ29tbWVudDUwOTA2NjUxMw== simonw 9599 2019-07-08T03:30:41Z 2019-07-08T03:30:41Z OWNER

This worked as intended - thanks @glasnt!

https://travis-ci.org/simonw/datasette/builds/555580006

The release has been deployed to PyPI even while the Docker image is still being built.

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 1,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Make it so Docker build doesn't delay PyPI release 445868234  
509051355 https://github.com/simonw/datasette/issues/552#issuecomment-509051355 https://api.github.com/repos/simonw/datasette/issues/552 MDEyOklzc3VlQ29tbWVudDUwOTA1MTM1NQ== simonw 9599 2019-07-08T01:47:30Z 2019-07-08T01:47:30Z OWNER

This is a good opportunity to clean up some duplicate code too. This code is duplicated in a few places:

https://github.com/simonw/datasette/blob/741760d05c6836396756ff6be44a4d375a83a06f/datasette/publish/heroku.py#L65-L87

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Add --plugin-secret support to "datasette package" 465019882  
509050775 https://github.com/simonw/datasette/pull/544#issuecomment-509050775 https://api.github.com/repos/simonw/datasette/issues/544 MDEyOklzc3VlQ29tbWVudDUwOTA1MDc3NQ== simonw 9599 2019-07-08T01:43:15Z 2019-07-08T01:43:15Z OWNER

Deployed the Cloud Run demo like this: datasette publish cloudrun fixtures.db \ --branch=master \ --install=datasette-auth-github \ -n datasette-auth-demo \ --service datasette-auth-demo \ --show-files \ --plugin-secret datasette-auth-github client_id 7524167294949f7886fc \ --plugin-secret datasette-auth-github client_secret ... https://datasette-auth-demo-j7hipcg4aq-uc.a.run.app/

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 --plugin-secret option 464894812  
509042334 https://github.com/simonw/datasette/issues/498#issuecomment-509042334 https://api.github.com/repos/simonw/datasette/issues/498 MDEyOklzc3VlQ29tbWVudDUwOTA0MjMzNA== chrismp 7936571 2019-07-08T00:18:29Z 2019-07-08T00:18:29Z NONE

@simonw I made this primitive search that I've put in my Datasette project's custom templates directory: https://gist.github.com/chrismp/e064b41f08208a6f9a93150a23cf7e03

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Full text search of all tables at once? 451513541  

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]);