fix(docker): chemin de la CLI de migration apres aplatissement (#5)
CD — Déploiement / deploy (push) Successful in 18s

Le refactor a range cli.ts dans src/lib, donc tsc produisait
dist/lib/cli.js alors que Compose, le bin du package et la doc lancent
dist/cli.js : MODULE_NOT_FOUND, le service migrate sortait en 1 et l'API
(depends_on migrate) ne demarrait plus.

cli.ts revient a src/cli.ts, aux cotes de index.ts et admin.ts :
dist/cli.js est de nouveau produit. Imports ajustes en ./lib/...

---------

Co-authored-by: xEsiah <[email protected]>
Reviewed-on: #5
Reviewed-by: Esiah <[email protected]>
Co-authored-by: Gitea Actions <-[email protected]>
This commit was merged in pull request #5.
This commit is contained in:
Gitea Actions
2026-10-16 11:21:54 +00:00
committed by Esiah
co-authored by Esiah
parent 9dd1ad72e0
commit 284646562b
@@ -2,10 +2,10 @@
import { pathToFileURL } from "node:url";
import { resolve } from "node:path";
import { ConfigError, loadDbConfig } from "./config.js";
import { Db } from "./db.js";
import { AppError, toSafeError } from "./errors.js";
import { listMigrations, runMigrations } from "./migrate.js";
import { ConfigError, loadDbConfig } from "./lib/config.js";
import { Db } from "./lib/db.js";
import { AppError, toSafeError } from "./lib/errors.js";
import { listMigrations, runMigrations } from "./lib/migrate.js";
/**
* Point d'entree des migrations : `node dist/cli.js --dir <dossier>`.