carapace-sh/carapace-bin / skills/lore
lore
FlaggedUse when working with the Epic Games Lore version control system — a centralized VCS designed for game development with binary-first content-addressed storage. Covers architecture, core concepts, server deployment, CLI and server configuration, workflows, and the full command reference. Triggers on: "lore", "Lore", "Epic Games Lore", "loreserver", "version control system", "VCS", "content-addressed", "immutable store", "mutable store", "BLAKE3", "Merkle tree", "FastCDC", "fragment", "partition", "content-defined chunking", "split-write", "shared store", "revision", "branch", "merge", "cherry-pick", "revert", "bisect", "layer", "link", "lock", "staging", "dirty", "obliterate", "packfile", "LoreError", "config.toml", "cli.toml", "lore://", "Lore server", "Lore CLI", "Lore configuration", "Lore FAQ", "Lore roadmap", "Lore system design".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| references/cli.md | markdown | 14.0 KB |
| references/config.md | markdown | 8.1 KB |
| references/core-concepts.md | markdown | 11.5 KB |
| references/faq-roadmap.md | markdown | 5.0 KB |
| references/overview.md | markdown | 5.8 KB |
| references/setup.md | markdown | 3.7 KB |
| references/workflow.md | markdown | 5.9 KB |
references/setup.md
View on GitHub# Setup
Installation, server deployment, certificates, and configuration.
> **Source of truth**: <https://epicgames.github.io/lore/how-to/install-lore-cli/> and <https://epicgames.github.io/lore/how-to/deploy-local-lore-server/>
## Install the Lore CLI
### Prebuilt Binary (Recommended)
```bash
# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash
# Windows (PowerShell)
irm https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.ps1 | iex
```
Open a new terminal session for PATH changes. Verify with `lore --version`.
### Build from Source
```bash
cargo build --release -p lore-client --bin lore
sudo cp target/release/lore /usr/local/bin/lore # or ~/bin/
```
### Shell Completions
```bash
lore completions zsh ~/.zsh/completions
lore completions bash > ~/.local/share/bash-completion/completions/lore
lore completions powershell | Out-String | Invoke-Expression
```
Supported shells: `bash`, `zsh`, `fish`, `powershell`, `elvish`. If you omit the output path, the completion script is printed to stdout.
## Start a Local Server (Demo Mode)
Runs a throwaway server with ephemeral self-signed certificate, temporary store, and no auth.
```bash
# macOS / Linux — install CLI + server + start demo
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash -s -- --demo
# Windows
$env:LORE_DEMO=1; irm https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.ps1 | iex
```
The server listens on ports **41337** (QUIC/UDP + gRPC/TCP) and **41339** (HTTP).
## Deploy a Persistent Server
### From Binary
```bash
# Install the server binary
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash -s -- --server
```
### From Docker
```bash
docker build --platform linux/amd64 -f lore-server/Dockerfile -t lore-server .
docker run -d --name lore-server \
-p 41337:41337/tcp -p 41337:41337/udp -p 41339:41339 \
lore-server
```
> Apple Silicon requires `--platform linux/amd64` — the `linux/arm64` image targets AWS Graviton3 (SVE).
### Ports
| Port | Protocol | Purpose |
|------|----------|---------|
| 41337 | TCP (gRPC) + UDP (QUIC) | Primary server communication |
| 41339 | TCP | HTTP (health checks) |
### Health Check
```bash
curl -i http://127.0.0.1:41339/health_check
# → HTTP/1.1 200 OK
```
### Certificates
Generate a self-signed certificate for persistent deployments:
```bash
openssl req -x509 -newkey rsa:2048 -nodes \
-keyout key.pem -out cert.pem -days 365 \
-subj "/CN=localhost" -addext "subjectAltName=IP:127.0.0.1,DNS:localhost"
```
### Durable Storage
Both stores need a persistent path:
```toml
[immutable_store.local]
path = "/opt/loreserver/store"
flush_delay_seconds = 10
[mutable_store.local]
path = "/opt/loreserver/store"
flush_delay_seconds = 10
```
### Minimal Persistent Config
Place in `local.toml` in the config directory:
```toml
[server.quic.certificate]
cert_file = "/opt/loreserver/certs/cert.pem"
pkey_file = "/opt/loreserver/certs/key.pem"
[immutable_store.local]
path = "/opt/loreserver/store"
flush_delay_seconds = 10
[mutable_store.local]
path = "/opt/loreserver/store"
flush_delay_seconds = 10
```
Start with: `loreserver --config /opt/loreserver/config`
### Docker Persistent Setup
```bash
docker run -d --name lore-server \
-p 41337:41337/tcp -p 41337:41337/udp -p 41339:41339 \
-v "$PWD/cert.pem:/etc/lore/cert.pem:ro" \
-v "$PWD/key.pem:/etc/lore/key.pem:ro" \
-v "$PWD/local.toml:/etc/lore/config/local.toml:ro" \
-v ~/lore-data:/data \
lore-server
```
## Recommended Directory Layout
```
/opt/loreserver/
├── config/
│ └── local.toml
├── certs/
│ ├── cert.pem
│ └── key.pem
└── store/
```Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |