search

rapiz1 / rathole

A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok.
Apache License 2.0
9.8k stars 488 forks source link

Reduce the complexity of configuration files #216

Open mrzkj opened 1 year ago

mrzkj commented 1 year ago

Feature Proposed

Use Case

Can rathole's configuration file be changed to a unilateral configuration? Instead of having to move the configuration files on both sides every time you add a port? For example, the frp configuration file needs to be configured on the server. However, the configuration file on the server is a one-time configuration and can be used for a lifetime. You only need to add new configuration conditions on the client instead of the server. Another example is the configuration file of nps, which is used on the server side and can be configured only on the client side. When adding a new port, there is no need to configure the configuration file on the client side and the server side. Can rathole also be upgraded so that when new ports are added, they can be configured on either side of the server or client instead of both sides? Thanks!

fernvenue commented 1 year ago

Duplicate of https://github.com/rapiz1/rathole/issues/161, https://github.com/rapiz1/rathole/issues/158. Make sure you have checked the issues before you open a new one :)