2296008655
Added the three month time range to the analytics panes. Began work on adding new graphs to the analytics panes. Began work on the ElasticSearch adapter for the search system. Added the currently limited AddKey method to the database adapters. Expanded upon the column parsing logic in the database adapters to ease the use of InsertSelects. Added the BulkGet method to TopicCache. Added the BulkGetMap method to TopicStore. TopicStore methods should now properly retrieve lastReplyBy. Added the panel_analytics_script template to de-dupe part of the analytics logic. We plan to tidy this up further, but for now, it'll suffice. Added plugin_sendmail and plugin_hyperdrive to the continuous integration test list. Tweaked the width and heights of the textareas for the Widget Editor. Added the AddKey method to *qgen.builder Fixed a bug where using the inline forum editor would crash Gosora and wouldn't set the preset permissions for that forum properly. Added DotBot to the user agent analytics. Invisibles should be better handled when they're encountered now in user agent strings. Unknown language ISO Codes in headers now have the requests fully logged for debugging purposes. Shortened some of the pointer receiver names. Shortened some variable names. Added the dotbot phrase. Added the panel_statistics_time_range_three_months phrase. Added gopkg.in/olivere/elastic.v6 as a dependency. You will need to run the patcher or updater for this commit.
58 lines
3.7 KiB
Markdown
58 lines
3.7 KiB
Markdown
# Updating Gosora (Windows)
|
|
|
|
The update system is currently under development, but you can run `dev-update.bat` to update your instance to the latest commit and to update the associated database schema, etc.
|
|
|
|
If you run into any issues doing so, please open an issue: https://github.com/Azareal/Gosora/issues/new
|
|
|
|
If you want to manually patch Gosora rather than relying on the above scripts to do it, you'll first want to save your changes with `git stash`, and then, you'll overwrite the files with the new ones with `git pull origin master`, and then, you can re-apply your custom changes with `git stash apply`
|
|
|
|
After that, you'll need to run `go build ./patcher`.
|
|
|
|
Once you've done that, you just need to run `patcher.exe` to apply the latest patches to the database, etc.
|
|
|
|
# Updating a software with a simple installation (Linux)
|
|
|
|
The update system is currently under development, but you can run `dev-update-linux` to update your instance to the latest commit and to update the associated database schema, etc.
|
|
|
|
If you run into any issues doing so, please open an issue: https://github.com/Azareal/Gosora/issues/new
|
|
|
|
If you want to manually patch Gosora rather than relying on the above scripts to do it, you'll first want to save your changes with `git stash`, and then, you'll overwrite the files with the new ones with `git pull origin master`, and then, you'll re-apply your changes with `git stash apply`.
|
|
|
|
After that, you'll need to run `go build -o Patcher "./patcher"`
|
|
|
|
Once you've done that, you just need to run `./Patcher` to apply the latest patches to the database, etc.
|
|
|
|
|
|
# Updating a software using systemd (Linux)
|
|
|
|
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 `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 run into any issues doing so, please open an issue: https://github.com/Azareal/Gosora/issues/new
|
|
|
|
If you're using a systemd service, then you might want to switch to the `gosora` user with `su gosora` (you may be prompted for the password to the user), you can switch back by typing `exit`.
|
|
If this is the first time you've done an update as the `gosora` user, then you might have to configure Git, simply do:
|
|
|
|
`git config --global user.name "Lalala"`
|
|
`git config --global user.email "lalala@example.com"`
|
|
|
|
Replace that name and email with whatever you like. This name and email only applies to the `gosora` user. If you see a zillion modified files pop-up, then that is due to you changing their permissions, don't worry about it.
|
|
|
|
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` (with the corresponding user you setup for your instance) to fix the ownership of the files.
|
|
|
|
If you want to manually patch Gosora rather than relying on the above scripts to do it, you'll first want to save your changes with `git stash`, and then, you'll overwrite the files with the new ones with `git pull origin master`, and then, you'll re-apply your changes with `git stash apply`.
|
|
|
|
After that, you'll need to run `go build -o Patcher "./patcher"`
|
|
|
|
Once you've done that, you just need to run `./Patcher` to apply the latest patches to the database, etc.
|
|
|
|
|
|
# Updating Dependencies
|
|
|
|
Dependencies are third party scripts and programs which Gosora relies on to function. The instructions here do not cover updating MySQL / MariaDB or Go.
|
|
|
|
You can update them by running the `go get` command.
|
|
|
|
You'll need to restart the server after you change a template or update Gosora, e.g. with `run.bat` or killing the process and running `./run-linux` or via `./pre-run-linux` followed by `service gosora restart`.
|