I started building this project in February 2021 in Go to control all of the information flow, requests, and structural backend logic without needing to restart the process (like httpd or other servers) to make adjustments. It has gone through many tests in production (it didn't have a GUI at the beginning), specifically to serve PHP applications (with php-cgi), but with the option to add any preprocessor I wanted via CGI. And recently I published it as open source in its GitHub repository. It is intended to be accessed via GUI, and not via API.
It currently has these features: Cross-platform, custom visual management interface, management of unlimited domains and multi-level wildcard subdomains, SSL certificates, URI rewrites, request preprocessing, fine-grained request rate and size limiting, as well as custom aliases, headers, MIMEs, and indexes.
GUI access via: "http://localhost/admin:" — do not forget the ":" at the end.
Default credentials: "Turbo" (User) and "Admin" (Password). Compile with your own default credentials for better security.
How to trust the heavily obfuscated source code? Did not want to waste tokens on doing the review, but if one cannot trust the code (when something gets published as OSS), it becomes a difficult choice to adoption / usage. I can't even run in on my device. Probably could try a containerized version, but short of time.
I started building this project in February 2021 in Go to control all of the information flow, requests, and structural backend logic without needing to restart the process (like httpd or other servers) to make adjustments. It has gone through many tests in production (it didn't have a GUI at the beginning), specifically to serve PHP applications (with php-cgi), but with the option to add any preprocessor I wanted via CGI. And recently I published it as open source in its GitHub repository. It is intended to be accessed via GUI, and not via API.
It currently has these features: Cross-platform, custom visual management interface, management of unlimited domains and multi-level wildcard subdomains, SSL certificates, URI rewrites, request preprocessing, fine-grained request rate and size limiting, as well as custom aliases, headers, MIMEs, and indexes.
GUI access via: "http://localhost/admin:" — do not forget the ":" at the end.
Default credentials: "Turbo" (User) and "Admin" (Password). Compile with your own default credentials for better security.
Note: The GUI is currently available in Spanish.
Many other details are in the documentation (https://turbo.okzgn.com) and in the repository's readme (https://github.com/okzgn/turbo-go).
How to trust the heavily obfuscated source code? Did not want to waste tokens on doing the review, but if one cannot trust the code (when something gets published as OSS), it becomes a difficult choice to adoption / usage. I can't even run in on my device. Probably could try a containerized version, but short of time.