Update instraction after installation path changes

[hug-dev]

See parallaxsecond/parsec#250 for details. Very early version now just for early feedback.

[ionut-arm]

🙆‍♂️ thanks!

[ionut-arm]

See comments below, but I'm ok with the changes.

I'm curious about /etc/parsec having 700 permissions - all the /etc subdirectories on my WSL have at least read or execute for everyone else 😬

[ionut-arm]

Sorry if this is a bit late - would you mind adding bulletpoints to this list? Something like:

• /var/lib/parsec for storing persistent data like the mappings folder. The service will run from
  here

sudo mkdir /var/lib/parsec
sudo chown parsec /var/lib/parsec
sudo chmod 700 /var/lib/parsec

It reads a bit weirdly if you forget this is supposed to be a list

[hug-dev]

Yes good point! Will change.

[ionut-arm]

Cheers 😅

[hug-dev]

I'm curious about /etc/parsec having 700 permissions - all the /etc subdirectories on my WSL have at least read or execute for everyone else 😬

That's true it's similar on my Fedora system. I applied the principle of least privilege, as in I don't think users other than parsec need to know what is inside that file (especially if you have confidential information contained in the configuration file name itself). But if it's not Unix-idiomatic I am happt to change, now or in the future.

[ionut-arm]

I'm curious about /etc/parsec having 700 permissions - all the /etc subdirectories on my WSL have at least read or execute for everyone else 😬

That's true it's similar on my Fedora system. I applied the principle of least privilege, as in I don't think users other than parsec need to know what is inside that file (especially if you have confidential information contained in the configuration file name itself). But if it's not Unix-idiomatic I am happt to change, now or in the future.

I'd rather be secure than idiomatic, especially since config.toml will contain some pretty sensitive stuff. If someone thinks we're doing things wrong, we can reconsider it