Add MinIO self-hosted screenshot storage #1372
Draft
Conversation
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
Implements self-hosted screenshot storage using MinIO: - Added MinIO service for handling file uploads - Updated screenshot upload logic to support both MinIO and Supabase - Added MinIO container to docker-compose.yaml - Added documentation for self-hosted storage TODO: - Update self-host fire-engine to allow screenshot function
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.
Description
This PR adds support for self-hosted screenshot storage using MinIO, allowing users to store screenshots locally without requiring Supabase.
Changes
Related Issue
Fixes: #1028
Testing
Outstanding
Updates to the core fire-engine/playwright are still needed to allow the screenshot function to work in a self-host instance.
Draft PR Request