fac0a9ba94
* feature/runtime-improvements: Runtime things furthermore Allow tracking cgroups with futures Oh whoops handle that Get started on supervision trees Attach a GroupID to all LightProcs Noting down improvement ideas for procs More ideas about how to record data A number of small updates batched into one commit Improve Drop guards Even more console shenanigans tracing more data Some bits work \o/ Console is attached and compiles More console features Use `ManuallyDrop` instead of `mem::forget` where appropiate More console implementation stuff Start on the runtime console subscriber |
||
---|---|---|
.idea | ||
api | ||
bffhd | ||
bin/bffhd | ||
docs | ||
examples | ||
modules/sdk | ||
runtime | ||
test | ||
tools | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitmodules | ||
build.rs | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
Dockerfile | ||
i18n.toml | ||
INSTALL.md | ||
LICENSE | ||
README.md |
FabAccess Diflouroborane
Diflouroborane (shorter: BFFH, the chemical formula for Diflouroborane) is the server part of FabAccess. It provides a server-side implementation of the FabAccess API.
What is this?
FabAccess is a prototype-grade software suite for managing access, mostly aimed at Makerspaces, FabLabs, and other open workshops. It is designed to allow secure access control to machines and other equipment that is dangerous or expensive to use. It tries to also be cheap enough to be used for all other things one would like to give exclusive access to even when they are not dangerous or expensive to use (think 3D printers, smart lightbulbs, meeting rooms).
FabAccess uses a Client/Server architecture with a Cap'n Proto API. You can find the API schema files over in their own repository. The reference client is Borepin, written in C#/Xamarin to be able to be ported to as many platforms as possible.
Installation
See INSTALL.md
Contributing
See CONTRIBUTING.md. Thanks!