I have explained my issues in my other posts. Do you have a specific question?

How does it compare to LocalSend?

wow you are getting in quite a nonsensical defensive mood here. I gave my opinion on it and warmaster asked for clarification. If you want to use it go ahead I just pointed out the red flags. If you think it is hateful that people read the readme of your favorite project you really need to grow up. A readme is not the place for absurd ‘promotion’ like it’s a product sold on TV.

Also it’s not FOSS but a selfmade variation on Apache 2. Check the reddit link, even the author claims it is not FOSS.

It is becoming an important threat to you. Managing servers, applications and data is very complex, and the problem is that you cannot do it on your own: how do you know that the server application where you store your family photos has a secure code? it was never audited.

How do they fix this? Do they audit and approve all source code? Do they submit security patches to the apps they have in their repo?

In fact, the recent LastPass leak happened because a LastPass employee had a Plex server that wasn’t updated to the last version and was missing an important security patch!

How do they fix this? Auto updates? Those are going to bite you in the ass extremely hard at some point.

Things like this are completely untrue:

Additionally, because every new self-hosted applications re-implement crucial systems such as authentication from scratch everytime, the large majority of them are very succeptible to being hacked without too much trouble. This is very bad because not only Docker containers are not isolated, but they also run as root by default, which means it can easily be used to offer access to your entire server or even infrastructure.

Most tools currently used to self-host not specifically designed to be secure for your scenario. Entreprise tools such as Traefik, NGinx, etc… Are designed for different use-cases that assume that the code you are running behind them is trustworthy. But who knows what server apps you might be running? On top of that, a lot of reverse-proxies and security tools lock important security features behind 3 to 4 figures business subscriptions that are not realistic for selfhosting.

Scaremongering and lies.

Then let me tell you this: Cosmos does not solve any of the risks they paint in their vision. You are lulled into a false sense of “security” after they frightened you.

Why use Cosmos?

If you have your own self-hosted data, such as a Plex server, or may be your own photo server, you expose your data to being hacked, or your server to being highjacked (even on your local network!).

It is becoming an important threat to you. Managing servers, applications and data is very complex, and the problem is that you cannot do it on your own: how do you know that the server application where you store your family photos has a secure code? it was never audited.

Even a major application such as Plex has been hacked in the past, and the data of its users has been exposed. In fact, the recent LastPass leak happened because a LastPass employee had a Plex server that wasn’t updated to the last version and was missing an important security patch!

That is the issue Cosmos Server is trying to solve: by providing a secure and robust way to run your self-hosted applications, you can be sure that your data is safe and that you can access it without having to worry about your security.

Yeah, no, thanks. That sounds 100% like some snake oil salesman trying to sell me nord vpn or some trash because HaCkeRs.

lol “Selfhosted” my ass - that’s why FOSS is superior regardless of features.

Aegis on mobile and keepassxc on desktop.

It has an O-counter, something I’d not use in an app that hosts my family videos.

TBH I’m migrating manually by synching files. Still wonder if it’s worth the hassle to somehow export/import contacts & calendar instead of reproducing them by hand. I thought about feeding the mariadb the psql dump I used to create for backups but that’s probably more work than doing things by hand.

One reason for me to try docker is “easier” backup. I just throw the whole data-directory of the db container into restic. Restoring the backup would just be starting a container with that saved directory. I hope that way I don’t have to argue with the database about reading a huge sql dump.

Unfortunately the documentation is a bit weird, I think. There’s the official all-in-one container that starts a container that starts more containers but that was a bit too much “magic” for my taste. I used the images and documentation maintained by the community here and ended up with this compose file I can manage in portainer. Runs nextcloud (with apache), mariadb and redis. Also had to add that final bit for the cron job. This way I can point my reverse proxy at the local ip of the nextcloud_apache container and be done with it.

That’s how I ran my nextcloud for about a decade and never had problems. On my new server I’m running it in docker and so far it seems to work ok.

I wondered about that myself these days and decided to give each stack its own db. Makes it easier to throw a stack into the bin without having to manually prune the associated databases. I might end up running a database container anyways for tests and side projects and things like that but service stacks get their own db of their choice.

Looks like the rust-cult is at it again rewriting existing stuff for no gain but pushing rust on others.

While I don’t agree that using something like restic is overkill you are very right that backup process monitoring is very overlooked. And recovering with the backup system of your choice is too.

I let my jenkins run the backup jobs as I have it running anyways for development tasks. When a job fails it notifies me immediately via email and I can also manually check in the web ui how the backup went.

I think they had some form of cloud computing at some point but they now focus on B2 and some backup tools that utilize B2.

Yes it’s their cloud storage.

“bloat” is thrown around so lightly that it loses all meaning.

Except for when it stops working and you find your files on the server are scattered in their proprietary format.