1.0.0-beta.2
Pre-release🎉 Another long overdue release of Octyne (I promise octyne 1.0 before the year ends though)!
Octyne is pretty straightforward, so I don't really work on it very often, so releases are fairly delayed, however recently I've definitely picked up the pace since I use this project a LOT and can use a 1.0 release :^) This one is fairly monumental feature wise, and 1.0 is rather imminent now.
This release incorporates Redis support to share auth tokens between Octyne instances, a lot of security hardening like vulnerability fixes and HTTPS support, ability to disable servers from being auto-started, and fixes to file locking so that Octyne releases files correctly. This is especially important on Windows where mandatory file locking is used and Octyne works perfectly there now.
Changelog
- Added Redis support \o/
- Release file locks correctly in the files API (fixes it on Windows 🎉 )
- Add HTTPS support \o/ (although reverse proxies are preferred due to easy restarts to update cert)
- GET
/servers/{id}
now returns uptime and server status, totalMemory is no longer a bool (wut). - Downloading files is now a secure endpoint, was previously insecure due to Ecthelion.
- Redis connections are now closed properly when Octyne's HTTP server encounters a problem.
- Patched security vulnerability allowing authenticated users to access files outside an app's folder.
./octyne -v
is now aliased to./octyne --version
.- Auto-start when Octyne starts can now be disabled for individual servers.
- Added GitHub Actions and Deepsource (had to add a lot of skip comments).
What's missing for 1.0
- Copying on Windows.
- Alternate token authentication.
- Configurable crash limits and ports.
- Compression endpoints not complete.
- Statistics endpoint to get data like CPU and RAM usage of processes not complete.
x86_64 binaries for Windows, macOS and Linux are provided, but octyne works on other architectures like ARM as well. It should work on other architectures and Unix-like OSes supported by Golang as well (untested, but if you run into issues, let me know!).