github Forceu/Gokapi v2.0.0-beta2
v2.0.0-beta2: Custom CSS/JS

latest releases: v2.1.0, v2.0.1, v2.0.0...
pre-release3 months ago

To install this beta with docker, please use the gokapi:latest-dev tag.

Upgrading

⚠️ Make sure that you have a backup of all data! This beta might break your instance. It is not possible to downgrade afterwards

⚠️ If you are upgrading from v1.9.6, please read through the v2.0.0.-beta1 release notes first!

This beta removes the feature from v1.x to use a template or static folder to replace the content of the webserver. This is now replaced with a feature to add custom CSS or JavaScript, which does not replace any code and should not break as easily on updates.
In addition to that, a better logging system has been introduced and some bugs from previous versions were fixed.

Changelog

  • Added API endpoint to delete logs, added more logging, added filtering and deletion of logs in UI
  • Fix email scope not being submitted #234, fix always being redirected after successful OIDC login
  • Fixed sqlite bug for e2e reset
  • Fix DuplicateFile setting hotlink on wrong file object (#246)
  • Fixed bug that prevented setting Manage_Users API permission on new API key
  • Enable experimental hotlinking for videos with env var GOKAPI_ENABLE_HOTLINK_VIDEOS
  • Fix bug where picture files where not uploaded at all when encryption and cloud storage was active as well as SaveToLocal #247
  • Fix that an empty line was inserted before <!doctype html>
  • Make GOKAPI_LENGTH_ID non-permanent, add GOKAPI_LENGTH_HOTLINK_ID to change hotlink ID length #251
  • Hotlink URL are now shorter (#253) @lenisko
  • Allow file deletion without refreshing the page (#255)
  • Other minor fixes and improvements @nilicule

Breaking changes

Upgrading when using custom templates or static content

If you want to change the layout (e.g. add your company logo or add/disable certain features), follow these steps:

  1. Create a new folder named custom where your executable is. When using Docker, mount a new folder to /app/custom/. Any file in this directory will be publicly available in the sub-URL /custom/.
  2. To have custom CSS included, create a file in the folder named custom.css. The CSS will be applied to all pages.
  3. To have custom JavaScript included, create the file public.js for all public pages and/or admin.js for all admin-related pages. Please note that the admin.js will be readable to all users.
  4. In order to prevent caching issues, you can version your files by creating the file version.txt with a version number.
  5. Restart the server. If the folders exist, the server will now add the local files.

Optional: If you require further changes or want to embedded the changes permanently, you can clone the source code and then modify the templates in internal/webserver/web/templates. Afterwards run make to build a new binary with these changes.

Don't miss a new Gokapi release

NewReleases is sending notifications on new releases.