Use require to set order, remerge zfs blocks (require can solve the state order, previous require block was an onchanges actually)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 4 2018
zfs allow should occur when user is created
tank → zfs_tank
Plan is to move nasquenautes to 3005 as not currently deployed (mediawiki is)
Don't hardcore arcology as tank name
Allow to replace /usr/home by /home
FreeBSD uses /usr/home, but other OSes can directly use /home instead (e.g. Linux).
Migrating existing home directories
zfs allow isn't currently available in salt.states.zfs, and it's not really a problem to run again the permission command, so probably a cmd.run with require state to the ZFS create dataset operation.
$ zfs allow -s @local allow,clone,create,diff,hold,mount,promote,receive,release,rollback,snapshot,send arcology/usr/home $ zfs allow -s @descendent allow,clone,create,diff,destroy,hold,mount,promote,receive,release,rename,rollback,snapshot,send arcology/usr/home
Nov 2 2018
Nov 1 2018
Oct 30 2018
With T727 closed, we don't currently have service requiring a shared MongoDB instance.
Not maintained anymore at Flockport level. At this stage, we can use as a base template to provision a standalone mail server ourself through Salt.
Also tested it's not an open relay:
Send a mail from my local workstation
Confirmed 2018-10-29.
Discourse should be deployed with multiple containers.
The Java process now restarts rather quickly, with a waiting page explaining the server is launching, with ab autorefresh feature.
The 502 generic page has been deployed on Dwellers and Equatower.