Easiest is probably “certbot --standalone” which lets certbot use its embedded webserver.

Otherwise nginx and apache httpd are common and reasonable options.

Apache is plenty fast enough for self-hosting scenarios.

For local backup I like rsnapshot. It’s a script that uses rsync and hard links to create incremental backups.

The thing about it is that it’s super simple and easy to restore from since you just get a bunch of directories like “daily.0” and “daily.1”. To restore you just find the files you want with standard tools like find and locate and just copy files out.

There are other more advanced tools like restic, borg, duplicacy, etc. I use things like that for the off-site backups (I backup the “daily.0” directory from my rsnapshot backups).

You should buy a UPS if those things are concerns for you. If not, then don’t.

Yes, that’s the excuse I’ve been getting. Sorry to be vague.

not sure why you’re being downvoted.

LaNgUaGe EvOlVeS. 🙄

Yeah - that’s reasonable. I brought it up since it’s the #1 thing I always forgot about for some time and now it’s the first thing I check.

He look - I drive a car with a V8! I mean I know it only has 4 cylinders in-line but I count them twice and I like the letter “V” so in this specific context it’s a V8!

It’s just what it means in this specific context.

“I used the wrong words but I feel like justifying them as right.”

This is that whole “I know literally means literally the opposite of what I meant but deal with it” bullshit. Whatever, I’ll not argue with such lunacy. Words mean whatever you want them to.

What is it you think the “metal” is in in the phrase “running on bare metal?”

Your comment is irrelevant. Who cares in what directory or disk image the packages are installed? If I run in a “chroot jail” am I not “running on bare metal?” What if I include a library in /opt/application/lib? Does it matter if the binaries are on an NFS share? This is all irrelevant.

The phrase means to be not running in any emulation. To answer my question above - the “metal” is the CPU (edit: and other hardware).

edit2: I mean - it’s the defining characteristic of containers that they execute on bare metal unlike VMs and (arguably - I won’t get into it) hypervisors. There is no hardware abstraction at all. They just run natively.

Yes - in this context containers run on bare metal. They run directly on the host. They even show up in the host’s process list with PIDs. There is no virtual machine between an executable running in a docker image and the CPU on the host.

You’ve told us nothing about your hardware.

I’ve been running nextcloud for some time with this setup:

KVM virtual machine with 4 cores / 8 GiB RAM
docker image: `nextcloud:28.0.2-apache` with db: `mariadb:11.1`

The UI has never been what one would call… “fast”. Especially on first load of a page or directory. It’s been adequate for me though. Once I click around a bit it caches enough things to feel fairly responsive. I also mount /var/lib/nextcloud off a network share so I’m sure that hits my performance some as well.

Nextcloud leans on the database a lot so be sure to have a local and quick storage for it (no - don’t run it on your raspberry pi). There are also cleanup cron jobs and indexes that need to be updated when doing upgrades that help performance as well.

Have you created any indexes the new release might have needed? Nextcloud doesn’t create them by default.

https://help.nextcloud.com/t/some-indices-are-missing-in-the-database-how-to-add-them-manually/37852

Containers run on “bare metal”…

Containers run on “bare metal”.

I think you need to provide the criteria you’re using to define “best”.

Do I need to buy a more powerful device?

Yes? You seem to have answered that yourself.

Run “free” and see how much memory is being consumed. And “top” as well (hitting ‘m’ will sorry by memory usage).

Oh man this brings back memories! It is indeed a simple way to get some basic “site template” without needing a lot of infrastructure.

Sorry - I thought you didn’t know rather than were just offering completely useless information on purpose.

So you know - that’s the max power output rating of the power supply. The NAS can be using anything “up to” that amount. Likely well below it.