Most documentation is in the form of README files within the subdirectories; here is the code auto-docs: https://docs.rs/fractalide https://docs.rs/fractalide

Most documentation is in the form of README files within the subdirectories; here is the code auto-docs: https://docs.rs/fractalide https://docs.rs/fractalide Looks like knowledge of the nix distribution system is required to use. I don't know how hard it would be, but a neat auxiliary project would be a cargo plugin that supports fetching packages though nix. The "net/http" fractal definition [0] references the repository https://github.com/fractalide/fractal_net_http https://github.com/fractalide/fractal_net_http, which is where the rust microservice code actualy lives. There is an example TODO app in the https://github.com/fractalide https://github.com/fractalide root dir (split between fractal_app_todo_{,model,controller}). Upon further inspection, this seems to be "simple nix microservices" that happen to be implemented in rust. One of the goals is to "remove cargo", and they use `nix-build` over `cargo build`. Also, a lot of implementation is in their 'flowscript' language within a lot of *.nix files [1] [2]. Interesting project nonetheless. Good luck to them! [0]: https://gitlab.com/fractalide/fractalide/blob/master/fractals/net/http/default.nix https://gitlab.com/fractalide/fractalide/blob/master/fractal... [1]: https://github.com/fractalide/fractal_app_todo/blob/master/components/todo/patch/default.nix https://github.com/fractalide/fractal_app_todo/blob/master/c... [2]: https://github.com/fractalide/fractal_app_todo/blob/master/contracts/todo/default.nix https://github.com/fractalide/fractal_app_todo/blob/master/c...