![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Noticeable difference loading the page? Loading photos? Uploading photos?
Photo files are relatively small, so an HDD is absolutely fine.
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.
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
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:
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.
Just flexibility and future proofing. Having/building a music library is very time consuming, so I’ve chosen to do it properly so there’s no work in the future.
Since my stuff is all FLAC it doesn’t matter what new lossy formats become popular 25 years from now. My music server will convert it on the fly to stream it to my phone.
The only downside to keeping everything in a lossless format is that over the years new formats emerge. mp3 used to be the only game in town, but now we have multitudes of lossy formats to pick from. By having your collection in mp3 format, you aren’t able to say “hey, this new format looks cool, let me switch to that”. By storing everything in a lossless format (FLAC), you can convert for mobile as you see fit.
I just updated my comment above with more info, FYI.
I’m not a pro at Docker, but I’ve spun up over 30 different services using Docker Compose so I’m more than a novice. I would say that Lemmy’s documentation is the worst I’ve ever seen.
The website points you at that compose file which is (I think?) designed for Ansible. I think there’s another example somewhere without all the jibbery joo, but I can’t search for it right now.
Edit: here it is https://github.com/LemmyNet/lemmy/blob/main/docker/docker-compose.yml
No idea why they don’t link to that one in the first place. I’d fix it if I knew how.
I think the docs recommend (and this is how I have it set up) leaving the go2rtc stream as you have it currently, and changing the stream path for the camera config to rtsp://127.0.0.1:8554/nursery
It was a typo in my compose file. Oops!
Wow. What are the chances?
Meh, even then. If they’re 60MB each that’s only 120GB.