Documentation
The documentation uses the fictional Example Ltd to explain everything.
Using Heinzel Pro
For everybody who works with Heinzel Pro, hosted or in an installation of their own. The interface is the same.
Chapter 1
Getting started
From the invitation to the first approval, in a quarter of an hour.
Chapter 2
Sessions and approvals
Writing a task, reading command cards, the three levels, plans, sharing, reports.
Chapter 3
Servers and connections
Adding and preparing a server, logins, keys, jump hosts, VPN, import.
Chapter 4
Schedules, findings and rollouts
Letting it work alone at night, reading the report in the morning, working off findings.
Chapter 5
Rights and tenants
Who may do what on which server, ceilings, the block list, the emergency stop, tenants.
Recipes
One problem each from the daily work of Example Ltd and how Heinzel Pro solves it, step by step with screens of the application. One more recipe is on heinzel-pro.de as a film of 55 seconds: the database moves while the website keeps running.
Recipe 1
Backup alert at 02:10
The on-call admin types one sentence. Heinzel Pro finds the cause, proposes a fix and waits for a tap on the phone.
Recipe 2
Security updates every night
One schedule, twelve servers, nobody watching. A mail in the morning, and what Heinzel Pro was not allowed to decide alone stands as a finding.
Recipe 3
php2shell on 13 servers
Two holes in PHP, one sentence from a phone. Heinzel Pro researches, checks every server and installs the fix: on one first, then on all.
Recipe 4
Updating Ollama every week
Ollama comes out often, and nobody reads a cron job's output. A schedule updates on Sundays, checks the service and reports on Monday.
Recipe 5
Swapping Apache for nginx
Three sites on an old Apache with mod_php. Heinzel Pro reads it out, writes the server blocks and switches after your approval, with the way back in the journal.
Recipe 6
fail2ban for the web server
Thousands of login attempts a day. One sentence, and fail2ban bans SSH and the login page, never the office; the first bans are in the answer.
Recipe 7
Making PostgreSQL under the shop faster
The shop slows down. Heinzel Pro measures the database, fits server and indexes right away and writes down for the developers what only the shop code can change.
Running it on premises
For the person who installs Heinzel Pro on a host of their own and keeps it running. A container plus PostgreSQL; anybody who knows Docker Compose is done in an hour.
Chapter 6
Installing on premises
Docker Compose, reverse proxy, mail, first sign-in. With a checklist and what can go wrong.
Chapter 7
Upgrade
Change one line, check, step back if need be. Without interruption with two slots.
Chapter 8
Operations
Backup, restore, monitoring, rotating the key, locked out, troubleshooting.
Reference
The guides to look things up in, fuller than the chapters and without screens.
Reference
Administration guide
The complete manual: roles, rights, tenants, servers, keys, VPN, sessions, schedules.
Reference
Security architecture
Trust boundaries, the way of a command, what leaves the installation, known limits.
Reference
Licensing
Trial, seats, keys, source code for individual customers.
Reference
API
Tokens, the calls, the command heinzel for the shell.
Reference
Changelog
Every version and what it changes for you, the newest first; what to do before an upgrade.