fix: default generate to PGlite (no Postgres required) - #58
Open
theatlasteam wants to merge 6 commits into
Open
Conversation
Updated README to clarify that PGlite is used by default for generation, eliminating the need for a PostgreSQL server.
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.
Fixes #2
@algora-pbc /claim #2
Summary
generate()andpgstrap generateto PGlite so generation works without a running PostgreSQL server.--no-pglite/pglite: falsesupport for external PostgreSQL.DATABASE_URL,POSTGRES_URI, andPG_URIin all cases.db:generatefor PGlite and document the default and opt-out behavior.Test plan
pgstrap generate(orbun run db:generateafter init) succeedsbun test tests/generate.defaults.test.tspgstrap generate --no-pglite