{"html_url": "https://github.com/simonw/datasette/issues/514#issuecomment-504686266", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/514", "id": 504686266, "node_id": "MDEyOklzc3VlQ29tbWVudDUwNDY4NjI2Ng==", "user": {"value": 7936571, "label": "chrismp"}, "created_at": "2019-06-22T17:58:50Z", "updated_at": "2019-06-23T21:21:57Z", "author_association": "NONE", "body": "@russss \r\n\r\nActually, here's what I've got in `/etc/systemd/system/datasette.service`\r\n\r\n```\r\n[Unit]\r\nDescription=Datasette\r\nAfter=network.target\r\n\r\n[Service]\r\nType=simple\r\nUser=chris\r\nWorkingDirectory=/home/chris/digital-library\r\nExecStart=/home/chris/Env/datasette/lib/python3.7/site-packages/datasette serve -h 0.0.0.0 databases/*.db --cors --metadata metadata.json\r\nRestart=on-failure\r\n\r\n[Install]\r\nWantedBy=multi-user.target\r\n```\r\n\r\nI ran: \r\n```\r\n$ sudo systemctl daemon-reload\r\n$ sudo systemctl enable datasette\r\n$ sudo systemctl start datasette\r\n```\r\nThen I ran:\r\n`$ journalctl -u datasette -f`\r\n\r\nGot this message.\r\n\r\n```\r\nHint: You are currently not seeing messages from other users and the system.\r\n      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.\r\n      Pass -q to turn off this notice.\r\n-- Logs begin at Thu 2019-06-20 00:05:23 CEST. --\r\nJun 22 19:55:57 ns331247 systemd[16176]: datasette.service: Failed to execute command: Permission denied\r\nJun 22 19:55:57 ns331247 systemd[16176]: datasette.service: Failed at step EXEC spawning /home/chris/Env/datasette/lib/python3.7/site-packages/datasette: Permission denied\r\nJun 22 19:55:57 ns331247 systemd[16184]: datasette.service: Failed to execute command: Permission denied\r\nJun 22 19:55:57 ns331247 systemd[16184]: datasette.service: Failed at step EXEC spawning /home/chris/Env/datasette/lib/python3.7/site-packages/datasette: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16186]: datasette.service: Failed to execute command: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16186]: datasette.service: Failed at step EXEC spawning /home/chris/Env/datasette/lib/python3.7/site-packages/datasette: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16190]: datasette.service: Failed to execute command: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16190]: datasette.service: Failed at step EXEC spawning /home/chris/Env/datasette/lib/python3.7/site-packages/datasette: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16191]: datasette.service: Failed to execute command: Permission denied\r\nJun 22 19:55:58 ns331247 systemd[16191]: datasette.service: Failed at step EXEC spawning /home/chris/Env/datasette/lib/python3.7/site-packages/datasette: Permission denied\r\n```\r\nWhen I go to the address for my server, I am met with the standard \"Welcome to nginx\" message:\r\n\r\n```\r\nWelcome to nginx!\r\nIf you see this page, the nginx web server is successfully installed and working. Further configuration is required.\r\n\r\nFor online documentation and support please refer to nginx.org.\r\nCommercial support is available at nginx.com.\r\n\r\nThank you for using nginx.\r\n```", "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}
{"html_url": "https://github.com/simonw/datasette/issues/514#issuecomment-504685187", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/514", "id": 504685187, "node_id": "MDEyOklzc3VlQ29tbWVudDUwNDY4NTE4Nw==", "user": {"value": 7936571, "label": "chrismp"}, "created_at": "2019-06-22T17:43:24Z", "updated_at": "2019-06-22T17:43:24Z", "author_association": "NONE", "body": "> > > WorkingDirectory=/path/to/data\r\n> > \r\n> > \r\n> > @russss, Which directory does this represent?\r\n> \r\n> It's the working directory (cwd) of the spawned process. In this case if you set it to the directory your data is in, you can use relative paths to the db (and metadata/templates/etc) in the `ExecStart` command.\r\n\r\nIn my case, on a remote server, I set up a virtual environment in `/home/chris/Env/datasette`, and when I activated that environment I ran `pip install datasette`. \r\n\r\nMy datasette project is in `/home/chris/datatsette-project`, so I guess I'd use that directory in the `WorkingDirectory` parameter?\r\n\r\nAnd the `ExecStart` parameter would be `/home/chris/Env/datasette/lib/python3.7/site-packages/datasette serve -h 0.0.0.0 my.db` I'm guessing?\r\n ", "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}
{"html_url": "https://github.com/simonw/datasette/issues/514#issuecomment-504684709", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/514", "id": 504684709, "node_id": "MDEyOklzc3VlQ29tbWVudDUwNDY4NDcwOQ==", "user": {"value": 7936571, "label": "chrismp"}, "created_at": "2019-06-22T17:36:25Z", "updated_at": "2019-06-22T17:36:25Z", "author_association": "NONE", "body": "> WorkingDirectory=/path/to/data\r\n\r\n@russss, Which directory does this represent?", "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}