twiner VS syncthing-android

You need to ensure that you have write access to the directory in which you clone a repository. I do have access, I could create directories and files, and I even ran an instance of Syncthing, synced a "folder" with another computer running Syncthing. It's just that git was having trouble. Following is what I see on the console: bash-5.1# git clone https://github.com/myTerminal/twiner.git Cloning into 'twiner'... remote: Enumerating objects: 450, done. error: unable to get random bytes for temporary file: No such file or directory error: unable to get random bytes for temporary file: No such file or directory fatal: Unable to create temporary file '/var/twiner/.git/objects/pack/tmp_pack_XXXXXX': No such file or directory remote: Counting objects: 100% (22/22), done. remote: Compressing objects: 100% (18/18), done. fatal: fetch-pack: invalid index-pack output

Getting to know Linux better from my initial days with beginner-friendly distributions to stepping into the manual installation of Arch (pacstrap), Debian (debootstrap), and Void (xbps) has taught me a lot more of Bash than I would have expected from myself. I now also maintain my personalized setup scripts along with my dotfiles. Furthermore, I also created twiner as a re-usable tool (that tries to be a lot of things at the same time), which "sort of" helped me deepen my understanding of Bash a little bit more.

Now that we have a running Linux system, we can bring in my custom setup scripts and set up the rest of the system with a little help from twiner.

I never had a proper introduction to shell scripting before and as far as I remember, my first shell script was indeed the simple packages installation script for my Linux setup. Needless to say, I started improving my setup scripts and soon realized that most of the scripts that I was writing could be re-used. Around the same time, due to my failure of being able to run a regular Linux distribution on my Dell Precision T3600 desktop due to the incompatibility of the super-old hardware with the latest Xserver packages, I literally had to learn setting up a command-line Linux for graphical use. More configuration meant adding more code to my setup scripts, and all this extra code was a perfect candidate for my library of functions for Linux setup and this led me to create twiner.

I've got another one on topic of self-hosted file sharing:

- FileBrowser running in Docker (https://filebrowser.org/features)

- Syncthing running in another container (https://syncthing.net/)

Syncthing keeps the files on your PC, Mac, BSD systems updated, and FileBrowser can point to the share and supply a convenient web UI. It works for me, it's kind of like a local Dropbox-lite.

We use syncthing to share files between our machines. It avoids is having to use dropbox / OneDrive etc. You just choose a folder and it automatically syncs it in the background.

https://syncthing.net/

This very hn entries is bust contradicting your statement.

Also what about syncthing[1] (for recurrent/permanent sync) and croc[2] (for one time copies) ?

I have used both for a number of years already.

[1] https://syncthing.net/

[2] https://github.com/schollz/croc

I would use syncthing, which is open source at https://syncthing.net/.

After minimal setup, it just works(tm).

You have a normal directory in your filesystem, that is synced to the other peers (which you set up in the "minimal setup").

I have been using it for years, and it works well. It has no problems crossing os'es (i.e. windows -> linux, linux -> mac)

For windows I usually recommend https://github.com/canton7/SyncTrayzor, but vanilla syncthing works fine too (but don't try to mix them!)

Do consider Syncthing particularly if you are using Android. If using apple iOS you'd need the möbius sync client.

https://syncthing.net/

https://www.mobiussync.com/

One thing that it beats the cloud / centralized sync on is because the connection is direct between devices when the initial transfer is completed the file is completely there on the other device. With a cloud type of sync you do the transfer twice. I've seen stack up on large media or with the structure of cloud services pricing making it expensive depending on how your workflow is setup with inside and outside parties. For example, Dropbox deduction from all parties' storage limits not just the sharer.

You can also point Syncthing at a local sync of Dropbox or Google drive and then forward the files to other recipients from that for some purposes.

I think sync is a non-feature, as you can just ride on your existing solution.

For example, I use syncthing [1] with Obsidian to sync files off-cloud.

https://syncthing.net/

When I was 14 and just getting started, I used Notepad. Upgraded to Wordpad when I realized I loved putting italics in every other sentence, moved to Google Docs at around 25 when I started writing on my phone and wanted to sync with my computer, finally moved to Obsidian a few months ago (with Syncthing for syncing) when I decided I don't want to live in Google's house where they can burn my stuff down whenever they want.