📦 Asset Pipeline

Rotkeeper’s asset pipeline governs how static files are copied, versioned, and injected into the tomb environment. It also defines how asset-meta tags are tracked and maintained throughout the build cycle.

📁 Asset Sources

Assets are typically sourced from:

home/assets/
home/themes/
home/icons/

These folders are expected to exist prior to running rc-assets.sh and are recursively scanned.

🔃 Copy Mechanisms

The primary tool for copying assets is rc-assets.sh (formerly ASSETELLA). It handles:

• Recursively copying from declared source folders
• Maintaining folder structure
• Logging each copied file into bones/manifest.txt
• Ensuring injected assets are recorded with asset-meta

You can run it standalone or via the main CLI:

./rotkeeper assets

Or directly:

./scripts/rc-assets.sh

📑 asset-meta Headers

Every tracked script, template, or asset should include an asset-meta: header — either as shell comment, HTML comment, or YAML frontmatter. These tags are required for changelog visibility and audit inclusion:

# --- asset-meta ---
# file: scripts/rc-render.sh
# version: 0.1.2
# tomb-version: 0.1.7.5
# tracked: true
# injected: 2025-05-12
# --- end-meta ---

These tags allow rc-scan.sh and rc-bless.sh to:

• Detect stale, duplicated, or unversioned assets
• Validate integrity during packing
• Confirm changelog eligibility

📂 Folders Typically Managed

⚠️ Notes on Pipeline Behavior

• The pipeline does not deduplicate—it’s your job to manage redundant files
• Files without asset-meta may be ignored by rc-bless.sh
• If a file is missing from bones/manifest.txt, it won’t be packed
• Use rc-scan.sh to validate what’s missing or untracked

🧪 Example Flow

./rotkeeper init         # creates structure
./rotkeeper assets       # injects static files
./rotkeeper render       # builds output
./rotkeeper pack         # archives everything in manifest.txt

Continue to Template Library Back to Configuration Reference