I would like to introduce a reverse proxy which I really like to use and maybe you will like it too š
I tried a few reverse proxies, but in the end nothing met my needs. A simple reverse proxy with webinterface, easy to setup, but powerful...
I was impressed from the start with Zoraxy. A good alternative to Nginx Proxy Manager and Cosmos. Zoraxy can be run in docker, but it is possible to install it directly on the host. This is the first reverse proxy I saw, where docker is not an obligation (except apache and nginx itself :) )
Zoraxy makes it easy to setup subdomain proxies oder virtual directory records. An uptime Monitor is included too and a few network tools like ping, whois, mDNS scanner, IP-scanner or a ssh client.
LetĀ“s Encrypt is supported and custom certificates. Blacklist / Whitelist access control and a lot of stats (like goaccess but with better diagrams)
You can import and export all settings to zip file including all subdomain proxies etc...
That makes it entirely unusable, IMO. That's like using an automatic transmission vehicle with 5mpg just because you're afraid to learn how to drive a manual even if it gets 50mpg.
Officially, no. I'm an avid caddy user for years and not looking to change, as I'm very comfortable with config files and cli, but I have to admit Zoraxy looks very slick!
I might give it a try soon, I'm starting to embrace more nice UI to work with although I'll always feel most at home in the terminal
This is the first reverse proxy I saw, where docker is not an obligation
This is the broader direction. I lament the days where everyone can just use shared hosting and never worry about infrastructure, but everything seems to be moving towards larger and larger stacksā¦ and to abstract as much of that away as possible so people can focus on the apps, docker/Kubernetes is playing a larger and larger role.
Which is also why youāre seeing more and more CLI/scripting ā so infrastructure pieces that get in the way of development/apps can be abstracted away and managed in a repeatable fashion between deployments. As you start to work with more and more moving pieces, it is generally a good idea to expand your area of expertise beyond just GUI and move into the more scriptable side, so you can gain more control over your stack more effectively.
Thanks for posting this. Itās nice that people are working on more accessible ways to do this, every way Iāve done it so far has been pure command line. And while thatās fine, it takes longer to understand and set up for simple installs.
And while thatās fine, it takes longer to understand and set up for simple installs.
It also allows for easier scripting, which makes things more reproducible.
Even for simple things I'm nowadays going through Ansible - because I know I'll have forgotten what exactly I did in a year, and that way I can just look at the Ansible files in git to remember.