Pre-deployment checklist for Linux servers

Topic: Servers linux

Before going live: verify hostname, time, network, firewall, SSH, updates, backups, monitoring, and app config. Use this so nothing is left in default or broken state when the server is put in production.

Intent: Checklist

Quick answer

  • Hostname and /etc/hosts correct; time synced (timedatectl, NTP); network and DNS work; firewall allows only required ports; SSH key-only and no root.
  • Updates applied; backup of /etc and data configured and tested; monitoring or alerting in place; app config and secrets correct and service starts.
  • Document: IP, role, owner, backup schedule, and how to access (SSH, console); run through the checklist and tick each item.

Prerequisites

Steps

  1. Identity and time

    hostname; hostnamectl set-hostname NAME; /etc/hosts has correct entry; timedatectl; enable NTP (systemctl enable systemd-timesyncd or chronyd).

  2. Network and firewall

    ip addr; ip route; getent hosts; ufw status or nft list; allow only 22, 80, 443 (or your ports); test from outside.

  3. Access and updates

    SSH key-only, no root login; apt upgrade or dnf update; no failed units (systemctl list-units --state=failed).

  4. Backup and monitoring

    Backup /etc and data; test restore; set cron or timer; configure alerting (disk, service, or external check); document runbook.

Summary

You will run a pre-deployment checklist: hostname, time, network, firewall, SSH, updates, backup, and monitoring so the server is ready for production and documented.

Prerequisites

  • Server installed and minimally configured; hardening and networking guides done.

Steps

Step 1: Identity and time

Set hostname and /etc/hosts; enable and verify NTP.

Step 2: Network and firewall

Verify IP, route, DNS; firewall allows only required ports; test from client.

Step 3: Access and updates

SSH hardened; updates applied; no failed systemd units.

Step 4: Backup and monitoring

Backup and test restore; monitoring or alerts; document IP, role, and access.

Verification

  • Every item on the checklist is done and documented; one final smoke test (SSH, app, backup).

Troubleshooting

Item fails — Fix before go-live; refer to the specific guide for that item.

Next steps

Continue to