79c3769542
- demo/files/<Folder>/<file> becomes the cloud's content for every visitor (read-only; "private login" = git/repo access). Text inlined, binaries streamed from disk; empty folder falls back to the built-in seeded set. - Dockerfile.backend now copies docker/bitcoin-ui and demo/files into the image (they live outside neode-ui/) — this also fixes the Bitcoin UI mock, which the backend reads from /docker/bitcoin-ui and was previously absent in the container. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
23 lines
848 B
Markdown
23 lines
848 B
Markdown
# Curated demo files
|
|
|
|
Drop real files into `demo/files/` to make them the cloud's content for **every**
|
|
demo visitor (read-only — visitors can browse, download, and "buy" them, but only
|
|
maintainers add them). This is the "private login": the only way to add files is
|
|
to commit them here, which requires repo access.
|
|
|
|
```
|
|
demo/files/
|
|
Documents/whitepaper.pdf
|
|
Photos/rig.jpg
|
|
Music/track.mp3
|
|
```
|
|
|
|
- Folder structure becomes the cloud's folders.
|
|
- Text files (`.md .txt .json .csv …`, < 1 MB) are inlined; everything else is
|
|
streamed from disk on download.
|
|
- If `demo/files/` is empty, the demo falls back to the built-in seeded set
|
|
(Documents/Photos/Music/Videos with sample content).
|
|
|
|
After adding files, commit and push — CI rebuilds the `:demo` image and Portainer
|
|
redeploys. Keep the total modest (these load into the demo image).
|