Their contribution agreement forces you to give up copyright to them.

The license just looks like the standard Apache license though, which doesn’t require this. With the Apache license, contributors still own the copyright to their code, but they license it to the project. Did you see a document in the repo that says something different?

if you need a POSIX interface

SSHFS isn’t POSIX compliant. It doesn’t support hard links, file locking, atomic renames, full support for changing file permissions, umasks, and probably other things.

Versity S3 Gateway is another option that’s trying to focus on simplicity. https://github.com/versity/versitygw

Out of all these, SeaweedFS is the most scalable. Seaweed’s design is based off some of Facebook’s whitepapers about their warm storage system, and it works especially well for use cases that have a very large number of small files (like images).

SSHFS is very unreliable. At least use NFSv4 or even SMB/CIFS.

Practically every other object storage provider offers an S3-compatible API.

It looks like there’s no way to migrate from Conduit. If I reinstall from scratch using the same domain, and create an account again, will everything still work properly including federation with other servers?

My server is just for myself.

What did you end up doing? I’m still running Conduit at the moment.

I like Pushover too. I’ve been using it for over 10 years now.

It’s worth noting that Proxmox uses Debian. It’s essentially a collection of Debian packages, and you can install Proxmox on top of an existing Debian system: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie

Proxmox lacks a Docker UI though, which is annoying. One of the reasons I’m using Unraid at home is because it supports KVM, LXC, and Docker, all in the same UI. (LXC is a plugin rather than being available out-of-the-box, but it works very well)

(and no, Proxmox’s new OCI container support isn’t it - that just converts the container to LXC and doesn’t handle upgrades)

Unraid is pretty beginner-friendly, so it’s what I’d recommend too.

I use it too. I have over 20 years experience running Debian servers and can write a docker-compose.yml file and Nginx config from scratch, but sometimes it’s nice to have a decent web UI that mostly “just works”.

If you set it to update your compose automatically it will notify you and create a log, it something goes wrong you can easily revert it from the dashboard. Did I get your question right? Let me know if you meant something else.

What I meant was does it handle multiple docker-compose files? I have a bunch of them - one for Immich, one for Lemmy, etc.

Copying my comment from the homelab community:

I haven’t tried it yet, but here’s some initial thoughts:

Does it support multiple separate docker-compose.yml files? It would be useful if it could pull the list of containers directly from Docker rather than having to paste the docker-compose.

Does it pull changelogs so that the user can tell if a change is a breaking change that’ll require extra work?

It would be useful to support Webauthn/FIDO2 2FA instead of just TOTP. TOTP is being slowly phased out due to its weaknesses (it’s phishable). Similarly, it’d be useful to support single sign on using OIDC (OpenID Connect) as a lot of self-hosters use Authentik, Authelia, or Keycloak to have one login for all their self hosted services.

Automatic updates for bug fixes (e.g. 1.0.0 to 1.0.1) are usually fine - it’s major and minor updates that are scarier. I’ve never used Watchtower so I’m not sure if it has an option to only allow bugfixes.

I haven’t tried it yet, but here’s some initial thoughts:

Does it support multiple separate docker-compose.yml files? It would be useful if it could pull the list of containers directly from Docker rather than having to paste the docker-compose.

Does it pull changelogs so that the user can tell if a change is a breaking change that’ll require extra work?

It would be useful to support Webauthn/FIDO2 2FA instead of just TOTP. TOTP is being slowly phased out due to its weaknesses (it’s phishable). Similarly, it’d be useful to support single sign on using OIDC (OpenID Connect) as a lot of self-hosters use Authentik, Authelia, or Keycloak to have one login for all their self hosted services.

Where is the website template from? I’ve seen the exact same one before.

You can run your own AI locally if you have powerful enough equipment, so that you’re not dependent on paying a monthly fee to a provider. Smaller quantized models work fine on consumer-grade GPUs with 16GB RAM.

The major issue with AI providers like Anthropic and OpenAI at the moment is that they’re all subsidizing the price. Once they start charging what it actually costs, I think some of the hype will die off.

I definitely agree with you!

I’m using AI a little bit myself, but I’m an experienced developer and fully understand the code it’s writing (and review all of it manually). I use it for tedious things, where I could do it myself but it’d take much longer. I don’t let AI write commit messages or PR descriptions for me.

At work, I reject AI slop PRs, but it’s becoming harder since AI can submit so much more code than humans can, and there’s people that are less stringent about code quality than I am. A lot of the issues affecting open-source projects are affecting proprietary code too. Amazon recently had to slow down with AI and get senior devs to review AI-written code because it was causing stability issues.

… did you read the same article as everyone else? I can’t tell if you’re joking or not.

I think the blurb was posted by the submitter (@vegetaaaaaaa@lemmy.world) rather than being a part of the link.

If your AI is making PRs without you, that’s even worse.

This is happening a lot more these days, with OpenClaw and its copycats. I’m seeing it at work too - bots submitting merge requests overnight based on items in their owners’ todo lists.