Repository navigation
docs: record D4 decision (BYTEA for file storage) - #150
Merged
Merged
Conversation
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 D4 (file storage backend), decided 2 November 2026.
Chose BYTEA over Azure Blob Storage. Reasoning in the file: transactional integrity, air-gap simplicity, operational surface, scale fits.
#68 closed separately with the full investigation and evidence. New issue filed to audit the Terraform-provisioned storage accounts (which no app code uses).
Related: #67 (D3, same air-gap discipline), #60 (offline install).