which is weird because they are not any good either
HelloRoot
Already selfhosting it. Thank you so much for your time and effort <3
afaik you just listed features that the printer I mentioned (or if I am wrong, other similar printers) supports
it's my bad for not mentioning all possible workflows, I was just a bit lazy and thinking of my personal documents only, which do not work well with further smart automation, because my batches are highly irregular. So the more manual approach is the best for me currently. Maybe possible with some future AI integration.
please elaborate
Epson WorkForce DS‑730N
put 100 sheets on the tray, it scans them all and either puts them all into a single pdf or multiple pdfs. Then you split / merge them in software.
You could buy an automatic scanner that takes a stack of docs and dumps the files to a network share.
afaik I'm on an older version of https://github.com/distribution/distribution/pkgs/container/distribution
my compose somehow doesn't have much info ... i should have made more notes
image: registry:2
i selfhost a pullthrough docker repository, so every container I use is stored in there and can be pulled offline.
a budget oriented one
I backup the whole / with borg
It has insane deduplication and compression and it creates a structure kind of like git, so you can have lots of incrimental versions without using much space.
It does sound like one, but it isn't. Ignoring the differences in UX:
Passkey
- Per-service key pair, unique per domain, Identity bound only to that specific account on that site
- Challengeresponse via WebAuthn
- Trust anchored only in the target service (no external CA)
- Private key sealed in OS / secure hardware keystore
Certificate login
- Single global identity usable across many services
- TLS client authentication with certificates
- Trust established via certificate authorities and chain validation
- Private key stored in exportable file or smartcard
I recommend managing it through Dokploy.
And put crowdsec in front of it to block attacks.