a
/
gosora
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

And don't forget to update the README.

This commit is contained in:
Azareal 2018-08-07 14:57:11 +10:00
parent a3c5601ac7
commit 2fa6659db9
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -67,7 +67,7 @@ On Windows, you might want to try the [GosoraBootstrapper](https://github.com/Az
First, you will need to jump to the place where you want to put the code, we will use `/home/gosora` here, but if you want to use something else, then you'll have to modify the service file with your own path (but *never* in a folder where the files are automatically served by a webserver). First, you will need to jump to the place where you want to put the code, we will use `/home/gosora` here, but if you want to use something else, then you'll have to modify the service file with your own path (but *never* in a folder where the files are automatically served by a webserver).
If you place it in `/www/`, `/public_html/` or any similar folder, then there's a chance that your server might be compromised. If you place it in `/www/`, `/public_html/` or any similar folder, then there's a chance that your server might be compromised. Also, if you do modify the service file and things don't work, then you might want to try putting # in-front of the lines starting with PrivateUsers, PrivateDevices, and ProtectSystem.
You can navigate to it by typing the following six commands into the console and hitting enter: You can navigate to it by typing the following six commands into the console and hitting enter:

2
gosora_example.service
View File

@ -15,7 +15,7 @@ WorkingDirectory=/home/gosora
# Make sure you manually run pre-run-linux before you start the service # Make sure you manually run pre-run-linux before you start the service
ExecStart=/home/gosora/Gosora ExecStart=/home/gosora/Gosora
# Let's hope these don't blow up on me # If things don't work for some reason, try putting # in-front of the following three lines until it does and open an issue on the bug tracker
ProtectSystem=full ProtectSystem=full
PrivateDevices=true PrivateDevices=true
PrivateUsers=true PrivateUsers=true