“Easy” might just be relevant to your experience. You can follow along with the Ansible instructions, or go your own way with Docker and Docker Compose.

Both methods require a bit of work to get spun up, but it’s not too bad.

Meh, even then. If they’re 60MB each that’s only 120GB.

I’ve used it plenty of times for other reasons. I can never remember what kind of CPU I have and it tells me. I can’t even remember how much RAM I have, and it tells me that, too.

I’m sure the next thing someone is going to do is tell me the individual commands to find that info, but I can’t be bothered with that.

Noticeable difference loading the page? Loading photos? Uploading photos?

Photo files are relatively small, so an HDD is absolutely fine.

Oh thanks for the heads up

I installed MagicMirror onto a Raspberry Pi using a pre-made Magic Mirror OS image (can’t remember where I got that, but I think it’s relatively “official”, so maybe their website? It comes ready to go with Docker and everything you need set up.

Then I installed this https://github.com/pelaxa/MMM-ImmichSlideShow and configured it.

I actually found some additional configuration options by going back in the chain to the project it’s based on (linked at the top of the readme). Their documentation included some additional stuff that actually works with MMM-ImmichSlideShow. Edit: Looking at my config again, and all the stuff is in the MM-ImmichSlideShow documentation now. Maybe they updated it.

Then I hooked up an old monitor, put it in vertical mode, and that’s it.

It was actually kind of difficult to figure out how to get the display to work in vertical mode. A lot of old forum posts are the “old” way of doing it. I ended up making a cronjob that runs 60 seconds after boot and runs some command that rotates the display. I’ll dig it up if you need me to, but since MMM-ImmichSlideShow is still broken it’s not turned on right now so I can’t check it. Here’s the line from my crontab to rotate the display: @reboot sleep 60 && DISPLAY=:0 xrandr --output HDMI-1 --rotate right

Aha, that must be it. The photo in question is 6.7MB

I’m able to save a trail without any photos, but if I try to add a photo it lets me select the photo, but saving the trail gives a toast notification in the bottom right that says “Error saving trail.” The web, db, and search logs don’t show any errors.

Mine was having some weird problem with docker, I think it must be a docker bug. Basically it put the Wanderer stuff at the very bottom of the routes (running “sudo route” on Debian lists the routes). The last entry in the routes table needs to be eth0 or the equivalent so that stuff can loop back to the beginning of the list. At least that’s my understanding.

So anyway, to get around that bug/limitation I had to create a static docker network which I called “wanderer-static” using docker network create --attachable -d bridge --subnet 172.28.0.0/16 --gateway 172.28.0.1 wanderer-static. Choose a subnet that’s not being used already.

Then in the docker compose file, point everything at that network by:

Removing

 networks:
   wanderer:
     driver: bridge

Adding

networks:
  wanderer-static:
    external: true

And finally, pointing each service to that network. Under each service you should have:

    networks:
      - wanderer-static

I also had to update the ORIGIN and whatever else to http://wanderer-static:7000, etc.

Immich is the only thing I run where I check the change log before doing any sort of update. It’s worth it, though. Great software.

This update broke my janky little raspberry pi “photo frame” which uses MagicMirror and a plugin. I probably just need to rename a port in the plugin or something (or wait for an update).

Looks cool. I have it up and running with the docker compose provided. Every time I try to create a user it says “Error creating user”, and the logs say [ERROR] [23:30:00]: Login failed. Unable to obtain cookie.

Edit: I got it working, just had to updated some of the network stuff in the docker compose. The networking in Portainer is a bit “complex”.

I can’t get photos to work. Oh well.

Linux ISO is slang for pirated content. They were clearly joking. https://www.urbandictionary.com/define.php?term=Linux+ISO

A “joke” often references material that is related, but not the same.

I think they were joking.

The upgrade went smoothly for me. Be smart with your backups with this one!

Upgrading to postgres 16 was the hardest part. You need to pg_dump the lemmy database, upgrade to postgres 16 (which will complain in the logs that the current data isn’t compatible), delete the database folder (don’t delete the backup file from pg_dump!), then import the backup file into postgres 16.

I had already upgraded pict-rs to version 0.5+ so that was easy.

Then I compared the new lemmy.hjson with what I already had to get the new pict-rs setting for proxied images (turned off for now).

Overall a lot more complex than previous upgrades.

Be smart with your backups with this one!

One more thing to consider if you’re using Debian 12 is it comes with postgres 15, so if you you’re using the bare metal to make backups, you’ll need to install postgres 16 using the instructions here.

This is honestly the most confusing and complicated part of self-hosting.

I agree! It took me years to finally decide to buckle down and wrap my head around what a “reverse proxy” is. Once I figured it out things became so much more usable and fun.

Combined with DNS redirects in my LAN (to get around NAT loopback), things are very easy to use.

FYI here’s a link to the other compose file I was talking about: https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml

I’d say SSD or anything else non-spinning is a waste of money for most people’s needs. There are fringe cases, of course, like people who are editing gigantic video files or whatever.

I have a bunch of WD HDD’s that I shucked a while ago, they’ve been running non-stop for over 5 years last time I checked and I haven’t had any problems. That being said, I think Toshiba is usually considered “better”.

Either way, you shouldn’t rely on the reliability of any drive, SSD, HDD, or otherwise. If you have a backup then your worries go out the window and you can live life in peace!

The docker instructions are a hot pile of garbage, unfortunately. The referenced docker compose file, for example, is for installing via Ansible I think. There’s another Docker Compose file somewhere in the GitHub which is formatted for regular installation.

Lemmy is little too complex for a one click install.

Lemmy consists of:

1. Lemmy
2. Lemmy-ui
3. Postgresql
4. Pict-rs
5. Probably something else I’m forgetting.

Each one of those has a number of environmental config options that need to be set before running it all. You need a domain name so that other instances can reach your instance. Your database needs a password, Pict-rs needs to know where to store things, etc.