Isn't that creating hardlinks between source and dest? Hard links only work on the same drive. And I'm not sure how that gives you "time travel", as in, browsing snapshots or file states at the different times you ran rsync.
Edit: ah the hard link is between dest and the link-dest argument, makes more sense.
I wouldn't bundle fs and backup compression in the same bucket, because they have vastly different reqs. Backup compression doesn't need to be optimized for fast decompression.
It works fine if all you need is transfer, my issue with it it's just not efficient. If you want a "time travel" feature, your only option is to duplicate data. Differential backups, compression, and encryption for off-site ones is where other tools shine.
ah, it's a massive improvement. Everything is in your project dir, so you can move it around. But uv is the fastest package manager, so reinstalling most things doesn't take time; with the exception of dependencies that need to compile code in different langs.
uv mostly gets rid of the "venv activation" thing (mostly bc you can still use it if you really want, but you don't need to), you can do uv run main.py and it'll just work, no need to even install packages explicitly, it'll also do that for you and make sure your uv.lock is in sync with your environment.
it's the most hassle-free experience I've had with python, by a long shot.
I've written C, JS, PHP, and a few others. Today I write Python almost everyday and wouldn't trade it for any of them. Maybe Rust, but not because of brackets.
It does make it easier to read. We primarily use indentation to match brackets, so clearly, indentation is the most important readability feature between the two, not brackets.
Try reading the same piece of code: without brackets, and then without whitespaces and tell me which is better.
Whitespaces as syntax force you to indent your code properly and not be misleading.
In the Python documentary they mention the early creation of numeric as an alternative for closed options like Matlab; which led to Python being used in the sciences and data processing. Then later it became the natural choice for machine learning in the early 2010s and the AI explosion of 2020+.
I tried portainer for a while, but it was almost useless to me, as I'd always end up in the command line anyway. So I dropped that and any other dashboard idea.
Isn't that creating hardlinks between source and dest? Hard links only work on the same drive. And I'm not sure how that gives you "time travel", as in, browsing snapshots or file states at the different times you ran rsync.
Edit: ah the hard link is between dest and the link-dest argument, makes more sense.
I wouldn't bundle fs and backup compression in the same bucket, because they have vastly different reqs. Backup compression doesn't need to be optimized for fast decompression.