I'm hoping there is more innovation in this space with React engineers rediscovering the benefits of server-side rendering and Backend-For-Frontend efforts.
I think the perfect stack involves all 3 paradigms (initial loads, hypermedia loads and data/AJAX loads) used in parts of the application as makes sense.
That command works well and accomplishes some of what rincr what built to solve. For example, when I mention browse-ability, I mean on the backup host without any dependencies so I can use standard file tools and browsers.
I also needed both "pull" (backup remote files) and "push" (backup local files) backup features and if I'm not mistaken restic still only supports the "push" model.
If you're doing pull to prevent remotes from destroying old backups (in case of malware takeover, etc), this can be solved by running rest-server with --append-only
> I mean on the backup host without any dependencies so I can use standard file tools and browsers.
This means the backups are not encrypted though, and is something you really have to think twice before requiring
> "pull" (backup remote files)
You can mount the server to backup on the backup host, or you can ssh from the backup host to the server to backup, call `tar cf - /folder`, and ingest that from stdin on the backup host. Both will retransmit the totality of the files to backup
Name it "Funky Jon" to make it more international than Czkawka. Given that it deals with useless, dusty, files, I looked at things related to bureaucracy concepts in Polish. "Funkcjonariusz publiczny" (public official/servant), which in turn can be made into Funky Jon.
"Funky Jon" is a funky public servant/official who dusts off cabinet files, removes clutter, and makes the organization run smoothly.
It's "international" without losing the Polish roots.
A reimplementation of the ideas in rsnapshot built with the composibility and simplicity of rsync in-mind. It comes with sane defaults and I have been using this to compliment my rsync-style mirror backups for data that needs incremenetal backup.
Looking for feedback. I'm gearing up for a stable v1 release.
I'm hoping there is more innovation in this space with React engineers rediscovering the benefits of server-side rendering and Backend-For-Frontend efforts.
I think the perfect stack involves all 3 paradigms (initial loads, hypermedia loads and data/AJAX loads) used in parts of the application as makes sense.