gbpark/invyone
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(docker): point invyone backend at test_dev instead of vexplor_dev

Browse Source 
User confirmed test_dev is the correct database for invyone (the
old TEST-VEX project), matching what the previous mac compose was
using. Same host (211.115.91.141:11134), same credentials, just a
different database name.

Verified end-to-end: real login (POST /api/auth/login from the
browser path) returns 200 with a valid JWT, meaning the full chain
browser → next dev rewrites → backend-spring → HikariCP → test_dev
works and the user table lookup + password check both pass.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
gbpark
2026-04-07 23:45:27 +09:00
parent 276e338b0e
commit 9890b906b9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker/dev/docker-compose.invyone.yml
+2 -2
View File
@@ -28,8 +28,8 @@ services:
environment:
SPRING_PROFILES_ACTIVE: dev
SERVER_PORT: 8081
# vexplor_dev DB (211.115.91.141:11134)
SPRING_DATASOURCE_URL: jdbc:postgresql://211.115.91.141:11134/vexplor_dev
# test_dev DB (211.115.91.141:11134)
SPRING_DATASOURCE_URL: jdbc:postgresql://211.115.91.141:11134/test_dev
SPRING_DATASOURCE_USERNAME: postgres
SPRING_DATASOURCE_PASSWORD: vexplor0909!!
JWT_SECRET: ilshin-plm-super-secret-jwt-key-2024