gatekeeper/net
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use default postgres user (always exists) instead of custom user

Browse Source
This commit is contained in:
cawcenter
2025-12-14 09:14:20 -05:00
parent 716ca8a9a9
commit 80008ddcfd
2 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
CREDENTIALS.md
View File

@@ -1,14 +1,14 @@
# Credentials (Using Existing Database)
# Credentials (Using Default Postgres User)
## Directus Admin Login
- **URL**: https://spark.jumpstartscaling.com
- **Email**: somescreenname@gmail.com
- **Password**: Idk@2026lolhappyha232
- **Email**: admin@sparkplatform.com
- **Password**: SecureAdmin2024!
## Database Credentials (Existing)
- **User**: bbdf554
## Database Credentials
- **User**: postgres (default user, always exists)
- **Password**: Idk@2026lolhappyha232
- **Database**: directus
## Note
These credentials match the existing PostgreSQL database volume. The database was already initialized with these credentials from a previous deployment.
Using the default `postgres` user to avoid user existence issues with reused volumes.