Not really. Personally I’d allow the service account running jellyfin only access to read media files to avoid accidental deletion but otherwise no.

Also, jellyfin docs have a sample proxy config. You should use that. It’s a bit more in depth than a normal proxy config.

Honestly, if you know nginx just stick with it. There’s nothing to be gained by learning a new proxy.

Use Mozilla’s SSL generator if you want to harden nginx (or any proxy you choose)- https://ssl-config.mozilla.org/

Which they expressly said they wanted in the comment I responded to…

Personally I’d recommend restic and backblaze b2 if I were you. Dedup and quick.

Dude, I speak like four languages. It’s a dumb name in my opinion.

Because like the op said- it’s not clear how it’s to be pronounced.

I’ve learned some Esperanto. Doesn’t mean it’s a great base for naming a project.

I think it’s interesting but also still a terrible name. But I fear the time to change it is long gone.

Just use a sonatype nexus 3 image and proxy docker hub, etc. Then you pull images through it.

It is BUT you are limited to their test servers for mobile notifications and they honestly suck. It’s a coin flip whether you get them. And if you want better you have to set up your own container system like them with firebase and Apple Dev ids.

I like it still but for a Greenfield project I’d probably try matrix 2.0 on synapse with element x as the mobile app.

If you don’t need notifications I’ve actually found just adding it to Firefox as a pwa works well for me. Mobile interface is surprisingly good.

Jackass says most war mongering ignoring the actual country invading another.

Typical.

I distinctly remember yum/dnf should be using a loop. Forget why but it’s recommended. Here’s a snippet from my playbook. Simply make the vars as you need and run.

  - name: Install flathub as remote
    ansible.builtin.shell:
      cmd: flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
    tags:
      - apps

  - name: Install flatpak apps
    community.general.flatpak:
      name: "{{ item }}"
      state: present
    loop: "{{ flatpaks }}"
    tags:
      - apps

  - name: Remove some default unused packages
    ansible.builtin.dnf:
      name: "{{ item }}"
      state: absent
      update_cache: no
    loop: "{{ remove }}"
    ignore_errors: true
    tags:
      - apps

  - name: Install our packages
    ansible.builtin.dnf:
      name: "{{ item }}"
      state: present
      update_cache: yes
    loop: "{{ rpms }}"
    ignore_errors: true
    tags:
      - apps```

On mobile. Apologies if formatting is off.

Exactly. I don’t know if the AIO image was used and how that all works (I stay away from that and the snap which is just an abomination) but no one should try to selfhost anything for prod unless they know exactly how it works. That and have a staging env. If you’re not up to the task then just pay for some commercial hosting (even if it’s just Nextcloud that is hosted elsewhere.)

I’ve run the nextcloud image (just docker.io/nextcloud IIRC) pinned for years with k8s and it’s durable and fine. It stays put and I just take the time to update my testing instance, make sure it all works with some cheap smoke tests, then upgrade prod.

I haven’t looked terribly far into it but zrok (SP?) is based on openziti

Pita= pain in the ass

I really want to like one of these. I’ve tried it before but can anyone using this or similar tell me how it differs and improves upon just using Firefox sync?