Mirror
/
seaweedfs
mirror of https://github.com/seaweedfs/seaweedfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13069 Commits
120 Branches
330 Tags
365 MiB
 
 
 
 
 
 
Tree: c89709e47e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c89709e47e'
${ noResults }
seaweedfs/sw-block
pingqiu c89709e47e
feat: add WAL history model and recoverability proof (Phase 04 P3) 		2 days ago
..
.gocache_v2 feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago
.private feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago
design feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago
private feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago
prototype feat: add WAL history model and recoverability proof (Phase 04 P3) 2 days ago
test feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago
README.md feat: add V2 protocol simulator and enginev2 sender/session prototype 2 days ago

README.md

sw-block

Private WAL V2 and standalone block-service workspace.

Purpose:

  • keep WAL V2 design/prototype work isolated from WAL V1 production code in weed/storage/blockvol
  • allow private design notes and experiments to evolve without polluting V1 delivery paths
  • keep the future standalone sw-block product structure clean enough to split into a separate repo later if needed

Suggested layout:

  • design/: shared V2 design docs
  • prototype/: code prototypes and experiments
  • .private/: private notes, phase development, roadmap, and non-public working material

Repository direction:

  • current state: sw-block/ is an isolated workspace inside seaweedfs
  • likely future state: sw-block becomes a standalone sibling repo/product
  • design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths