Doc addition to OutOfScope > Domain based forwarding for HTTP

[hevisko]

Feature Proposed

Domain based forwarding for HTTP

Perhaps (rather??) point to Caddyserver.com that is very easy to setup reverse proxy to point to rathole's server/upstream... and do the LetsEncrypt certificates as added benefit/additions without additional configs

[fernvenue]

I don't think link any other applications here is a good idea.

[hevisko]

Suggestion, but then why list nginx which is complex? I see rathole as simple/easy, and this is a quick/simple/easy way to achieve just that.

Any case, was a suggestion only. If you don't like it, welcome to close ticket as "Not going to implement" :)

[fernvenue]

Anyone is free to choose their preferred application for processing at the application layer, but the purpose of the documentation is simply to provide an explanation and an example, listing all available options may only make the document more cumbersome and hard to read. And yea, I'm not against the idea that people should have more options, feel free to use your favorite one :)

By the way, I don't think NGINX is complex to configure. Besides, we don't always need web application to generate certificates for us, in many cases, we wanna use our own certificates or support devices that do not support HTTPS using a pure HTTP network. (For example, when using some Linux distributions, you need to first install ca-certificates, openssl or that kind of things over HTTP before using HTTPS.)

[hevisko]

I'll respectfully disagree when you can do (without ca-certificates and without openssl) just download a single binary and execute caddy reverse-proxy --from example.com --to localhost:9000 or have this single configfile:

example.com {
    reverse_proxy localhost:5000
}

That said, I do have sites I don't front with Caddy but with nginx for application reasons.

Again: in the spirit of "out of scope: here is simple/quick option"

[rapiz1]

I'm fine with the improvement to the docs since people will ask less questions. It may not suit well in a section called out of scope. However we don't have faq or cookbook. So feel free to bring up a PR about caddy. 

---Original--- From: @.> Date: Thu, Mar 16, 2023 19:40 PM To: @.>; Cc: @.***>; Subject: Re: [rapiz1/rathole] Doc addition to OutOfScope > Domain basedforwarding for HTTP (Issue #232)

I'll respectfully disagree when you can do (without ca-certificates and without openssl) just download a single binary and execute caddy reverse-proxy --from example.com --to localhost:9000 or have this single configfile: example.com { reverse_proxy localhost:5000 }
That said, I do have sites I don't front with Caddy but with nginx for application reasons.

Again: in the spirit of "out of scope: here is simple/quick option"

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[oliverbob]

Do we have the docs already? I would like to expose apache, caddy or nginx, but don't know how.

The introductory docs assumes frp knowledge/experience. I came here to use it for web http and expose it as https just like what ngrok does.

Newbie questions like ours that can be answered by the docs will allow us to make use of this tool and recommend it to others that would naturally attract a community to this project.

Can someone point me to the example of how this is use for any of the three?

Thanks.