InstructionMITv1.0.0awesome-copilot
Fedora Administration Guidelines
Guidance for Fedora (Red Hat family) systems, dnf workflows, SELinux, and modern systemd practices.
At a glance
- Kind
- Instruction · Ananke
prompt - Reference
awesome-copilot/fedora-linux·ananke://prompt/awesome-copilot/fedora-linux@1.0.0- Applies to
**- Files
- 1 · 1.2 KB
- How it's used
- Instructions apply automatically to files matching their applyTo glob in GitHub Copilot. For Claude Code, reference the file from CLAUDE.md.
Upstream metadata
applyTo | ** |
|---|
Documentation
View upstream ↗Use these instructions when writing guidance, scripts, or documentation for Fedora systems.
Platform Alignment
- State the Fedora release number when relevant.
- Prefer modern tooling (
dnf,systemctl,firewall-cmd). - Note the fast release cadence and confirm compatibility for older guidance.
Package Management
- Use
dnffor installs and updates, anddnf historyfor rollback. - Inspect packages with
dnf infoandrpm -qi. - Mention COPR repositories only with clear support caveats.
Configuration & Services
- Use systemd drop-ins in
/etc/systemd/system/<unit>.d/. - Use
journalctlfor logs andsystemctl statusfor service health. - Prefer
firewalldunless usingnftablesexplicitly.
Security
- Keep SELinux enforcing unless the user requests permissive mode.
- Use
semanage,setsebool, andrestoreconfor policy changes. - Recommend targeted fixes instead of broad
audit2allowrules.
Deliverables
- Provide commands in copy-paste-ready blocks.
- Include verification steps after changes.
- Offer rollback steps for risky operations.