02 - Terminology throughout this document

This page describes the terminology and wording used throughout the entire documentation. Please do not hesitate to ask your Blunix consultant if anything is unclear or needs updating.

Term	Description
service	A program running on a Debian Linux server
baseline	A set of services every server runs, for example openssh-server, fail2ban, dnscrypt-proxy and others
utility stack	A set of servers that provide services for all other servers, like monitoring, backups, central logfiles, wireguard and others
development environment	the environment where apps are developed, commonly on the employees workstation
test(s)	automated tests (code) that try out the functionality of the app and report problems
staging	the server environment that feels like production but usually is smaller scale and is only accessible to developers
production	environment where the production app is hosted, accessible to customers
cus	three letter abbreviation of customer company name
cus.int	customer internal vpn reachable domain, only for staff
cus.pub	customer internal internet reachable domain, only for staff
playbook-infrastructure-company	Your companies git repository containing all configuration management code, commonly called after your companies name, Example: Example GmbH on Debian 12: playbook-infrastructure-example-12
server or instance	A Debian Linux installation on a cloud provider instance, a physical server or a proxmox virtual machine
Blunix or Blunix Stack	Describes the tools and programs provided by Blunix GmbH, hosted at git.blunix.com
Blunix GmbH	The company developing and maintaining Blunix Stack