d9acf27c5b
Added AJAX Pagination for the Topic List and Forum Page. A new log file pair is now created every-time Gosora starts up. Added proper per-theme template overrides. Added EasyJSON to make JSON serialisation faster. Moved a bit of boilerplate into paginator.html Improved paginator.html with a richer template with first, last and symbols instead of text. Phased out direct access to Templates.ExecuteTemplate across the software. Fixed the Live Topic List so it should work again. Added MicroAvatar to WsJSONUser for topic list JSON requests. An instance of the plugin is now passed to plugin handlers rather than having the plugins manipulate the globals directly. Added the pre_render_panel_forum_edit and pre_render_panel_forum_edit_perms hooks to replace pre_render_panel_edit_forum. Renamed the pre_render_panel_edit_user hook to pre_render_panel_user_edit Reduced the amount of noise from fsnotify. Added RawPrepare() to qgen.Accumulator. Added a temporary phrase whitelist to the phrase endpoint. Moved the location of the zone data assignments in the topic list to reduce the chances of security issues in the future. Changed the signature of routes/panel/renderTemplate() requiring some changes across the panel routes. Removed bits of boilerplate in some of the panel routes with renderTemplate() Added a BenchmarkTopicsGuestJSRouteParallelWithRouter benchmark. Removed a fair bit of boilerplate for each page struct by generating a couple of interface casts for each template file instead. Added the profile_comments_row_alt template. Added the topics_quick_topic template to reuse part of the quick topic logic for both the topic list and forum page. Tweaked the CSS for the Online Users Widget. Tweaked the CSS for Widgets in every theme with a sidebar. Refactored the template initialisers to hopefully reduce the amount of boilerplate and make things easier to maintain and follow. Add genIntTmpl in the template initialiser file to reduce the amount of boilerplate needed for the fallback template bindings. Removed the topics_head phrase. Moved the paginator_ phrases into the paginator. namespace and renamed them accordingly. Added the paginator.first_page phrase. Added the paginator.first_page_aria phrase. Added the paginator.last_page phrase. Added the paginator.last_page_aria phrase. Added the panel_forum_delete_are_you_sure phrase. Fixed a data race in LogWarning()
4.7 KiB
Windows Installation
Run install.bat, e.g. double-click on it. You will also have to start-up MySQL, which if you're using Wnmp or friends is just a matter of opening that program and starting the MySQL process via it.
Follow the instructions shown on the screen.
To navigate to the folder the software is in at any time in the future, you can just type cd followed by the folder's name, e.g. cd /home/gosora/src/ and then you can run your commands. cd stands for change directory.
Linux Simple Installation
Simple installations are usually recommended for trying out the software rather than for deploying it in production as they are less hardened and have fewer service facilities.
This might also be fine, if you're using something else as a reverse-proxy (e.g. Nginx or Apache).
First, we need somewhere for the software to live, if you're familiar with Linux, then you might have some ideas of your own, otherwise we may just go for ~/gosora.
First, we'll navigate to our home folder by typing: cd ~
And then, we'll going to pull a copy of Gosora off the git server with: git clone https://github.com/Azareal/Gosora
And now, we're going to rename the downloaded folder from Gosora to gosora because the uppercase letter bugs me with: mv Gosora gosora
We can now hop into that folder with the same command we used for getting to the home folder:
cd gosora
And now, we'll change the permissions on the installer script, otherwise we'll get an access denied error:
chmod 755 ./install-linux
Just run this to run the installer:
./install-linux
Follow the instructions shown on the screen.
Linux Installation with Systemd Service
You will need administrator privileges on the machine (aka root) to add a service.
First, you will need to jump to the place where you want to put the code, we will use /home/gosora/src/ 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.
The following commands will pull the latest copy of Gosora off the Git repository, will create a user account to run Gosora as, will set it as the owner of the files and will start the installation process.
If you're just casually setting up an installation on your own machine which isn't exposed to the internet just to try out Gosora, then you might not need to setup a seperate account for it or do chmod 2775 logs.
Please type the following commands into the console and hit enter:
cd /home/
useradd gosora
passwd gosora
Type in a strong password for the gosora user, please oh please... Don't use "password", just... don't, okay? Also, you might want to note this down somewhere.
mkdir gosora
cd gosora
git clone https://github.com/Azareal/Gosora
mv Gosora src
chown -R gosora ../gosora
chgrp -R www-data ../gosora
cd src
chmod 2775 logs
chmod 755 ./install-linux
./install-linux
Follow the instructions shown on the screen.
We will also want to setup a service:
chmod 755 ./pre-run-linux
cp ./gosora_example.service /lib/systemd/system/gosora.service
systemctl daemon-reload
Advanced Installation
This section explains how to set things up without running the batch or shell files. For Windows, you will likely have to open up cmd.exe (the app called Command Prompt in Win10) to run these commands inside or something similar, while with Linux you would likely use the Terminal or console.
Linux is similar, however you might need to use cd and mv a bit more like in the shell files due to the differences in go build across platforms. Additionally, Linux doesn't require StackExchange/wmi or /x/sys/windows
You also need to substitute the gosora.exe bits for ./Gosora on Linux. For more info, you might want to take a gander inside the ./run-linux and ./install-linux shell files to see how they're implemented.
git clone https://github.com/Azareal/Gosora
go get
rm -f template_*.go
rm -f gen_*.go
rm -f tmpl_client/template_*.go
rm -f ./Gosora
go generate
go build ./router_gen
router_gen.exe
go build ./cmd/query_gen
query_gen.exe
go build -o gosora.exe
go build "./cmd/install"
install.exe
go get github.com/mailru/easyjson/...
easyjson -pkg common
gosora.exe -build-templates
gosora.exe
I'm looking into minimising the number of go gets for the advanced build and to maybe remove the platform and database engine specific dependencies if possible for those who don't need them.
If systemd gives you no permission errors, then make sure you chown, chgrp and chmod the files and folders appropriately.