You could try it with KaraDAV. Much simpler and works fine with the Nextcloud apps.

With new parts yes, but except for a brief period after a new console is released you can buy used PC parts for playing games of similar graphically fidelity for about the same price or slightly cheaper.

Gogs is what became Gitea, is what became Forgejo. The fork history is a bit complicated.

But if Gogs works for you, no need to change.

I was talking about Podman Pods. Sorry for not being clear.

Yeah, inside of Pods you can just use the container name and thus avoid hard-coding any IPs.

Yes it is a general purpose WebDAV server and should work with Zotero. I have not tried it with Zotero specifically, but I use it with several other apps that only offer normal WebDAV support such as Floccus for bookmarks syncing.

Nextcloud uses Webdav internally, but especially the Nextcloud apps expect a lot of additional non-standard extensions to WebDAV so that they don’t work with normal WebDAV servers. KaraDAV has reverse-engineered most of these extensions and thus the official Nextcloud Android and Desktop apps accept it as if it was a real Nextcloud. It is hovever limited to the file sync feature of Nextcloud, no calendars and such.

Prosody is a XMPP server and not a WebDAV server though.

Your loss, as KaraDAV works very nicely and is significantly faster than Nextcloud 😎

You are probably better of switching to a better ISP or renting a VPS in that case.

Have you tried running it without the cloudflare tunnel? Seems like an unnecessary extra complication.

As for NPM… I never used it, but Lemmy has a rather complex Nginx setup that probably can’t be acuratly mapped with a simplistic UI like that.

Yeah, beginners are probably better served with Yunohost.

Well usually the opposite happens. People make many releases and outsource the testing to unsuspecting users.

This is IMHO fine if you clearly mark these releases as release candidates or such, so that people can make their own risk judgement. But usually that isn’t the case and one minor version looks like any other unless you have a closer look at the actual changes in the code.

I think the better option is to have many releases that are clearly marked as beta-test releases or release candidates for those that don’t mind testing stuff.

“Bigger” is a bit missleading here. Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

But “bigger” in the other sense i.e. meaning slower, means that there was more time for people to run pre-release versions if they are adventurous and thus there is better testing.

Of course this assumes that there are actual beta testers and that it is easy to do so by creating such beta releases.

Yeah, running it like that here. Works fine for the most part, except that the hybrid inverter that I bought advertised “UPS” mode, but it doesn’t actually switch fast enough to avoid also adding a proper UPS (but running an UPS chained is another issue…).

It sounds a bit strange as it does actually run off the battery all the time (unless below the minimum charge limit, when it seamlessly switches to grid power automatically), but due to legal requirements it needs to switch to another supply mode when the grid power fails and this switch is not entirely seamless on my inverter.

Rebuilding my main router to work with 10gbe fiber that recently became available here. Although it is a tad expensive, so I am not actually sure yet if I will upgrade my contract.

You can use the Nextcloud app with the much simpler KaraDAV backend. Works fine for photo backups.

You need to make sure you get a unique public IP from your home ISP. Some utilize a so called CGNAT which allows them to share one IP with multiple customers, but this makes self-hosting from home much more difficult. Less bad is a so called dynamic IP, which is unique but can change randomly. For that you need some system to automatically update your DNS records when a IP change is detected.

And yes, the domain registrar and dns server operator has an webinterface to associated your public IP with the domain name. The better and larger ones also provide an API to automate it should your public IP change.

There are many things you can do to improve security, but mostly you should run a firewall to not expose any internal services to the public internet.

Lemmy is very database write heavy once federated, so unless you get the nvme extension for your Rpi5 it will not work very well. The database is also very RAM hungry as a result.

Anyways, if it is just about testing, it should not be a problem.

Lemmy by itself should be accessible without a domain name, but federation depends on it. Just give it a try and access it via “localhost” or the local IP of the server hosting it.

A TLD is just a reference to an public IP. Basically you ask a server what IP does this name reference and that’s it.

TLS certificates (via Lets Encrypt) are necessary for participating in the federation and protect data like passwords of the users while being send to the server. It is not strictly speaking a security measure for your server.

As usual it depends (and TDPs are highly misleading). First of all the 6700k is a 14nm chip, Vs. 32nm for the E5-2620. And the 6700k is a Skylake generation chip, compared to Sandy Bridge for the Xeon, which brings significantly better power-states. But on the other hand the 6700k is much higher clocked and has turbo-boost, with the latter being notoriously power hungry (can be disabled in the bios though).

In my educated guess the 6700k will use significantly less power if it mostly idles or does only burst tasks, which is actually what most self-hosters have as as task-loads. But if you serve websites to thousands of users which results in a consistently high CPU load, the Xeon is probably overall the better chip, including power-consumption under load.

Edit: I realized now that it is a E5-2620v2, which is Ivy Bridge and 22nm. So the difference is probably less, but overall the same considerations apply.