Add Glossary
parent
ec64ab5772
commit
30ccc4f6b4
1 changed files with 15 additions and 0 deletions
15
Glossary.md
Normal file
15
Glossary.md
Normal file
|
|
@ -0,0 +1,15 @@
|
||||||
|
Here's the explanation of words describing the furtka project.
|
||||||
|
|
||||||
|
# Furtka Components
|
||||||
|
| Term | Definition |
|
||||||
|
|---------|---------|
|
||||||
|
| Webinstaller | Custom archinstall wrapper with a webserver to facilitate user input. Input should be kept simple, technical user input needs to be inferred. |
|
||||||
|
| FurtkaOS | Our arch linux based OS. It uses docker to run different apps. |
|
||||||
|
| Furtka Server | A device with FurtkaOS as it's main operating system. |
|
||||||
|
| App | Docker container (or stack) with dependancies and manifest information. Dependancies are different apps. Coexistance between an App and its dependancies needs to be defined by sets of setup, update and uninstall cli commands, that will be executed on the dependancy app in each case. Circular dependancies should be avoided. |
|
||||||
|
| Backend | A service, which communicates with a Furtka Server and allows internet access to apps. Backend needs unrestricted access to a Furtka Server, either through a VPN, or being in the same local network. |
|
||||||
|
|
||||||
|
# Common Terms
|
||||||
|
| Term | Definition |
|
||||||
|
|---------|---------|
|
||||||
|
| should | We use the word should to indicate points, that are not technically necessary, but have to be kept to ensure compatibility with the core values of Furtka. |
|
||||||
Loading…
Add table
Reference in a new issue