urieljareth
e1f3263c9f
Coolify auto-injected env vars from an attached Postgres use DB_DATABASE, but the cotizador code read DB_NAME. Now both are accepted (DB_DATABASE takes priority) across db.ts, seed.ts, and prisma.config.ts so attaching a managed Postgres in Coolify Just Works.
27 lines
1.0 KiB
TypeScript
27 lines
1.0 KiB
TypeScript
import "dotenv/config";
|
|
import { defineConfig } from "prisma/config";
|
|
|
|
// El CLI de Prisma (migrate deploy) necesita una URL. Si DATABASE_URL no está
|
|
// definida (p. ej. despliegue Dockerfile en Coolify), se arma desde las DB_*
|
|
// que ya usan la app y el seed — así ambas vías apuntan a la misma BD.
|
|
function databaseUrl(): string {
|
|
if (process.env["DATABASE_URL"]) return process.env["DATABASE_URL"];
|
|
const host = process.env["DB_HOST"] || "localhost";
|
|
const port = process.env["DB_PORT"] || "5432";
|
|
const user = encodeURIComponent(process.env["DB_USER"] || "postgres");
|
|
const password = encodeURIComponent(process.env["DB_PASSWORD"] || "postgres");
|
|
const name = process.env["DB_DATABASE"] || process.env["DB_NAME"] || "cotizador_e3";
|
|
return `postgresql://${user}:${password}@${host}:${port}/${name}`;
|
|
}
|
|
|
|
export default defineConfig({
|
|
schema: "prisma/schema.prisma",
|
|
migrations: {
|
|
path: "prisma/migrations",
|
|
seed: "npx tsx prisma/seed.ts",
|
|
},
|
|
datasource: {
|
|
url: databaseUrl(),
|
|
},
|
|
});
|