

That’s ok Like any landing you can walk away from. Any code that runs to spec is good, much could be better.
That’s ok Like any landing you can walk away from. Any code that runs to spec is good, much could be better.
Yeah, no problem… I started out with just bare rsync - but I did the backup infrequently and needed my notes to know the command. Then I wrote a simple shell script to run the rsync for me. Then I decided I needed more than one backup, redundancy is good. Then I wanted to keep track of the backups so I had it write to .backuplog then that file started getting dated (every time I run a “sun” backup the record of the previous one is useless) so Finally TaDa! loci is born.
It’s also to help me learn python. And it works for me. : ^ )
From the above for those who find it TTDU, This block of addresses is set aside for internally routed nodes inside ISPs.
( *TTDU Too technical didn’t understand )
Thanks! That does look useful! Why does Tailscale use the 100.x.y.z range of IP addresses? Aren’t those also normal routable addresses?
Perhaps I will need to print from time to time, and I may want to access my desktop machine.
If I can use 2FA, especially a time-based one-time password That will be good. I have authy on my phone.
The traveling machine is going to be a Linux machine which will have a strong login password.
So the server as a talescale router set up to only accept a routing connection from my traveling laptop with 2fa. My server’s other services only accepting connections from my network. Do I have the basic concepts correct?
I used chatGPT to work up a backup program that tracked rsync backups as I wanted and could report which backups needed to be run and which ones should be started fresh because too many rsync runs from my home dir to the target dir. It’s call Loci, and it’s on codeberg.