Examples

001-:

Manage iocage

010-:

Module, Inventory and Filter vbotka.freebsd.iocage

040-:

Other plugins

200-:

Ansible client

300-:

Modules

310-:

Role vbotka.freebsd.postinstall

320-:

Role vbotka.freebsd.packages

330-:

Role vbotka.freebsd.iocage

340-:

Role vbotka.freebsd.config_light

350-:

Role vbotka.freebsd.rsnapshot

360-:

Role vbotka.freebsd.network

370-:

Role vbotka.freebsd.pf

380-:

Role vbotka.freebsd.custom_image

390-:

Role vbotka.freebsd.poudriere

400-:

Role vbotka.freebsd.zfs

410-:

Role vbotka.freebsd.lib

420-:

Role vbotka.freebsd.apache

430-:

Role vbotka.freebsd.certificate

440-:

Role vbotka.freebsd.dhcp

500-:

Infrastructure

Note

  • The examples that create jails use by default the iocage host setting created in the example 440 Configure DHCP and pf. The firewall is on the external interface and on the vnet bridge of the iocage host. The DHCP for the jails is on the bridge. The SSH from the local network to the jails is redirected. The examples that do not use this setting are marked .deny. This means, they are not included in batch.sh. To run these examples, reconfigure the firewall. See the example 370 Configure pf.

  • All examples comprise additional files not shown in the files’ tree. See them to learn more details.

  • The examples comprise batch.sh that runs the commands and creates the output for the examples.

  • Most plays in batch.sh are idempotent. The output of such a play may show status ok instead of expected changed if the play has been run repeatedly.

  • The playbooks in the examples use dashes - in their filenames. For example, pb-iocage.yml.

  • The playbooks in the collection, because of the Ansible collection naming conventions, use underscores _ in their filenames. For example, pb_iocage_template.yml.

  • To avoid connection errors in examples where DHCP is used, host_key_checking = false can be set in ansible.cfg.

Hint

See Update examples.