Ideally, there’d be a simple RPM installer compatible with Alma 9 that I can point to a samba share that holds all the photos, kind of like what I do with Jellyfin. Also nice if it uses an otherwise unused port or I can easily set what port it uses.

My googling is finding a bunch of docker stuff, which always seems needlessly complicated to me vs an RPM… I’m also using a low powered x86 tiny computer to front JellyFin and would like to host this on the same computer vs needing another server.

Any ideas?

  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    Install docker: https://docs.docker.com/engine/install/centos/

    Then running a container is just same as installing an RPM, except you don’t have to download it first. You just docker run the container.

    You can probably get regular old packages for a lot of stuff, but a lot of stuff is packaged as containers because it makes everything easier for both the maintainer and the user.

    • Bookmeat@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      Containers are really only useful for scaling. I suppose there’s some benefit to isolation, but it’s not really that much better than just using correct permissions with SElinux.

      OP is kinda right. Containers get overused unnecessarily.

      • MangoPenguin@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        7 months ago

        They’re also useful because they’re easy to deploy, contain all the dependencies needed, portable, and isolate things breaking from affecting the host or other containers.

      • SDK@midwest.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        The confidence with which you make this factually incorrect statement is mind bending.

        • Bookmeat@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          7 months ago

          Sure, let’s add another layer of complexity for the user to set up their network, storage, and other external resources and call it easier and simpler.

          My point isn’t that containers are bad. It’s just that there is often a push to containerise workloads that don’t require containers.

      • uzay@infosec.pub
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        Containers are useful for a lot more things than scaling. E.g. portability, ease of setup, dependency separation.

  • ChrislyBear@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    I recently started using https://github.com/immich-app/immich

    It’s basically a self hosted Google Photos and it’s working really well. You can just mount your heap of photos into the container, declare it as external library and you’re good to go.

    After a few hours/days of training the face recognition, extracting meta data, generating thumbnails ans possibly transcoding videos you’ll have a very responsive and easily searchable timeline of ALL your pictures and videos.

    • Avid Amoeba@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      7 months ago

      I love how they literally ripped off Google Photos’ interface, including using the same Material icons. I could navigate it via muscle memory. 😅

  • Shimitar@feddit.it
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    Docker (better use Podman!) Is, I am afraid, hard to avoid nowadays. I fully agree with you that bare-metal deployment should always be an option.

    Its one of my biggest issues with immich/photoprism/librephotos but there is no way around that.

    Immich is the only container I have on my system… A necessary evil (joking).

    I know containers now, but still don’t like them too much. I am old I am afraid.

    But you shouldn’t be FORCED to use containers, that’s my point.

    • Phrey@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 months ago

      No one is forcing you to use containers for Immich. It’s simply the most robust way to support it for the team.

      You can just take a look at the dockerfiles and follow those steps on bare metal.

      • Shimitar@feddit.it
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 months ago

        No, I am forced to use containers because… There are no instructions for bare-metal installation and they also do not provide any instruction on how to build from sources (and I tried…)

        Also, there are no binary releases only docker-compose.

        All in all, immich cannot be deployed but with containers.

        No choice: not good.

        • Scipitie@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          A Dockerfile itself is the instruction set. There is a certain minimum requirement expected from a server admin that differs from end-user requirements.

          The ease of docker obfuscates that quite a bit but if you want to go full bare metal (or full AWS or GCS, etc etc) then you need to manage the full admin part as well - including custom deployments.

          • Shimitar@feddit.it
            link
            fedilink
            English
            arrow-up
            0
            ·
            7 months ago

            Indeed I am a quite proficient sysadmin for my home server, while not a professional one.

            I didn’t consider a docker file as instructions for bare metal install, thanks for the suggestion. I am currently using podman with immich because its release cycles are too fast for me to catch up otherwise.

            I am thinking to experiment with something different from immich because, while its a great tool, it’s “just” (no pun intended) a backup solution for mobile devices and I need something more than that.

            I was considering https://damselfly.info/ which looks more like the workflow I am looking to implement.

        • Phrey@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          Like I said, if you follow the dockerfiles you will end up with a similar result on bare metal.

          It’s your own decision if you want to deviate from what the developers want to support.

          A project doesn’t need to produce binary releases.

  • MangoPenguin@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    7 months ago

    The simplest option is just connect via SMB, WebDAV, NFS, etc and browse using your normal file browser.

    There are a ton of various web based photo galleries: https://github.com/awesome-selfhosted/awesome-selfhosted?tab=readme-ov-file#photo-and-video-galleries

    Some can be hosted on your basic Nginx+PHP+MariaDB stack which is more complex to set up, but most are going to be meant for deployment on Docker because that makes everything very easy.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    Get out of the anti container mindset. Getting started with docker takes half an hour. You need to learn 3-4 commands to use other people’s services. Everything is easier than RPMs afterwards.