The containers will store their data in volumes, and ideally those volumes are individual ZFS datasets. The containers themselves are stateless, and you can just boot them up with the volume to “restore” them.
However if you want to learn proxmox anyway this is a moot point anyway.
Some concerns:
Anything based on nagios supports custom checks, via any executable script.
apt install nginx
cp -r my-files/* /var/www/
I wouldn’t use it unless you have a separate room somewhere, they are VERY loud.
I disagree with this, container runtimes are a software like all others where logging needs to be configured. You can do so in the config of the container runtime environment.
Containers actually make this significantly easier because you only need to configure it once and it will be applied to all containers.
Docker stores that stdout per default in a log file in var/lib/docker/containers/…
Containers don’t do log rotation by default and the container itself has no say in the matter. You have to configure it in your container runtime config.
In the oidc provider in authentik you have to enable sending the groups. I forgot what its called.
Roles in authentik are for permissions in authentik. You want a group instead. Group memberships are send via OIDC.
Check out EFF cover your tracks: https://coveryourtracks.eff.org/
The results are very interesting. For me, the most unique thing about my browser was that I had two system languages, and so the accept-language header was very unique.
I now use vanadium (graphene OS), which simply sends made up values for a lot of headers, and so makes fingerprinting harder.
In general, you should try to be as “normal” as possible, use standard settings for everything, just accept English, etc…
I would put truenas on the NAS, also put a VM on truenas with 16-24G of RAM.
Create a kubernetes or docker swarm cluster with server 1 and the nas vm and just have everything as containers. This way you just have one resource pool, and the containers will be started wherever there are enough resources available. The containers will mount NFS shares from truenas which truenas will create automatically as ZFS datasets. ZFS supports snapshots.
This is probably the way, because a traditional “mail server” is actually 4-5 different servers working together.
And they can all be very easily misconfigured to break everything completely. Great learning experience though.
GrapheneOS provides users with the ability to set a duress PIN/Password that will irreversibly wipe the device (along with any installed eSIMs) once entered anywhere where the device credentials are requested (on the lockscreen, along with any such prompt in the OS).
No I’ve never seen this. Usually they send you an email to the admin address of the domain with the code.
Its always encrypted, just that the keys are in RAM when it runs.
In case of graphene though you can have a distress pin that wipes the encryption keys, making the phones content irrecoverable.
I’m using it and never going back.
It’s not just the privacy aspect, but the fact that most results in other search engines suck. The first two pages would usually be ads - first the bought ones, then company websites and copywritten blogs. I get that way less with kagi. I find useful stuff faster and my brain is less polluted.
Nextcloud has collabora integrated.
I would put this stuff behind VPN.
Exactly the opposite for me, using official container images is a major time save.