Comment on please recommend a simple selfhosted photo gallery

• derin@lemmy.beru.co ⁨4⁩ ⁨days⁩ ago

  I run Debian on my VPSes. But, also, I’ve been through the path of doing what the PKGBUILD does, which is read the Dockerfike and manually execute the steps: I think it’s pretty problematic to have to do that every update cycle. Got Immich set up, looked at what I’d have to do every time I want to run an update, and "nope"d out.

  With server side software like this, which will usually be running behind a reverse proxy and will connect to a postgres dB (or other services like Redis), I kind of don’t want to fight the software/make guesses to create these connections. I also take umbrage with the nginx proxying “example” configurations - just tell me what needs to be proxied to where and let me handle the rest; it’s a server, you don’t know my setup. Case in point, I don’t use nginx.

  I like photofield because it’s a single binary (thanks, Go) listening on a port. I proxy what I need to it, and let it run.

  Final note: I’m not knocking Immich, or the people who run it. I just think it’s lazy to distribute software with Docker because it encourages devs to get to write what I consider to be poorly designed software (E.g. Software with hard coded paths as strings, because everything is expected to be in the same place on every system - basically very rigid defaults). As a guy who knows his systems well, it annoys me I can’t manage them my way and need to run a nebulous docker container set up by some web developer. (some shade thrown there, my bad)

  You don’t have to agree with me, I’m Don Quixote and this is one of my windmills.

  original

  • Cyber@feddit.uk ⁨4⁩ ⁨days⁩ ago

    Yeah, I get it. I do think containers encourage lazy integration - could be hard coded paths, or things like leaving apt in there, so no worries.

    original