FediScanner

#git

← Back

Windowsのショートカットとシンボリックリンクは、似て見えてもOSからの扱われ方が異なります。
.lnkはWindows Shellがリンク先を開くための通常ファイル。一方、シンボリックリンクはファイルシステム上の再解析ポイントとして扱われ、通常のパスアクセスではリンク先へ解決されます。
そのため、デスクトップから人が開く用途ならショートカット、コマンドやアプリから別名のパスとして扱わせたい場合はシンボリックリンク、という使い分けができます。
mklinkのシンボリックリンク・ジャンクション・ハードリンクの違いや、Git・Java・robocopyでの挙動も整理しています。


chunlog.jp/it-trivia-shortcut-

Show Original PostReport

Github Awesome (@GithubAwesome)

Walgit은 S3 또는 GCS 버킷을 백엔드로 사용하는 단일 바이너리 Git 서버를 소개했다. 별도 데이터베이스나 리더 선출 없이 버킷 자체를 리포지터리로 취급하며, 서버 로컬 디스크는 폐기 가능한 캐시로 사용한다. push는 불변 로그 엔트리로 기록되고 compare-and-swap 매니페스트로 업데이트 충돌을 결정하는 분산 설계다.

x.com/GithubAwesome/status/209

#git #distributedsystems #s3 #gcs #developertools

Show Original PostReport

My notes on Radicle code forge User Guide

I spent some time reading the User Guide and some other docs, instead of going to sleep… here are my main takeaways.

  • It’s like GitHub, but decentralized.
  • It’s P2P, so you run a Radicle node on your laptop (but you have to opt-in to incoming connections)
  • It’s very offline/local workflow friendly
  • https://radicle.garden/ is an optional centralized, always-available node that can mirror/seed/host your code. So basically YOU <-> radicle.garden -> world
  • This is what the web interface looks like: https://radicle.network/nodes/kristoff.radicle.garden/rad:z3WukSjzicL8WaZHFALbBwb2r8W52
  • There is a concept of “seeding”. When a user “seeds” your repo, they add to your repo’s replica count, meaning it’ll have higher availability. It’s kinda like a GitHub “fork”, but the fork becomes a valid location to download your repo from. (Crypto makes it trustworthy.)
  • The point of seeding is to help keep the repo up, whatever the reason may be (outages, censorship, etc).
  • Repos have UUIDs across the network, so you aren’t tied to a specific server or company. If radicle.garden enshitifies and you move, your users keep cloning exactly the same.
  • CLI is written in Rust… single static binary, contains everything you need
  • Your git repo carries code, issues, and pull requests, but not in literal files mixed with your code (right?)
  • You can host on Radicle, but your users don’t have to use Radicle to clone, they can just do a regular git clone
  • Users do have to get on the Radicle network to post issues and pull requests though.
  • Private/invite-only repos supported
  • Release artifacts supported
  • CI supported via web hooks?

Show Original PostReport