Feat db baserow #27
Merged
Feat db baserow #27
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
A Baserow instances requires the following tables:
Screenshot:
Here are links to the demo tables:
|
|
See #26 |
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 adds the option for a Baserow backend and keeps the file local storage db, as a JSON file (rather than a JS file, which will make for easier edits through an eventual CMS like Frontaid).
New
.envfor environment variables, which should all be set in production (even when empty). For instance, theDB_TYPEis mandatory for specifying the backend configuration (file,baserow).The PR contains a small refactor, which simplifies the codebase a lot and removes unnecessary sveltekit routes (
[eventId]-html,config, etc.). It also documents many variables within the code and improves readibility.The PR also includes a couple of fixes and improvements.
Most of the app remains backward-compatible, except for the
db.js=>db.json.