Structure of .aseptic/
.aseptic/ is the folder where a project’s Aseptic configuration lives. It’s split
between what is versioned (of the team) and what stays outside Git (of your
machine).
Versionable (of the project)
Section titled “Versionable (of the project)”| Path | What it is |
|---|---|
scenarios/<name>.yml |
A scenario: its micros, each dependency’s resolution and each micro’s mode. |
micros/ (manifests) |
The startup description of each micro (stack, ports, infra, dependencies). |
mocks/<service>.json |
A service’s mock catalog (endpoints and variants). With hot reload. |
databases.yml |
The database connections catalog. |
Outside Git (of your machine)
Section titled “Outside Git (of your machine)”| Path | What it is |
|---|---|
settings.local.yml |
Local config and credentials (${creds.x}). Absolute paths, secrets. |
.runtime/control.json |
The live engine’s control server (ephemeral port + token). |
.runtime/logs/ |
session.log, errors.log, daemon.log. |
.runtime/entitlements.json |
Snapshot of your capabilities after signing in. |
.runtime/consent.json |
Terms acceptance history (proof of consent). |
.runtime/telemetry.json |
The telemetry state (on/off). |
Why this separation
Section titled “Why this separation”What genuinely belongs to the scenario (micros, mode, resolution) and to the catalog
(manifests, mocks, DBs) is shared via Git. What belongs to the machine (absolute paths,
secrets, ephemeral state) is isolated in settings.local.yml and .runtime/, so that a
shared repo never drags along a secret or a path that only exists on your computer.