Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: don't require the S3_SERVICE variable and set default appropriately, fix readme formatting #248

Merged
merged 1 commit into from
May 8, 2024

Conversation

4141done
Copy link
Collaborator

@4141done 4141done commented May 8, 2024

Proposed changes

Fixes issue where the S3_SERVICE variable should be optional but was being enforced as required.
I have tested this with and without the env var specified and against both traditional and "directory" style s3 buckets.

Checklist

Before creating a PR, run through this checklist and mark each as complete:

fixes #247

@4141done 4141done changed the title bugfix: don't require the S3_SERVICE variable and set default appropr… bugfix: don't require the S3_SERVICE variable and set default appropriately, fix readme formatting May 8, 2024
@alessfg alessfg added the bug Something isn't working label May 8, 2024
@alessfg alessfg linked an issue May 8, 2024 that may be closed by this pull request
@alessfg alessfg changed the title bugfix: don't require the S3_SERVICE variable and set default appropriately, fix readme formatting fix: don't require the S3_SERVICE variable and set default appropriately, fix readme formatting May 8, 2024
@4141done 4141done merged commit e83a94f into main May 8, 2024
9 checks passed
@4141done 4141done deleted the issue-247 branch May 8, 2024 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Container start fails because of missing S3_SERVICE variable
2 participants