fluckx

My supernote hasn’t advertised anything ( besides an occasional marketing email ): www.supernote.com

Category: e-ink device ( read+write ).

I also did it with this.

While you can change it afterwards, it might be worthwhile to check a setting in immich on how it organizes the photos on disk you upload.

I changed it to year/month/photo-id because I find it convenient, but it does not organized them like that for backups.

You can change it at a later date and run a job to “fix it”, but it might be worthwhile to set it up correctly from the start ( if this matters to you ). So no harm done if you change your mind later.

I’m on board with this. It sucks and it makes things a lot easier to be able to have SSO.

But I’m also peeved the SSO tax is nearly always in the enterprise tier and never in the first paying tier. Even if you’d want to pay for it, the enterprise cost is usually a multitude in price with features you likely don’t need.

They just know companies have policies that enforce SSO for compliancy reasons and are forced to pay.

But as a self hoster the enterprise tier is even more disgustingly expensive.

But the open source projects we use and love also deserve contributions ( financially ). But as a self hosted there’s also a financial incentive to self host and not take everything as a SaaS ( besides the obvious take control of your data ).

How do you enforce consistent backups of the database? Do you dump the data periodically? Copying the data on the docker volume won’t give you consistent ( and possibly corrupted ) backups IIRC if the database itself isn’t stopped.

I’d rather not send credentials over plain text. Even in a homelab environment