Interesting - I didn’t see that. They say “You can add your own copyright as well”, so you don’t have to give up your rights to the code. They do still need to comply with the terms of the Apache license.

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.

Maybe I just haven’t encountered any bugs that took a long time to fix. It’s been pretty reliable for me.

I’m a software developer that focuses on front end development (full-stack but I like frontend more) so I’m pretty picky about UI/UX. Boost feels very nice and polished.

I like Boost.

Last time I said this, I got shunned for recommending a closed-source app. I generally try to stick to open-source, but Boost has a good UI, works well, and bugs are fixed quickly.

Thanks for the info. 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 and I’m not sure if I should continue using it, or switch to something else.

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

We still call them weeds. It’s called a whipper snipper because it snips weeds by whipping them.

Australia has been using tap to pay for around 15 years now, whereas QR codes weren’t in widespread use in the country until COVID. There’s no reason to switch from NFC to QR given practically every bank’s app natively supports NFC payments now (no need to use a third-party wallet if you don’t want to)

The US is a different story… It took a looooong time for NFC payments to be adopted. I’m an Aussie living in the USA, and some of the US banks I use didn’t support contactless payments until a few years ago!

My car uses UWB (BMW Digital Key Plus) to automatically unlock when I’m walking towards it, once I’m pretty close. Maybe 1 meter (3 feet) from the car, in any direction. It has NFC as a fallback too - if the UWB thing fails for some reason, I can tap the phone to the door to unlock it too.

We call it a “whipper snipper” in Australia lol

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”.

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.