Support SQLite #29
Merged
Support SQLite #29
Conversation
This file contains 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.
This PR adds support for using a SQLite database for preview sites instead of Forge-installed MySQL/MariaDB/Postgres.
Adding
DB_CONNECTION=sqliteto theenvironmentinput will now make the action skip creating a database when creating a preview site, and configure the site to use the default SQLite connection details. The database file will be created automatically when migrations are run for the first time (during the first deployment).I think this is a decent workaround for sites that don't need a database at all for now too. All Forge servers have SQLite installed so this will always work, but more importantly they all default to including
artisan migrate --forcein the deployment script, so completely bypassing all database setup is more complicated than just not creating one initially. If a preview site really doesn't need a database to exist at all, the easiest and fastest option is to set it up to use SQLite.Closes #28.