Add PostgreSQL support and pdo_pgsql extension#4
Open
railway-app[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds dual-database support so the app can connect to PostgreSQL in the dev environment (via Railway's DATABASE_URL) while continuing to use SQLite as the default fallback for local development. config.php's getDB() now checks for DATABASE_URL first and constructs a PostgreSQL PDO connection from it; if the variable is absent it falls back to the existing SQLite path. The Dockerfile gains a pdo_pgsql install step so the extension is available at runtime.
Changes
config.phpDockerfileGenerated by Railway