Elaborate on a detail and remove a redundant line.
This commit is contained in:
parent
0b0b2d5649
commit
d3517ea24d
@ -236,7 +236,7 @@ If systemd gives you no permission errors, then make sure you `chown`, `chgrp` a
|
||||
|
||||
You will first want to follow the instructions in the section for updating dependencies.
|
||||
|
||||
The update system is currently under development, but you can run `dev-update.bat` or `quick-update-linux` to update your instance to the latest commit and to update the associated database schema, etc.
|
||||
The update system is currently under development, but you can run `dev-update.bat` or `quick-update-linux` in `/home/gosora/src`to update your instance to the latest commit and to update the associated database schema, etc.
|
||||
|
||||
|
||||
If you're logged in as `root`, then you might want to switch to the `gosora` user with `su gosora`, you can switch back by typing `exit`.
|
||||
@ -249,8 +249,6 @@ Replace that name and email with whatever you like. This name and email only app
|
||||
|
||||
If you get an access denied error, then you might need to run `chown -R gosora /home/gosora` and `chgrp -R www-data /home/gosora` to fix the ownership of the files.
|
||||
|
||||
In addition to this, you can update the dependencies without updating Gosora by running `update-deps.bat` or `./update-deps-linux` (.bat is for Windows, the other for Linux as the names would suggest).
|
||||
|
||||
If you want to manually patch Gosora rather than relying on the above scripts to do it, you'll first have to create a copy of `./schema/schema.json` named `./schema/lastSchema.json`, and then, you'll overwrite the files with the new ones.
|
||||
|
||||
After that, you'll need to run `go build ./patcher` on Windows or the following code block on Linux:
|
||||
|
Loading…
Reference in New Issue
Block a user