Skip to content

File Layering and VFS ​

racletteJS composes runtime files through a virtual file system overlay.

The .raclette Folder ​

  • .raclette is generated runtime/build output and should not be edited manually.
  • It includes generated compose/docker files, merged service package files, and virtual source trees.
  • It is an implementation detail for development and build pipelines.

Main Parts ​

text
.raclette/
β”œβ”€β”€ virtual/
β”‚   β”œβ”€β”€ backend/
β”‚   └── frontend/
β”œβ”€β”€ backend/
β”‚   β”œβ”€β”€ package.json
β”‚   └── raclette.config.js
β”œβ”€β”€ frontend/
β”‚   β”œβ”€β”€ package.json
β”‚   └── raclette.config.js
β”œβ”€β”€ docker-compose.yml
β”œβ”€β”€ backend.Dockerfile
└── frontend.Dockerfile

Layering Model ​

  • Base layer: core service files from @raclettejs/core.
  • App overlay: optional app files from services/, shared/, and i18n/.
  • Generated layer: generated config and package artifacts.
  • Runtime mounts: plugin folders and selected paths mounted directly into containers.

Important Notes ​

  • Effective container filesystem is VFS + mounts, not only VFS.
  • Additional source mappings can be configured for advanced cases (for example non-src hot-reload needs).