Use mcfly and it will be even better.

From their README. Have you looked at their forum?

We cannot provide direct technical support. Get help running this software in your own environment in our unofficial community forum.

This thread has a link to someone’s Dockerfile for their development.

Here is two enteries from my Caddyfile:

ip.domain.tld:80 {
        respond "{client_ip}" 200
}


git.domain.tld {
        reverse_proxy forgejo:3000
}

This is all I need and Caddy will handle the rest. I have created a network with podman/docker that I add to any container that I need to reverse proxy to.

I meant more figuratively. Finally managed to move my compose files to nix files thanks to compose2nix. One thing that throw me for a loop was that podman (or perhaps nix) creates a service named <backend>-<service>. Compose2nix handles this accordingly but I had a few hours of head scratching until I figured that out.

That was an interesting and enlightening read. Thanks!

From all the hate you see, it does look like that. It is not?

I mean keep using port 22 on the server and redirect whatever port you want in your firewall (your router unless you have a dedicted fw) to port 22. Don’t change the ssh port on the server at all.

Why change the SSH port of a home server, which most likely is not reachable from the outside anyway?

And if it is, why change it on the server and not in the fw?

I installed a new server at home and went with NixOS. It looks super cool but it takes so much time to learn everything. The only thing keeping me from going back to Debian is how easy it was to permanently mount drives (and save a configuration for any future install or mishaps).

(I.e. mount, nixos-generate-config, nixos-rebuild switch and done!)

Swanstation

Thanks! Found their repo: https://github.com/libretro/swanstation

What’s the new one called?

From the readme:

RomM (ROM Manager) allows you to scan, enrich, browse and play your game collection with a clean and responsive interface. With support for multiple platforms, various naming schemes, and custom tags, RomM is a must-have for anyone who plays on emulators.

Go to a concert.

I can’t say I agree or disagree because I don’t have any data to prove your right nor wrong. I can say that I understand some shit people give Java but your argument was a first for me. I was intrigued.

That’s the first time I ever hear someone call Java a legacy language.

Is it considered best practice to run a bunch of different compose files, and update them all separately?

tl;dr I do one compose file per application/folder because I found that to suite me best.

I knew about docker and what is was for a long time, but just recently started to use it (past year or so) so I’m no expert . Before docker, I had one VM for each application I wanted and if I messed something up (installed something and it broke or something), I just removed the entier VM and made a new one. This also comes with the problem that every VM needs to be stopped before the host can be shutdown, and startup took more work to ensure that it worked correctly.

Here is a sample of my layout:

.
├──audiobookshelf
│  ├──config
├──diun
│  └───data
├──jellyfin
├──kuma
├──mealie
│  ├──data
│  └──pgdata
├──n8n
│  ├──n8n_data
│  └──n8n_files
├──paperless
│  ├──consume
│  └──export
├──syncthing
│  └──data
└───tasksmd
    └──config

I considered using one compose file and put everything in it by opted to instead use one file for each project. Using one compose file for everything would make it difficult to stop just one application. And by having it split into separate folders, I can just remove everything in it if I mess up and start a new container.

As for updating, I made script that pulls everything:

#!/bin/bash

function docker_update {
    cd $1
    docker compose down && docker compose pull && docker compose up -d
}
docker_update "/path/to/app1"
docker_update "/path/to/app2"
docker_update "/path/to/app3"

Here is a small sample from my n8n compose file (not complete file):

services:
  db:
    container_name: n8n-db
    image: postgres
    ...
    networks:
      - n8n-network

  adminer:
    container_name: n8n-db-adminer
    image: adminer
    restart: unless-stopped
    ports:
      - 8372:8080
    networks:
      - shared-network
      - n8n-network

  n8n:
    container_name: n8n
    networks:
      - n8n-network
      - shared-network
    depends_on:
      db:
        condition: service_healthy

volumes:
  db_data:

networks:
  n8n-network:
  shared-network:
    external: true

shared-network is shared between Caddy and any containter I need to access to externally (reverse proxy) and then one network that is shared between the applications.

It’s a spring framework project. It is a solid choice if Java is your language and you need a predefined web server to build on.

Also, what is odd with Java?

Love docker. Updating has never been easier.

Agreed, have used both android and iOS over the years and both OSes has their pros and cons. Currently staying with iPhone because nothing beats their face ID in my opinion.

I am currently looking into borg because it can take incremental backups. I just need figure out how I should handle a running system, if I need to turn of all my docker images or if there is some kind of snapshot function I can use.

From what I read on their FAQ, Borg cannot verify the integrity so I would need to turn everything off during the backup process. A filesystem like ZFS could have solved that problem (cannot find the link, something about shadow copy I think?) but since I don’t have a backup yet nor physical access, I need to work with what I have.

I think I will set it to take a backup every night.

EDIT: Maybe it can verify integrity? Still trying to find information on my use case. https://borgbackup.readthedocs.io/en/stable/usage/check.html