From d3d9c7d0e2d9712f28c07a7b21dd8f6570cc878d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Kr=C3=BCger?= Date: Tue, 28 Oct 2025 23:26:12 +0100 Subject: [PATCH] fix: use hardcoded DB credentials for VPS production Changed from ${DB_USER} and ${SEXY_DB_NAME} variables to hardcoded values 'valknar' and 'directus' for production VPS environment. Arty environment variables are not exported to the shell where scripts execute, so the variables were empty when docker exec commands ran. Production VPS always uses: - PostgreSQL container: core_postgres - DB user: valknar - Database name: directus These values are stable for production and won't change. --- arty.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arty.yml b/arty.yml index bf2e983..230339b 100644 --- a/arty.yml +++ b/arty.yml @@ -111,7 +111,7 @@ scripts: sexy/db/import: | echo "⚠️ WARNING: This will replace the current database!" && echo "Make sure core_postgres container is running..." && - docker exec -i core_postgres psql -U ${DB_USER} -d ${SEXY_DB_NAME} < ~/Projects/docker-compose/sexy/directus.sql && + docker exec -i core_postgres psql -U valknar -d directus < ~/Projects/docker-compose/sexy/directus.sql && echo "✓ Database imported from ~/Projects/docker-compose/sexy/directus.sql" && echo "Restarting Directus API..." && docker restart sexy_api && @@ -134,7 +134,7 @@ scripts: sexy/import/all: | echo "⚠️ WARNING: This will completely replace the database and schema!" && echo "Importing database..." && - docker exec -i core_postgres psql -U ${DB_USER} -d ${SEXY_DB_NAME} < ~/Projects/docker-compose/sexy/directus.sql && + docker exec -i core_postgres psql -U valknar -d directus < ~/Projects/docker-compose/sexy/directus.sql && echo "✓ Database imported" && echo "Applying Directus schema..." && docker cp ~/Projects/docker-compose/sexy/schema.yaml sexy_api:/directus/schema.yaml &&