Repository navigation
Coexistence
A clean or dedicated FreeBSD host is not required. Other jails can share the host when their configuration meets the requirements below. The installer checks for conflicts before installation.
The installer creates new deployments; it does not adopt or upgrade existing Nextcloud installations. A new deployment does not require reinstalling FreeBSD or removing unrelated jails that meet these coexistence requirements.
It uses its own Bastille configuration at
/usr/local/etc/bastille/nextcloudonfreebsd.conf and storage under
/srv/cloud-installer. It does not take over other jails or their configuration.
For existing NextcloudOnFreeBSD installations, use their original installer.
Keep console access and a second SSH connection while changing host networking.
PF must be running and enabled at boot (pf_enable=YES). Both the live rules and
the boot file selected by pf_rules are checked. The installer does not merge or
reload an existing parent policy. Custom pf_program/pf_flags and integration
with IPFW/IPFilter are not supported.
Project instances share the nextcloudonfreebsd anchor in
/etc/pf.cloud-installer.conf. Other firewall rules remain under your control.
Place the project hooks first in their respective sections:
# Existing options, macros and single-line tables precede these sections.
nat-anchor "nextcloudonfreebsd"
# Other NAT rules follow.
rdr-anchor "nextcloudonfreebsd"
# Other RDR rules follow.
anchor "nextcloudonfreebsd" quick
load anchor "nextcloudonfreebsd" from "/etc/pf.cloud-installer.conf"
# Other filter rules follow.
The supported parent layout has these restrictions:
- No filter rule before the project filter hook, or conditional/duplicate hooks.
- Only
lo0may useset skip. - No includes, multiline declarations, inline anchors, scrub, Ethernet or binat rules.
- Other named filtering and NAT anchors are allowed. Other redirections must be
numeric IPv4 TCP/UDP rules in the parent's RDR section, not
rdr-anchorcalls.
For first setup, create the empty project anchor file as root-owned mode 0600
before loading the parent. Leave an existing managed anchor file intact. Check
and load the parent policy using your usual FreeBSD administration procedure.
On a host without an existing firewall policy, the installer offers Prepare empty
PF parent. Review it and type PREPARE; --yes does not approve this step.
This starter leaves non-project traffic unrestricted. Preparation remains if you
later cancel installation.
Enable IPv4 forwarding with gateway_enable=YES in /etc/rc.conf and load
if_bridge at boot with if_bridge_load="YES" in /boot/loader.conf.
The required live settings are:
net.inet.ip.forwarding=1
net.link.bridge.pfil_bridge=1
net.link.bridge.pfil_member=0
net.link.bridge.pfil_local_phys=0
net.link.bridge.pfil_onlyip=1
Save the bridge values in /etc/sysctl.conf. Check for conflicting overrides,
including /boot/loader.conf.local. These settings affect the whole host, so
check that your other workloads can use them.
Keep a fixed host/LAN IPv4 address. This is separate from the public hostname and any changing WAN address. See port forwarding.
Names, storage paths, bridges, networks and ports must not overlap. Stopped jails still reserve their configured resources. Shared-IP jails use host ports; separate VNET jails do not. Live jail settings must match their saved configuration.
The installer can inspect static native jail configurations and recognized Bastille bridge/jib layouts. Its iocage support is limited to schema-34 static shared-IP jails with ordinary non-basejail roots, numeric IPv4 addresses, no IPv6, an empty/comment-only fstab and default no-op host hooks. iocage VNET, NAT/DHCP, delegated/nested jails and custom hooks are not supported.
If a check fails, correct the reported configuration or resource conflict, then choose Recheck host. Edit settings returns to your draft. Once installation has started, follow its recovery message instead; saved Resume settings cannot be edited.
Package installation may update pkg itself and required installed dependencies. It does not perform a blanket host upgrade or switch repository branches.
Keep your original installer directory. If network recovery is required, resolve it before starting another operation. Removal retains application data by default and leaves shared host settings in place; see Uninstall.