Local Git Remotes
- zenoprax - 3452 sekunder sedanI was expecting the use of non-SSH git remotes without network access. Any mounted file system can be a valid remote such as a USB drive. I use file-based remote to keep some repos encrypted on S3 using Rclone.
For example, `git remote -v` would show: `secure-s3 /mnt/fuse/rclone/secure-s3/git/$REPO.git`
I think concurrency is a problem with file-based remotes but for one person keeping a desktop and laptop in sync it is much simpler than running a VPS.
- antiframe - 8439 sekunder sedanGitHub has been such a staple of the modern dev that some are now (re)discovering git is distributed.
- nasretdinov - 7059 sekunder sedanYou can also have multiple independent git repos that don't duplicate the full object store, via git clone --reference. It's less relevant in the container era, but otherwise it can save a lot of time and disk space when cloning repos repeatedly
- mystifyingpoi - 7618 sekunder sedanWhat's the purpose of this? I don't get it. Why push at all to "local remote", if you can just keep your changes on a local branch, and push it whenever "remote remote" becomes available again?
- joeyguerra - 2037 sekunder sedanI love reading articles like this. It's kinda of a slap in the face – "hey guys, you know that thing you've been doing for decades, well for decades you've had this ability to do it with your own stuff if you just spend a few human brain tokens on it".
btw, Git also supports the HTTP protocol ...
- whax - 1952 sekunder sedanInteresting that the footer of the page contains the magic string Anthropic provides to trigger model refusal (styled small and clear).
- ucirello - 5762 sekunder sedanThat's what I used to do with git (just recently moved off of SVN) in a shared computer predating github. It works very well!
- cerved - 7361 sekunder sedanyou can also setup a local remote which hardlinks the index so it doesn't occupy more space. Why? Idk. You don't want to share stash, rerere-cache, branches whatever.
Also handy if you're running an agent in a container on the local fs. Set up a local clone, contain the agent to that repo folder and have it hack away on that. Later, you step out of the container and do the syncing. You can't use worktrees in this situations.
Bare repos are also pretty cool. You can clone the git mailing list as a bare repo and search for threads there instead of setting up an mbox (same for the kernel obviously)
- enoint - 6992 sekunder sedanIt’s hard to sincerely bring up things like site-to-site VPN, without condescending.
- thehwang - 5223 sekunder sedan[flagged]
- globular-toast - 7589 sekunder sedanA "local remote" is a contradiction. Unless the remote is on a different disk you are just wasting space. Even then the point of remotes is for sharing, not for backup/redundancy.
Nördnytt! 🤓