{"html_url": "https://github.com/simonw/datasette/issues/498#issuecomment-509042334", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/498", "id": 509042334, "node_id": "MDEyOklzc3VlQ29tbWVudDUwOTA0MjMzNA==", "user": {"value": 7936571, "label": "chrismp"}, "created_at": "2019-07-08T00:18:29Z", "updated_at": "2019-07-08T00:18:29Z", "author_association": "NONE", "body": "@simonw I made this primitive search that I've put in my Datasette project's custom templates directory: https://gist.github.com/chrismp/e064b41f08208a6f9a93150a23cf7e03", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 451513541, "label": "Full text search of all tables at once?"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/514#issuecomment-509154312", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/514", "id": 509154312, "node_id": "MDEyOklzc3VlQ29tbWVudDUwOTE1NDMxMg==", "user": {"value": 4363711, "label": "JesperTreetop"}, "created_at": "2019-07-08T09:36:25Z", "updated_at": "2019-07-08T09:40:33Z", "author_association": "NONE", "body": "@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.\r\n\r\nSee [this generic question-and-answer](https://superuser.com/questions/710253/allow-non-root-process-to-bind-to-port-80-and-443) and [this systemd question-and-answer](https://stackoverflow.com/questions/40865775/linux-systemd-service-on-port-80) 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.\r\n\r\nAt 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. ", "reactions": "{\"total_count\": 1, \"+1\": 1, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 459397625, "label": "Documentation with recommendations on running Datasette in production without using Docker"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/514#issuecomment-509431603", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/514", "id": 509431603, "node_id": "MDEyOklzc3VlQ29tbWVudDUwOTQzMTYwMw==", "user": {"value": 7936571, "label": "chrismp"}, "created_at": "2019-07-08T23:39:52Z", "updated_at": "2019-07-08T23:39:52Z", "author_association": "NONE", "body": "In `datasette.service`, I edited\r\n\r\n```\r\nUser=chris\r\n```\r\n\r\nTo...\r\n\r\n```\r\nUser=root\r\n```\r\n\r\nIt worked. I can access `http://my-server.com`. I hope this is safe. Thanks for all the help, everyone.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 459397625, "label": "Documentation with recommendations on running Datasette in production without using Docker"}, "performed_via_github_app": null}