Local Git Remotes
The article discusses the setup and benefits of using local git remotes. It explains how to create a bare repository on a home server and add it as a remote for pushing and pulling code. The author highlights the advantages of having a local remote for better reliability compared to offsite remotes.
- ▪A bare repository can be created by cloning an existing project directory.
- ▪Local remotes can be added using specific git commands for both local and remote machines.
- ▪The author prefers using a local remote for its reliability over offsite options.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Cblgh |
| Canonical URL | https://cblgh.org/posts/local-git-remotes/ |
| Publication time | Fri, 29 May 2026 12:45:02 +0000 |
| Retrieval time | 2026-05-29T12:50:00.410Z |
| Last seen | 2026-05-29T12:50:00.410Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 6fg3K1xZIWXz |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Local git remotes As part of working on cani I was also using a variety of git remotes. One of the remotes was hosted on a server I have at home. Here’s how I set that up. Let’s say the server has a project in a folder called cani. This folder has the code and a .git/ directory: /home/user/projects/cani We can use the above folder to clone a bare repository (can be used as a remote without causing weird conflicts): cd /home/user/bares git clone --bare /home/user/projects/cani # creates /home/user/bares/cani.git To add this bare repository as a remote to push & pull from can look like a few different ways.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Cblgh.
Discussion
0 commentsMore from Cblgh
