vvzvlad
ef223e13ff
Set up the project structure per the new-project guide, adapted from the Python skeleton to the Node/TS stack fixed in SPEC.md (reuses docmost-mcp). Scaffold only — the sync engine is not implemented yet. - src/settings.ts: single config layer on zod, schema keyed by real ENV names; credentials and own-service address have no default (fail fast). - src/config-errors.ts: loadSettingsOrExit — clear startup message naming the missing/invalid env var instead of a raw stack trace; exit(1). - src/index.ts: thin entry point that validates config and logs (stub). - test/: vitest unit tests for settings parsing and config errors (10 tests). - Makefile (install/env/build/test/run/dev/clean), strict tsconfig, vitest. - Dockerfile (single-stage, no EXPOSE, prunes dev deps), docker-compose (daemon, volume on /app/data, watchtower), ghcr CI with build needs test. - .env.example, .gitignore/.dockerignore, AGENTS.md, README.md. - Pinned deps (dotenv, zod) + committed package-lock.json.
15 lines
627 B
TypeScript
15 lines
627 B
TypeScript
import { loadSettings } from './settings.js';
|
|
|
|
// Thin entry point. loadSettings() validates the environment and exits with a
|
|
// clear message if anything is missing/invalid. The sync engine is not
|
|
// implemented yet — see SPEC.md for the design and the phased plan.
|
|
function main(): void {
|
|
const settings = loadSettings();
|
|
console.log(`docmost-sync starting (log level: ${settings.logLevel})`);
|
|
console.log(`Docmost: ${settings.docmostApiUrl} (space ${settings.docmostSpaceId})`);
|
|
console.log(`Vault: ${settings.vaultPath}`);
|
|
console.log('Engine not implemented yet — scaffold only. See SPEC.md.');
|
|
}
|
|
|
|
main();
|