Fix: Usar host único de Postgres para evitar conflictos en red compartida
All checks were successful
build-and-deploy / build-and-deploy (push) Successful in 1m5s
All checks were successful
build-and-deploy / build-and-deploy (push) Successful in 1m5s
Cambio de 'postgres' a 'lotes-postgres' para evitar errores 28P01 causados por resolución de DNS a instancias incorrectas en la red principal.
This commit is contained in:
@@ -15,7 +15,9 @@ function buildConnectionString(): string {
|
||||
// Fallback para entornos locales si no se pasó NUXT_POSTGRES_URL
|
||||
const user = process.env.POSTGRES_USER || 'seguidor'
|
||||
const password = process.env.POSTGRES_PASSWORD || 'seguidor_password'
|
||||
const host = process.env.POSTGRES_HOST || 'postgres'
|
||||
const defaultHost =
|
||||
process.env.APP_NAME ? `${process.env.APP_NAME}-postgres` : 'postgres'
|
||||
const host = process.env.POSTGRES_HOST || defaultHost
|
||||
const port = process.env.POSTGRES_PORT || '5432'
|
||||
const db = process.env.POSTGRES_DB || 'seguidor_lotes'
|
||||
return `postgres://${user}:${password}@${host}:${port}/${db}`
|
||||
|
||||
Reference in New Issue
Block a user