I want to print from a web page: upload the file, hit print button.

In this way I can print from whatever device I want even without any driver installed or configuration.

Nginx "just works(tm)" had never got into the way, its been rock solid and has not changed significantly over the years.

Why would I need something else?

Connection closed means somebody is listening to the port and failing/not willing to reply.

Unless some network middlemen is closing your connection (ssh should be on port > 1024 to be safe from ISP throttling), your ssh server is severely strained (oom, disk full...) or your F2B is kicking in.

Definitely yes. I only see positive benefits by using a reverse proxy. From the fun of learning new stuff to the added security (which is never a downside) and being ready to expose outside in a future.

Man, at 55 I will be still running ironman's... Hopefully. And trails. Let's keep arthritis for the 70's, shall we?

Agreed and big thumbs up for Gentoo. Our distro never gets enough love!

What if your home network goes down while you are away for a week and you cannot get it back online?

Not a risk I am willing to take, so a backup server would be required.

Here goes my experience.

When I started the self hosted trip, I was against containers and tried to avoid them at all costs. Then I learned about containers, and now I still am against containers but less vividly so. I have used them and still use them.

Containers are good for the self hoster because they deliver fast deploy and easy testing of lots of services quickly. They are good for developers because they can provide one common installation approach that reduces greatly user issues and support requests.

But containers also have downsides as well. First of all they make the user dumber. Instead of learning something new, you blindly "compose pull & up" your way. Easy, but it's dumbifier and that's not a good thing. Second, there is a dangerous trend where projects only release containers, and that's bad for freedom of choice (bare metal install, as complex as it might be, need to always be possible) and while I am aware that you can download an image and extract the files inside, that's more an hack than a solution. Third, with containers you are forced to use whatever deployment the devs have chosen for you. Maybe I don't want 10 postgres instances one for each service, or maybe I already have my nginx reverse proxy or so. I have seen projects release different composer files for different scenarios, but at that point I would prefer to deploy on bare metal.

Said so, containers are not avoidable today, so study and embrace them, you will not be disappointed as its a cool piece of tech. But please stay clear of docker and go podman instead. Podman doesn't rely on a potentially insecure socket and does not require an always running daemon. Podman also by default doesn't force you to run services as root which you should never do. Also, networking feels clearer on podman and podman feels more .modern by using nft instead of iptables. Yes most of this can be fixed on docker, but since podman is a drop in replacement, why bother? Also, podman is truly open source while docker, shockingly, its not.

Here is my wiki page on the subject: https://wiki.gardiol.org/doku.php?id=gentoo:containers feel free to read it.

One last thought: updating containers should not be taken lightly. Its so easy and fast that you might be tempted to setup cron jobs or install watchtower, but you will end sooner or later with a broken service and lost data. So backup, always backup, and keep updating with rationale.

Tldr: containers are unavoidable today and are a cool piece of tech worth investigating. Don't blindly use them as there are security issues involved, and I hope the trend of making containers the only way doesn't take hold, because containers also make self hosters dumber and that's not good.

Now the big question is: are you an Arch or a Gentoo lover? Just joking.

Good job! Keep it up

I want to try this...

Yes I mean https://mydomain/immich, like all other self-hosted tools do.

Auth just with name, please why email??? And maybe get that name from already performed proxy auth, not many tools does, but some do. Its a neat feature.

But immich requires an EMAIL and will also enforce it, so you cannot fool it with a plain username. I just want consistency with the rest of the world.

Docker is enough? Maybe, but bare metal should always be an option. Always. Just write down some basic steps or publish the build script already in place for releases.

And for albums I mean that it should recognize that external libraries have already albums in the form of subfolders.

I will open tickets and feature requests of course, this post is here to share my findings and your aggressive reply is out of place.

By the way, I am talking with strangers on the internet and the objective is to help solve those issues.

Unfortunately internal memory gave up quickly so only like 3 years of fun