https://github.com/pyrretsoftware/ray
easily self-host your stuff
https://github.com/pyrretsoftware/ray
go reverse-proxy self-hosted server
Last synced: 8 days ago
JSON representation
easily self-host your stuff
- Host: GitHub
- URL: https://github.com/pyrretsoftware/ray
- Owner: pyrretsoftware
- Created: 2025-03-12T14:46:56.000Z (11 months ago)
- Default Branch: main
- Last Pushed: 2026-01-17T17:15:25.000Z (21 days ago)
- Last Synced: 2026-01-22T21:30:29.304Z (16 days ago)
- Topics: go, reverse-proxy, self-hosted, server
- Language: Go
- Homepage: https://ray.pyrret.com
- Size: 7.08 MB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: readme.md
- Security: SECURITY.md
Awesome Lists containing this project
README
ray
easily self-host your stuff
Installation guide
|
Docs
|
Latest release
|
Latest unstable builds
# what is ray?
ray is a comprehensive system for deploying, managing, and routing web applications on self-hosted servers. Given a project configuration file, ray can build, deploy and make your project accessible through ray's reverse proxy (ray router). Ray can automatically deploy and update from a remote git repository, manage different deployment channels on different branches, handle authenticating users on private deployment channels, load balance your application to other ray servers, monitor your projects, notify you if anything goes wrong, and a lot more.
# ray's current stage of development
ray is currently early in development. The latest release (v2.2.0) is considered to be pretty stable and i currently use it for everything i personally host. Beware though, there could certanly be bugs in this release.
# known issues (in the latest release)
These are bugs that are known to be in the current release, most of them fixed already, but not pushed out in a release.
* 404 pages for rayserve does not work properly
* Redirects for rayserve does not work properly
* Inproperly defined rayserve redirects causes panic instead of being handled properly
* Panic can be triggered by attempting to kill nonexistant processes
* Build continues even after a step has failed