-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: REST configuration #230
Comments
You can just start rpxy using the There's no API endpoint at his moment unfortunately but it'll come to the webui soon. |
At this point, i have no plan to implement REST api for dynamic configuration. I had considered that, but i decided not to implement it as a core function of rpxy by the following reason.
|
Maybe the third option of another rpxy-bin dedicated only to REST api would be reasonable. IMHO, worth to consider in detail. |
It'll take another few weeks but the next release of |
@Gamerboy59 Sounds nice to enhance The priority to consider the RESTful api inside rpxy(-bin) is not high for me at this point, as explained in my previous comment. So it would be helpful for users that the external helper tool supports it. |
I respectfully disagree on using the toml as the external contact point for any integration work as the best option. I consider the config file as an externalized internal state. The internal routing config should have be exposed for querying and potentially modification via a standard API, REST just being a common choice. My specific case requires frequent adding/enabling specific routes and traffic monitoring, all programmatically. Additionally I played with the TOML config and sometimes it worked and other times it did not, leaving me the impression that TOML config is not reliable. Otherwise the proxy worked beautifully. |
Any reason your project is GPL-3 licensed? |
Sounds like an off-topic discussion topic.. |
Basically I want people to make the source available if they fork it and state if and what has been changed. |
Liked it when the tmol worked. Would be really nice to have REST api to reconfigure at runtime to improve the interoperability.
The text was updated successfully, but these errors were encountered: