The previous chapter introduced services and rich rules as the mechanisms for controlling traffic within a zone. This chapter goes deeper into both. A service is not just a name that opens a port—it is an XML definition that can specify multiple ports, protocols, kernel modules, and destination addresses. A rich rule is not just…
The previous chapter established the conceptual model: zones as trust boundaries, services as named port sets, and the runtime-versus-permanent split. This chapter moves from theory to configuration. The LFCS exam tests the specific commands that create, modify, and verify zone rules, and it tests the traps that cause a working configuration to fail after a…
A firewall is not a single rule. It is a system of trust boundaries, and firewalld is the daemon that enforces them on most modern Linux distributions, including RHEL, CentOS, Fedora, and SUSE. Unlike raw iptables or nftables, firewalld introduces a layer of abstraction: zones, services, and policies. These abstractions simplify the configuration of common…
Stripping comments from XML shouldn’t be hard. But one wrong regex and you accidentally delete code instead of comments. You break the markup. You corrupt the file. I built a free tool that solves this. What it does: Use cases: Privacy:100% client-side. Nothing uploaded. Try it: tools.kandz.me/xml-comments-stripper
pnpm’s offline capabilities are a direct consequence of its content-addressable store architecture. Every package file that pnpm has ever downloaded is stored once in a global directory. When you run pnpm install –offline, pnpm does not contact the registry. It resolves the dependency tree from the lockfile, locates the required files in the store, and…
A monorepo with ten workspaces requires orchestration. Running pnpm test in each workspace manually is tedious. Running it in every workspace simultaneously overloads the machine. The –filter flag selects which workspaces to target, and the –parallel and –workspace-concurrency flags control how many run at once. The filter syntax is more than a simple name matcher—it…
A monorepo stores multiple packages in a single repository. pnpm Workspaces is the mechanism that makes this practical: it installs all packages’ dependencies together into a single virtual store, links packages to each other without publishing to a registry, and provides commands to run scripts across the entire project. The architecture is defined by a…
A project’s package.json is both a manifest and a command registry. The scripts field defines named commands that can be invoked with a short alias, and pnpm provides a resolution layer that decides whether a given name refers to a script, a taskfile, or a binary from a dependency. In pnpm, the run keyword is…
The previous chapters established how pnpm links packages from a global store and constructs a virtual store. This chapter explains the consequence: a strictly isolated node_modules layout that forbids access to undeclared dependencies. npm and Yarn Classic hoist packages to the root, allowing a project to import anything in the tree. pnpm’s default behavior is…
1. Authentication (gh) 2. Repositories 3. Issues & Pull Requests 4. GitHub Actions (gh) 5. Releases 6. Git: Commits, Tags, Remotes 7. Git: Merging Strategies 8. CODEOWNERS & Branch Protection 9. Workflow Configuration (.github/workflows/ci.yml) 10. GitHub Packages (GHCR) 11. Security & Dependabot 12. GitHub Pages & Custom Domains 13. .github Directory Layout