2# Mockup of data structure

I'm a newbie when it comes to TrueNAS, so when it comes to setup, there might be better ways than mine.. but I believe my philosophy about data structure is sound and therefore decided to publish my thoughts. (if not for anyone else, then at least as notes for my own sake)

Data structure: I want jails for each assignment (one jail for a database server, one for each webserver etc) but I want the data stored elsewhere.

meaning if my webserver grows old, gets hacked or for some reason doesn't perform as I want it to, I can simply destroy the jail, create a new one and connect to the existing data. Also, backing up the data pools is in my mind more systematical than having both database, webfiles etc stored inside the same

In addition, I want my familys phones, laptops etc to be backed up to a windows share, where the kids can read say... family photos, but only the parents have the option to delete said pictures. This also needs to be a cloud solution.

Here's my mockup:

mockup of data-flow

The IP adresses we will use in this project (for the jails):

truenas: 				192.168.5.10
haproxy: 				192.168.5.20
mysql: 					192.168.5.30
postgresql:			 	192.168.5.30
ghost.yourdomain.com: 	192.168.5.40
cloud.yourdomain.com:	192.168.5.50
...etc...

the dataPools:

dbPool
	|- postgreSQL
    |		|-postgreSQL_14-data
    |- mySQL
    		|-mySQL_80-data

wwwPool
	|- site_1
    |- site_2
    |- ..etc..
    
windowsset_shared
	|-family photos
    |-shared docs etc


windowsset_user
	|-wife
    |	|-wifes unshared documents
    |   |-wifes unshared photos
    |   |-wifes ..etc..
    |-kid1
    |	|-kids unshared documents
    |   |-kids unshared photos
    |- ..etc..