[GH-ISSUE #2931] [Feature Request] API interface instead of using .ini files for configuration of the client/server?

gitea-mirror commented

2026-05-05 13:30:26 -06:00

Owner

Copy link

Originally created by @JohnnyRacer on GitHub (May 10, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2931

Describe the feature request

Does there exist an API interface for frp? If not would it be possible to add a simple API interface instead of using .ini files for configuring the server/client? This would allow frp to be integrated with other components in languages like Python, JS or Rust much more easily. Since currently one would have to manually dump the .ini file and mess around with starting/stopping services which can be a pain in more complicated projects.

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @JohnnyRacer on GitHub (May 10, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2931 ### Describe the feature request Does there exist an API interface for `frp`? If not would it be possible to add a simple API interface instead of using `.ini` files for configuring the server/client? This would allow `frp` to be integrated with other components in languages like Python, JS or Rust much more easily. Since currently one would have to manually dump the `.ini` file and mess around with starting/stopping services which can be a pain in more complicated projects. ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [X] Extensions - [X] Others

gitea-mirror

2026-05-05 13:30:26 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:30:29 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (May 10, 2022):

We plan to support it in frp v2. There won't be changes in current version.

@fatedier commented on GitHub (May 10, 2022): We plan to support it in frp v2. There won't be changes in current version.

gitea-mirror commented

2026-05-05 13:30:29 -06:00

Author

Owner

Copy link

@penguine commented on GitHub (May 17, 2022):

i did some tests on which places we put the REST api. it works. right now the API is on holt. but we can work on it together if we start it again with that. that can certainly be used directly for v2.

@penguine commented on GitHub (May 17, 2022): i did some tests on which places we put the REST api. it works. right now the API is on holt. but we can work on it together if we start it again with that. that can certainly be used directly for v2.

gitea-mirror commented

2026-05-05 13:30:30 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 17, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Jun 17, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified