Releases: Forceu/Gokapi
v1.8.0
With this release, the old key-value database was changed to sqlite3. Please backup all Gokapi data before installing this release. On first start, the old database will be migrated and all users will be logged out. If you experience any problems, please open an issue and let us know!
Changelog
- Parameters of already uploaded files can be edited now
- Added permission model for API tokens
- Added
/auth/modifyand/files/modify APIendpoint - Fixed "Powered by Gokapi" URL not clickable
- Fixed the ASCII logo #108 Thanks to @Kwonunn
- Improved UI
- Fixed minor bugs
- Updated dependencies
- Updated documentation
Breaking Changes
- Dropped Windows 32bit support
- Only 4,000 parallel requests that are writing to the database are supported now, any requests above that limit may be rejected. Up to 500,000 parallel reading requests were tested.
- According to the documentation, the
GOKAPI_DATA_DIRenvironment variable should be persistent, however that was not the case. Now the data directory that was set on first start will be used. If you were usingGOKAPI_DATA_DIRafter the first start, make sure that the data directory is the one found in your config file. - By default, IP addresses of clients downloading files are not saved anymore to comply with GDPR. This can be enabled by re-running the setup
- Existing API keys will be granted all API permissions except
MODIFY_API, therefore cannot use/auth/friendlynamewithout having the permission granted first - The undocumented
GOKAPI_FILE_DBenvironment variable was removed - Removed optional application for reading database content
v1.7.2
Changelog
- Added option to change the name in the setup
- The filename is now shown in the title for downloads
- SessionStorage is used instead of localStorage for e2e decryption
- Replaced expiry image with dynamic SVG
Full Changelog: v1.7.1...v1.7.2
v1.7.1
Changelog
- Fixed Gokapi not able to upload when running on a Windows system #95
- Improved Upload UI
- Added healthcheck for docker by @Jisagi in #89
- Fixed upload counter not updating after upload #92
- Fixed hotlink generation on files that required client-side decryption
- Replaced go:generate code with native Go
- Min Go version now 1.20
- Updated dependencies
- A lot of refactoring, minor changes
- Fixed background not loading in 1.7.0 (unpublished release) #101
Full Changelog: v1.6.2...v1.7.1
v1.6.2
v1.6.1
v1.6.0
Changelog
- Use chunked uploads instead of single upload #68
- Add end-to-end encryption #71
- Fixed hotlink not being generated for uploads through API with unlimited storage time
- Added arm64 to Docker latest image
- Added API call to duplicate existing files
- Fixed bug where encrypted files could not be downloaded after rerunning setup
- Port selection is now disabled when running setup with docker
- Added timeout for AWS if endpoint is invalid
- Added flag to disable CORS check on startup
- Service worker for insecure connections is now hosted on Github
- "Noaws" version is not included as binary build anymore, but can be generated manually
Breaking Changes
- API output for fileuploads are less verbose and have changed parameters, please see updated OpenApi documentation
- If you disabled authentication, the following endpoints need to be secured:
- /admin
- /apiDelete
- /apiKeys
- /apiNew
- /delete
- /e2eInfo
- /e2eSetup
- /uploadChunk
- /uploadComplete
Upgrading
- Minimum version for upgrading is 1.5
- Please make a backup before upgrading.
- Remove any custom templates or custom static files
- Optionally run the server with the parameter
--reconfigureto try out the new features.
Please report any issues you have with this release!
Full Changelog: v1.5.2...v1.6.0
v1.5.2
Changelog
- Added ARMv8 (ARM64) to Docker image
- Added option to always store images locally in order to support hotlink for encrypted files
- Fixed crash when remote files exist but system was changed to local files after running
--reconfigure - Added warning if incorrect CORS setting are set for AWS bucket
- Added button in setup to test AWS credentials
- Added more build infos to
--versionoutput - Added download counter
- Added flags for port, config and data location, better flag usage overview
- Fixed that a file was reuploaded to AWS, even if it already existed
- Fixed error image for hotlinks not displaying if
nosniffis enforced - Fixed that two text files were created when pasting text
- Fixed docker image in documentation @emanuelduss
Full Changelog: v1.5.1...v1.5.2
v1.5.1
Changelog
- Fixed that selection of remote storage was not available during intitial setup #50
- Fixed that "bind to localhost" could be selected on docker image during initial setup
- Fixed that with Level 1 encryption remote files were encrypted as well
- If Gokapi is hosted under a https URL, the serviceworker for remote decryption is now included, which fixes that Firefox users with restrictive settings could not download encrypted files from remote storage #49
- Design improvements by @mraif13 #51
Full Changelog: v1.5.0...v1.5.1
v1.5.0
This release contains major changes, please read carefully
Upgrading
- Minimum version for upgrading is 1.3
- Please make a backup before upgrading.
- Remove any custom templates or custom static files
- Optionally run the server with the parameter
--reconfigureto try out the new features.
Changelog
- Encryption support for local and remote files
- Additional authentication methods: Header-Auth, OIDC and Reverse Proxy
- Option to allow unlimited downloads of files
- The configuration file has been partly replaced with a database. After the first start, the configuration file may be read-only
- A web-based setup instead of command line
Please report any issues you have with this release! Especially if you are using the full encryption mode with S3, we are very happy about any feedback.
Full Changelog: v1.3.1...v1.5.0
v1.5.0-beta1 Pre-Release
This is a pre-release, do not use for production
We are happy to release a beta version of 1.5.0, which includes the following:
- Encryption support for local and remote files
- Additional authentication methods: Header-Auth, OIDC and Reverse Proxy
- Option to allow unlimited downloads of files
- The configuration file has been partly replaced with a database. After the first start, the configuration file may be read-only
- A web-based setup instead of command line
Before upgrading, make a backup of your configuration file and the data folder. Remove any custom templates or static files. Optionally run the server with the parameter --reconfigure to try out the new features. Minimum version for upgrading is 1.3.
Please report any issues you have with this release! Especially if you are using the full encryption mode with S3, we are very happy about any feedback.
Full Changelog: v1.3.1...v1.5.0-beta1