This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Initial Server Setup on Fedora Server is the first hour on a lab Fedora Server host: the hostname, one admin with a key, and updates from dnf.
Fedora Server. A major release is a short window, not a ten-year server. It is not RHEL and not Ubuntu. SELinux stays enforcing. Do not set it permissive to make a service start.
Do not install a web stack, a database, and a desktop in this hour. One service waits for its own page. NetworkManager. nmcli or a keyfile is the change.
The generator drafts a starter script. It does not log in. 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Confirm the hostname you will set.
- Create or confirm one named admin. Use a key.
- Read the address. Replace any documentation address before the host leaves the lab.
- Update from dnf and read the list.
- Do not add a third-party repository.
- Stop before a second product is installed.
Mistakes that outlive the command
Initial setup on Fedora Server goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Pasting a draft you did not read.
- The wrong hostname.
- A secret in the ticket or in git.
- Two changes in one window.
- No copy saved before the change.
- A documentation address left on a host that is leaving the lab.
- Disabling a firewall, AppArmor, or SELinux to make a check pass.
- Calling the generator output a finished production change.
- Root SSH left open.
- A third-party repository in the first hour.
Decisions to write down
One decision for Initial setup on Fedora Server: The hostname is the inventory name. One named admin has a key. Updates come from dnf. No extra repository was added. And the address is not a documentation address on a production host.
Checks before you call it done
Confirm this before you call the change done: The hostname matches. The admin key works. The package list was read. No secret is in the note. And a second product was not installed. If one of those fails, stop.
# First hour on Fedora Server.
# dnf.
# prompt-for-this is not a password.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.Before you leave the host
Initial Server Setup on Fedora Server ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.