Connect the system to its ecosystem #
Integration guides describe the boundary between a FreeBSD facility and a maintained third-party tool. They identify which project owns each command, link to that project’s documentation, and preserve a route back to the underlying FreeBSD mechanism.
Bastille jail lifecycle #
- Create a first jail with Bastille prepares a release and creates a small managed jail.
- Publish a Bastille service through PF exposes one port from a private jail.
- Mount a host-managed ZFS dataset keeps durable data outside the jail root.
- Update and upgrade Bastille jails separates release patches, jail changes, and rollback.
- Back up and restore a Bastille jail protects the jail root, external data, configuration, and secrets.
Jails and virtualization #
- Compare jail managers and OCI tooling records current scope and stewardship without inventing a popularity ranking.
- Prepare bhyve and vm-bhyve uses the FreeBSD-maintained vm-bhyve repository and stops at verified preparation.
Packages, storage, and service operations #
- Build a package repository with poudriere defines source, signing, publication, and client trust boundaries.
- Choose ZFS backup automation compares maintained tools against the required retention, resumption, and restore behavior.
- Run Motion with webcamd connects a proven camera device to local control, streaming, and event recording.
- Choose NFS or Samba for file sharing begins with clients, identity, permissions, and trust.
- Manage FreeBSD configuration declaratively separates package, service, file, and rollout ownership.
- Design reverse proxy, certificate, and monitoring boundaries defines a maintainable public-service edge without a universal deployment recipe.