From 2216f253c18491b01efce09d00c5f1962dd74c96 Mon Sep 17 00:00:00 2001 From: Leonora Tindall Date: Sat, 19 Nov 2022 03:06:37 -0600 Subject: [docs] Move and document logs (#1076) Rather than a single access log and no error logging, put the logs in /var/log/gotosocial/, and document creating and owning that directory --- docs/installation_guide/binary.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/installation_guide/binary.md') diff --git a/docs/installation_guide/binary.md b/docs/installation_guide/binary.md index 14569bf52..b72790774 100644 --- a/docs/installation_guide/binary.md +++ b/docs/installation_guide/binary.md @@ -4,10 +4,10 @@ This is the binary installation guide for GoToSocial. It is assumed that you alr ## 1: Prepare VPS -In a terminal on the VPS or your homeserver, make the directory that GoToSocial will run from, the directory it will use as storage, and the directory it will store LetsEncrypt certificates in: +In a terminal on the VPS or your homeserver, make the directory that GoToSocial will run from, the directory it will use as storage, the directory it will store LetsEncrypt certificates in, and the directory it will store logs in: ```bash -mkdir /gotosocial && mkdir /gotosocial/storage && mkdir /gotosocial/storage/certs +mkdir /gotosocial && mkdir /gotosocial/storage && mkdir /gotosocial/storage/certs && mkdir /var/log/gotosocial ``` If you don't have root permissions on the machine, use something like `~/gotosocial` instead. @@ -118,7 +118,7 @@ sudo usermod -a -G gotosocial gotosocial Then make them the owner of your GoToSocial installation since they will need to read and write in it. ```bash -sudo chown -R gotosocial:gotosocial /gotosocial +sudo chown -R gotosocial:gotosocial /gotosocial /var/log/gotosocial ``` You can find a `gotosocial.service` file in the `example` folder on [github](https://raw.githubusercontent.com/superseriousbusiness/gotosocial/main/example/gotosocial.service) or your installation. -- cgit v1.2.3