vmario/fabaccess-docs
1
0
Fork 0
mirror of https://gitlab.com/fabinfra/fabaccess/docs.git synced 2024-11-19 21:47:57 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update Get it Running - Step by Step.md

Browse Source
This commit is contained in:
Joris 2021-12-23 14:05:42 +00:00
parent 47aa65b98b
commit 4eb15d3552
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
source/usage/Get it Running - Step by Step.md
View File

@ -5,7 +5,7 @@ This document provides a step by step Instruction on how to get FabAcess running
- 1 or more users registered to your system
- QR-Codes generated to acess a machine
- 1 Shelly configured as a door-opener
- 1 Shelly configured to identify if a machine is just switched on or realy running
- 1 Shelly configured to identify if a machine is just switched on or realy running (TO-DO)
**Step 1 Installing the BFFH-Server**
@ -198,5 +198,7 @@ Define a machine called "door" in the bffh.dhall<br>
`]`<br>
- assign the role DoorUser/internal to all users
It is imporatant all users have admin aka manage permissions, as the request to open the door by a user, thet the door "in Use" by this user. The door can only be re-activated when the previous user "un-uses" the door or if an othe user can "force free" the door prior to using the door hin/herself
It is imporatant all users have admin aka manage permissions, as the request to open the door by a user, thet the door "in Use" by this user. The door can only be re-activated when the previous user "un-uses" the door or if an othe user can "force free" the door prior to using the door hin/herself.<br>
**Note** in this special case, where all users will need admin capabilities the role could also contain only the permission `lab.door.use` and all permissions (disclos, manage, read, write) assigned to the machine would simply match `lab.door.use` (e.g. disclose = "lab.door.use"`).
**Identify if a machine is just switched on or realy running (TO-DO)