Releases: pyrretsoftware/ray
v3.0.1
This is a small patch release that fixes a null pointer dereference that occurs when ray attempt to shut down a process that is not actually running. This release also includes new a new rayinstall compatibility mode as well as limited windows 7 support.
Compatibility information
No action need to be taken when migrating from the previous release. Project config uses version v1-networked and ray config v3-extended-compatability
Installation information
Below you can find zip archives containing ray installation packages for different platforms and architectures. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.
v3.0.0
Last big release was may 18 last year, quite a while ago now! I've not been working that much on ray during that time but i thought i would pack up my changes that i have done into a new big release. Hope you enjoy this release, it's the biggest one yet!
Additions
- Comlines - communication lines, basically a rest api to interact with ray, either locally over unix domain sockets or over tcp.
- Rayc - replaces rray, instead of working over ssh, it interacts with comlines.
- Extensions - what it says on the tin, local comline based extensions to extend the functionality of rays.
- UDS Support - previously applications would have to listen to the RAY_PORT environment variable, now they can listen to a unix domain socket (named pipe on windows) which is a lot faster.
- Monitoring makeover - monitoring notifications, at least on discord, have had a visual makeover. Also see CatMode.
- New website - new site at ray.pyrret.com
- DCM (Docker Compatibility mode) - run docker containers in ray, see this and this.
- Raydoc - automated documentation system, basically doxygen for go but it outputs markdown.
- RLSP v2 - rlsp now uses single-use connections for better stability. This means pre-3.0.0 servers cannot interact with 3.0.0 servers.
- Reloadable RLS Connections - rls connections can now be hot reloaded from config without requiring a restart.
- Ray Files - place files into your project from your ray config. Useful for stuff like config files, and can also be used for docker volumes with DCM. See the reference.
Changes
- Rayinstall has once again been reworked
- Quite a few bugfixes
- Old ray environments are now cleaned up on startup, saving a lot of diskspace.
- Rayserve optimizations.
- Rls weight optimizations.
- Systemd file changes to prevent rays starting when the server is not yet online.
- Rayutil is now disabled in certain cases, for example when fetching htmx content.
And probably a lot more i forgot to record!
Compatibility information
Action may need to be taken when migrating from the previous release. Project config uses version v1-networked and ray config v3-extended-compatability
RLSP v2 means older servers cannot interact with newer ones. Please either upgrade all your servers (highly recommended) or do not update any of them.
Installation information
Below you can find zip archives containing ray installation packages for different platforms and architectures. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.
v3.0.0-rc2
This is the second release candidate for 3.0.0. This has undergone extensive testing.
v3.0.0-rc
v2.2.0
Yet another boring patch...
Changes
- Unknown ray router errors are now printed out by rays, so that they can be viewed in the ray logs.
Bugfixes
- Rayserve now properly sets the Content-Type header when serving 404 pages
Compatibility information
No action needs to be taken when migrating from the previous release. Project config uses version v1 and ray config v1-extended-compatability-middleware
Installation information
Below you can find zip archives containing ray installation packages for different platforms and architectures. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.
v2.1.0
Kinda boring patch but i couldn't stand reloading being single threaded.
Additions
- Multi threaded deployments - Deploying stuff is now multi threaded!
- Middleware - You can now specify another place for ray router to route your request, to allow for middleware.
Compatibility information
No action needs to be taken when migrating from the previous release. Project config uses version v1 and ray config v1-extended-compatability-middleware
Installation information
Below you can find zip archives containing ray installation packages for different platforms and architectures. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.
v2.0.0
It's been more than a month since last release, I've been working on some other project too during that time, but the main reason for the delay is the amount of new features packed into this release, hope you enjoy!
Additions
- RLS: Ray load balancing system - simply put, RLS is a flexible system to deploy projects to other ray servers and load balance traffic between them. Check the documentation for more info.
- Rray - new tool that makes managing remote ray servers easier, like easily editing their config or quickly deploying projects to them. Check the documentation for more info.
- Monitoring - you can now directly monitor your processes and ray itself via a slack or discord webhook.
- Autofix - autofix is a new ray feature that can perform automatic rollbacks of your projects if they go down. More measures to fix your projects can/will be added in the future.
- Require authentication for prod channel - you can now choose to require authentication for the prod channel through the
ProdTypeIsDevproperty. - UUID identifiers - start using uuids as identifiers to lower the risks of an id collision.
- Improved build logs - build logs have been significantly improved in a new json-based format. You can use
rays listto find the path of log files from processes. - NotWebsite - you can now deploy non-websites with ray using the
NotWebsiteproperty in your project config. - Redirects in rayserve - you can now specify redirects in rayserve (rays built in deploy tool for deploying static sites).
- 404 page in rayserve - you can now specify a 404 page in rayserve (rays built in deploy tool for deploying static sites).
Changes
- Rayinstall has been improved by getting rid of rpack files and packaging the binaries inside the rayinstall binary.
- Rayutil is now longer injected if asked to by no-transform header
- Directories of ghost processes are now deleted.
- Much better config validation.
- Process errors are handled much better
- The dev login page now looks much better.
- The ray router error page now looks much better.
- Ray router now adds the via header.
- Internal: The way errors are handled have been cleaned up, reducing boilerplate.
Bugfixes
- Fixed a bug that would cause rayutil to behave weirdly in some situations when a web server returned 304 codes.
- Fixed major update bug (twice lol).
- Fixed major issue with systemd configuration that caused rays to start too early on boot.
Compatibility information
No action needs to be taken when migrating from the previous release. Project config uses version v1 and ray config v1-extended-compatability
Installation information
Below you can find zip archives containing ray installation packages for different platforms and architectures. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.
v1.0.0
This is the first ever stable release of ray! It has taken about a month, but ray now contains all the features i initially wanted it to have, plus quite a bit more.
Below you can find zip archives containing ray installation packages for different platforms and architectures, bundled along the rayinstall utility to help you with installing them. Refer to the installation guide for help.
The zip archives below were automatically generated by this Github Actions workflow.