LB7666/my_lancedb_data

Static Flow LanceDB Data Repository

This repository stores the runtime data for the Static Flow website project. It contains content and metadata only, not application source code.

The corresponding public website is:

• —https://acking-you.github.io/

Purpose

• —Keep all website data in a versioned repository.
• —Store data in Lance/LanceDB table format for local-first workflows.
• —Support backup, rollback, and reproducible deployments.

What This Data Represents

The data is the canonical content layer used by the static-flow project, including:

• —Blog/article records.
• —Image binaries and image metadata.
• —Taxonomy metadata such as tags and categories.

Storage Format

Data is stored as LanceDB table directories (Lance format files):

• —articles.lance/
• —images.lance/
• —taxonomies.lance/

Inside each table directory, files such as *.lance, *.txn, and *.manifest plus index sidecar files (for example *.idx) are managed by LanceDB internals.

Notes

• —This repo is for data management and synchronization.
• —The Static Flow application code lives in a separate repository/workspace.
• —Prefer updating data through sf-cli or backend write paths to keep schema and indexes consistent.

Dataset Management in Static Flow

This dataset is maintained as the production content store for Static Flow. The recommended data lifecycle is:

1. 1.Ingest/update content through sf-cli write commands:
2. 2.write-article
3. 3.write-images
4. 4.sync-notes
5. 5.Keep search/index coverage up to date:
6. 6.sf-cli db --db-path <path> ensure-indexes
7. 7.sf-cli db --db-path <path> optimize articles
8. 8.sf-cli db --db-path <path> optimize images
9. 9.Reclaim stale/orphaned files when needed:
10. 10.sf-cli db --db-path <path> cleanup-orphans [--table <table>]
11. 11.Snapshot data changes into this repository with Git commits.

This keeps LanceDB table state, website data, and recoverable history aligned.

Hugging Face + Git Xet Setup (SSH)

The following commands configure this directory to sync with:

• —git@hf.co:datasets/LB7666/my_lancedb_data

1) Install and enable Git Xet

cd /mnt/e/static-flow-data/lancedb
bash <(curl -fsSL https://raw.githubusercontent.com/huggingface/xet-core/main/git_xet/install.sh)
export PATH="$HOME/.local/bin:$PATH"
git xet install
git xet --version

2) Configure SSH access for Hugging Face

ls ~/.ssh/id_ed25519.pub || ssh-keygen -t ed25519 -C "LB7666@hf"
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519
cat ~/.ssh/id_ed25519.pub

Add the printed public key at:

• —<https://huggingface.co/settings/keys>

Then trust the host key:

mkdir -p ~/.ssh
ssh-keyscan -H hf.co >> ~/.ssh/known_hosts
chmod 600 ~/.ssh/known_hosts
ssh -T git@hf.co

3) Initialize/bind repository remote

cd /mnt/e/static-flow-data/lancedb
git init -b main
git remote remove origin 2>/dev/null || true
git remote add origin git@hf.co:datasets/LB7666/my_lancedb_data
git fetch origin main
git checkout -B main origin/main

4) Track LanceDB files with Xet

cd /mnt/e/static-flow-data/lancedb
git xet track "*.lance"
git xet track "*.txn"
git xet track "*.manifest"
git xet track "*.idx"

5) Commit and push snapshots

cd /mnt/e/static-flow-data/lancedb
git add -A
git commit -m "data: sync lancedb snapshot $(date '+%F %T')" || echo "no changes"
git push origin main

Daily Sync Shortcut

cd /mnt/e/static-flow-data/lancedb
git add -A
git commit -m "data: sync $(date '+%F %T')" || echo "no changes"
git push origin main

Xet vs LFS Attribute Note

After git xet track, .gitattributes may still show filter=lfs lines. This is expected on Hugging Face because Git Xet integrates through an LFS-compatible transfer path, while still using Xet-backed storage semantics.