Repository navigation
docs: record decision to end Lovable platform dependency - #153
Merged
Merged
Conversation
added 2 commits
November 2, 2026 15:51
Closes decision raised in #68. No local/prod split existed; keeping BYTEA across all environments. Full reasoning in DECISIONS/2026-11-02-file-storage-backend.md.
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.
Adds the DECISIONS record for ending Lovable platform dependency, decided 2 November 2026.
Resolves #69. Supabase data (if any) is retired, not migrated. The Lovable workflow for the frontend is ended.
Frontend architecture (what to do with csv-table-hub-main) is a separate decision tracked in #152.
Related: #60 (offline install, reinforced), 4 Oct Lovable adoption (now superseded on platform dependency).