Should plugin data be separated from plugin/jail?

[majerus]

For plugins is it best to use a mount point for application data to another location in the pool? For example Gita has a directory /var/db/gitea/gitea-repositories would it be recommended to have this directory actually be a mount point outside of the jail? Generally is there guidance regarding this type of thing?

 

[Redcoat]

See https://www.ixsystems.com/documentation/freenas/11.2/jails.html#additional-storage that maybe fits your request.

 

[freedombacon]

I keep data separate from the plugins on a different dataset as described in the link above. Application configuration and user data should not be coupled together. This makes backups and snapshots easier. You can make a snapshot of just the plugin jail before updating, or backup a collection of music without mixing in cluttering or sensitive files from the server config. On FreeNAS, the separate dataset makes getting data in and out of the jail a lot easier.

 

[mjt5282]

I would highly recommend using the standard iocage jails in a SSD mirrored pool and having separate zfs datasets for the data used by the jail. Naming conventions are important - I tend to keep stateful configuration data for each jail app in its own dataset, and datasets for things like Plex Media Server, transmission's incoming target directories, etc. Doing it this way has made it much easier to migrate from Warden jails to iocage jails, and perhaps someday to something completely different such as Docker again or something that hasn't been released yet.