About that I have made the simplest possible implementation of a syslog server in Rust. I use it to collect OpenWrt logs and store them on my server. ;-)
El servidor eslemmy.es lleva ya unos cuantos días caído (al menos una semana). ¿Sabemos si se va a recuperar? Si es necesario puedo echar una mano con el tema a nivel técnico.
restic without any doubt. I use it with S3 backend and SSH copy and it has an excellent performance (with copies of years).
Borg I was using it for a while (to compare) and I do not recommend it, it is not a bad product, but it has a lousy performance compared to restic.
Kopia I didn't know it, but from what I have read about it it seems to be very similar to restic but with some additions to make it pretty (like having ui).
Some people say that Kopia is faster in sending data to the repository (and other people say it's restic), I think that, unless you need ui, I would use restic.
I know this is not the best answer since you would probably like me to talk about Nebula, but I have to say that the best solution I have found for setting up a mesh VPN is Zerotier.
It is a very complete solution. Multisystem, very simple but very configurable, fast, etc.
You simply start by creating a network on the public controller (which will generate an ID for that network) and then join the rest to that network and everyone can communicate with everyone (by default, then you can create subnets if you want).
Using the public controller is completely optional (I personally use it because it is convenient for me and because I have few hosts) but if you want you can set up your own controller, I have an article (the bad thing is that it is in Spanish, but if you run a translator you can understand it perfectly) where I explain how to do it without any requirement. If not, you can use ztncui for it.
Take a look at it, you might find it more attractive than Nebula.
By the way, for me one of the great advantages of ZeroTier is that I don't have to worry about certificates and keys, the controller takes care of everything for you and security is guaranteed from the point of view that each node has a unique identifier.
If you live in Europe you have 1TB by € 3.81 / month with Hetzner. It works fantastic with Restic (I'm using it too for my backups).
I was an Inoreader user too, but I discovered Miniflux and cannot be happier 😉
LessPass has the possibility to connect to a database (via its API) to store the configurations made for each site. This API can be used from any of the clients (either the browser extension, the mobile application, etc.).
You set up the DB server wherever you want. If you want something light you can use this implementation. And if you are interested, there is also a command line client.
In my view, both a password file (vault/database) and LessPass are potentially attackable via brute force. I don't see that one is safer than the other.
Before using borg I would recommend you to take a look at restic. In my opinion it is better in everything than borg.
As for how to backup the database, my advice is to export the database to a SQL file and backup that file. That will always be easier than having to deal with agents that connect to the database.
As for the number of repositories, if you use restic, a single repository is enough. Besides, as restic does deduplication, if you have the same files between your machines, they will only occupy the space of one. ;-)
I hope I have helped you with some of my ideas.
Best regards.
Running any AUR helper (I recommend paru instead of yay but either is a good option) should always be done with a normal user and never with sudo.
This is because both the download of PKGBUILD as well as the download of the sources and the compilation must be done with a normal user. Doing that as root poses a HUGE risk to the integrity of the system, a bad PKGBUILD, a source code with errors, a script with a space where it shouldn't be and you can even break your system completely, you could even execute malicious code!
It is the AUR helpers themselves that will (eventually) ask you for a sudo authentication for when they need to do the final step of installing the package once it has been built.
Montar el servidor es trivial, de hecho tienes hasta una guía en perfecto español que describe paso a paso como hacerlo. Ese no es el problema, el problema donde montarlo. Alojar una instancia de loquesea con un número medianamente alto de usuarios no es barato y depender de donaciones no es factible (a no ser que sea una comunidad consolidada y comprometida que, como es evidente, inicialmente no va a ser así).
A nivel técnico si es necesaria ayuda me presento como tributo 🙃, pero ya digo, es muy importante disponer del sitio para poder hacer un despliegue en condiciones.
Best alternatives:
Self-hosted:
Other alternatives: