vercel
Upgrade TypeScript to 5.5.3
Just adding my thoughts here:
It seems obvious to me that a repository should be 1:1 for an individual/administrator/organization because password sharing is bad.
Obviously, if you're a sysadmin at a company and you've got a team of people, some level of password sharing will be needed. In that case, you'd want to implement something like pass and gpg keys to keep the secret safe.
But it seems to me that the more systems you can back up on a single repository, the more efficient the backups become. For example, if you have a desktop and a laptop, it makes sense, in my mind, to back them both up on one repository because you'll likely have a lot of duplication of files. This will shrink the repository size significantly and speed up backups.
Another case would be, if you're the administrator of a bunch of computers that might not all be "yours" in the sense that you're the primary user. For example, if you have a wife and two kids. You have a laptop and desktop, your wife has a laptop, your kids have a laptop each and they share a desktop to play games on. That makes 5 computers. There would be less file duplication here than in the first case, you can still claw back some disk space by reducing the number of backups you need to keep.
Now for something different. Let's say you're taking sql dumps of postgresql and backing those up for different environments at work? Do you want to back up production data in the same repo as development data? Do you want your development data separated out by the different products or versions? You might consider splitting the data out for security purposes. If a bad actor gets the password for one repository, they don't have access to everything.
This isn't complete, but it should be a good jumping off point for someone. I may come back and finish this off later.
A repo can have multiple passwords (restic key add), so multiple admins can keep their passwords secret from one another. What they implicitly share, though, is the master key for the repo, since that cannot be revoked without re-encrypting everything.
