Editing Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software (section)

== Step 2: Understand how this will be set up differently from stock setup. ==

<span id="how-youre-supposed-to-use-immich"></span>
==== 2.1 How you’re supposed to use Immich ====

The stock setup of Immich, by default, is to have Immich upload your images &amp; videos from your phone to the immich server. You control your library on your phone &amp; on your server in the immich application.

<span id="syncthing-conflict-with-immich"></span>
==== 2.2 Syncthing conflict with Immich ====

Didn’t we already set up syncthing to do this? Yes, we did!

I don’t want to use Immich to sync my phone’s '''DCIM/Camera''' folder, and then syncthing for everything else. In my opinion, it doesn’t make sense to use Immich by itself to do this; Immich is for photos &amp; videos, it is not for Music, Documents, &amp; all the other folders on our phone. If we used syncthing for those files &amp; folders, and used Immich for photos/videos, that means we have two applications running at the same time, that do the same thing. This means 2 points of failure rather than 1.

Syncthing was designed with one purpose in mind; transfer files from device to device. I would prefer to use a tool that was designed for the job.

As a result, I am going to set up the <code>~/androidbackup/DCIM</code> folder as an '''external library''' in Immich.

<span id="attaching-zfs-pool-to-immich"></span>
==== 2.3 Attaching ZFS pool to Immich ====

See Also, remember the giant ZFS pool we created? On my setup, that’s over 100 terabytes of stuff! Much of that are old images &amp; videos that are not in my phone photo backup directory. I want to see those in Immich.

We created a Samba share for our ZFS pool so we could access it from elsewhere. I am going to create a '''read only''' samba share that is mounted on <code>~/Pictures</code>, and then set this up with Immich as a '''second external library.'''

TL;DR - Immich will have access to everything stored in your ZFS pool archive as a photo library, as well as your android phone’s photos. This allows me to perform machine learning on everything; my android phone photo backups, current android phone photos, as well as all of my stuff from the past 15 years all within one piece of software.

After this is done I will be able to use the search feature and find photos I forgot about within seconds, dating back 15 years. Awesome. :)

<blockquote>'''QUESTION:''' Why do we want the zfs pool share to be read only?

The '''androidstuff''' virtual machine that houses our syncthing backup of our android phone is going to be backed up regularly to our zfs pool. We have a copy of that being backed up every week. The entire ZFS pool, for me, is over 100 terabytes - so having version controlled backups is much more difficult.

As a result, I am personally much more protective of the data on my zfs pool than I am the data on my androidphone backups.
</blockquote>
<span id="step-3-mount-a-read-only-samba-share-of-the-zfs-pool-for-immich-onto-the-androidstuff-virtual-machine"></span>