Add CLAUDE.md, collection scaffold, and MemPalace wing
Establish this repo as a collection of independent script folders for the self-hosted environment (odin, an Unraid host). - CLAUDE.md: repo conventions, the odin stack, and MemPalace usage. The infrastructure facts are carried over from the FamilySync project, where they are documented and verified; the mapping of the name "odin" to that host is assumed and flagged for confirmation, along with the SSH/deploy gaps marked "?". - Core rule: each collection is a self-contained top-level folder owning its own docs, config, and dependencies. No shared/ or utils/ at the root — duplication is preferred over coupling so a collection stays independently deletable. - _template/: scaffold making that rule concrete. The bash entrypoint ships strict mode, --dry-run, and a required-env guard (all four paths tested). - mempalace.yaml: wing "odin-scripts", set explicitly because basename auto-detection would produce the colliding wing "scripts". Tracked rather than gitignored so a fresh clone keeps the config; entities.json stays ignored. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
4437ff5e54
commit
c6be0dc9d6
+11
@@ -0,0 +1,11 @@
|
||||
# Secrets — every collection keeps its own .env beside its .env.example
|
||||
.env
|
||||
**/.env
|
||||
!**/.env.example
|
||||
|
||||
# MemPalace per-project files (issue #185).
|
||||
# `mempalace init` ignores both by default. We deliberately track mempalace.yaml —
|
||||
# it is just wing/room config, and losing it on a fresh clone would make mining
|
||||
# fall back to basename auto-detection (wing "scripts", which collides).
|
||||
# entities.json stays ignored: it holds detected people/entities.
|
||||
entities.json
|
||||
Reference in New Issue
Block a user