This is a continuation of the effort to separate core logic and JSON-RPC services (see issue #23).
Here we have the beginnings of a bundled JSON-RPC server. It currently only includes the newly-separated peach-stats methods.
I will work on separating peach-network next and will add the networking methods to this repo. After that, I'll add pico-args to allow selective deployment of various method subsets (eg. start the JSON-RPC server with only the stats methods); as well as port number etc.
This is a continuation of the effort to separate core logic and JSON-RPC services (see [issue #23](https://git.coopcloud.tech/PeachCloud/peach-workspace/issues/23)).
Here we have the beginnings of a bundled JSON-RPC server. It currently only includes the newly-separated `peach-stats` methods.
I will work on separating `peach-network` next and will add the networking methods to this repo. After that, I'll add [pico-args](https://crates.io/crates/pico-args) to allow selective deployment of various method subsets (eg. start the JSON-RPC server with only the stats methods); as well as port number etc.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is a continuation of the effort to separate core logic and JSON-RPC services (see issue #23).
Here we have the beginnings of a bundled JSON-RPC server. It currently only includes the newly-separated
peach-statsmethods.I will work on separating
peach-networknext and will add the networking methods to this repo. After that, I'll add pico-args to allow selective deployment of various method subsets (eg. start the JSON-RPC server with only the stats methods); as well as port number etc.looks great ~
cool pico-args vs clap/structopt is quite a difference (looking at the pico-args chart comparing binary size and compilation times)