Skip to content
Saphira Linux

Server room scripture

BODH

The Bloody Offal Dragon from Heaven. Original Saphira nonsense, with an uncomfortable amount of truth hiding underneath it. Not BOFH imitation. Not recycled folklore. Just things the server room has taught us.

BODH, the Bloody Offal Dragon from Heaven
Unofficial Saphira wisdom

BODH accepts no responsibility for coffee expelled through keyboards while reading this page. Refresh occasionally. New sayings arrive when incidents, documentation and reality have another disagreement.

  • The cloud is somebody else's computer. The invoice proves it.
  • There is no magic. There is only configuration you have not found yet.
  • Before blaming the network, check which cable you unplugged.
  • A dashboard is not infrastructure. It is a picture of infrastructure.
  • If the documentation says ‘simply’, prepare provisions.
  • Your database is not slow. Your query has ambitions.
  • Backups become interesting approximately four seconds after you need one.
  • A firewall rule named TEMPORARY has achieved immortality.
  • DNS did exactly what you told it to do. This is usually the problem.
  • The server has plenty of memory. Konsole gave you one gigabyte. Ask how we know.
  • There are two kinds of automation: the kind you understand and tomorrow's incident.
  • A green status light means somebody chose green.
  • If your application needs seventeen SaaS accounts, perhaps the application is the problem.
  • We put the config in a text file so you can read it. Radical, apparently.
  • The fastest way to discover undocumented dependencies is to remove one.
  • Never fear the command line. Fear the person who hid it behind forty-seven buttons.
  • AI did not hallucinate your architecture. Somebody forgot to tell it what the architecture was.
  • Read-only access is a security control. ‘AI scary’ is not.
  • When production differs from documentation, production has submitted a bug report.
  • A subscription is just rent wearing a login screen.
  • If exporting your own data requires Enterprise Edition, it was never entirely your data.
  • IPv6 has 128 bits. Somehow people still managed to run out of excuses.
  • NAT is not a firewall. Saying it louder does not make it one.
  • The correct number of dashboards for BIND is zero.
  • Your certificate expired because calendars remain undefeated.
  • One day somebody will delete the test environment because it was called final-final2-working.
  • If the fix requires disabling validation, you have not reached the fix yet.
  • Logs are the server explaining itself while everybody talks over it.
  • Nothing is more permanent than the workaround nobody remembers creating.
  • We don't sell your attention. We haven't worked out how to package it as an RPM.
  • RTFM is not an insult when somebody bothered to write a good manual.
  • Saphira does not know your conversion funnel. She does know where nginx.conf lives.
  • You may contact Sales. We will probably ask what you are trying to build.
  • There is no Premium Dragon. The normal dragon already has all her legs.
  • If marketing requires us to lie, marketing may configure its own bloody server.
  • The most dangerous word in an incident is ‘probably’ followed by a command.
  • A service that starts on boot is not necessarily a service you meant to install.
  • The server is not being difficult. It is preserving the evidence.
  • A port number is not a personality. Give the service a useful name as well.
  • If nobody can explain the deployment, the deployment is already a mystery novel.
  • A package manager is a conversation with the filesystem. Read both sides.
  • The first requirement of a disaster-recovery plan is knowing where the plan is.
  • Someone said ‘we can clean that up later’. Later has a production hostname.
  • The network is usually fine. The network is also very good at proving you wrong.
  • A secret in a screenshot is still a secret, even if the screenshot is aesthetically pleasing.
  • If a tool needs an account before showing its manual, the manual is probably a sales funnel.
  • The command worked once. This is not the same as having a system.
  • A server does not become simpler because its complexity moved into a dashboard.
  • The outage began when someone called the temporary workaround ‘the new standard’.
  • A good alert tells you what happened. A great alert also tells you where to look.
  • A configuration file is a letter from the operator to the next operator. Try not to write in curses.
  • The machine is yours. The defaults are merely suggestions with confidence.
  • The best monitoring dashboard is the one that answers a question before coffee gets cold.
  • If the only recovery plan is ‘ask the person who set it up’, you have documented a dependency.

BODH has spoken

Read the manual. Check the cable. Keep the backup. Tell the truth about the system. Then, if the system still refuses to cooperate, blame DNS with evidence.