-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Autoconfiguration for S3 as Primary Storage #1124
Comments
+1 to add the possibility to configure S3 via env variable like this:
|
Would also love to see this feature. |
See also #1134 (with a PR). |
pierreozoux
added a commit
that referenced
this issue
Aug 28, 2020
closes #1193 #1124 #1134 Co-authored-by: Adam Jenkins <[email protected]> Co-authored-by: Stephen Cuppett <[email protected]>
pierreozoux
added a commit
that referenced
this issue
Aug 28, 2020
closes #1193 #1124 #1134 Co-authored-by: Adam Jenkins <[email protected]> Co-authored-by: Stephen Cuppett <[email protected]>
pierreozoux
added a commit
that referenced
this issue
Aug 28, 2020
closes #1193 #1124 #1134 Co-authored-by: Adam Jenkins <[email protected]> Co-authored-by: Stephen Cuppett <[email protected]>
pierreozoux
added a commit
that referenced
this issue
Aug 29, 2020
…1227) * Adds ability to configure S3 object stores via environment variables closes #1193 #1124 #1134 Co-authored-by: Adam Jenkins <[email protected]> Co-authored-by: Stephen Cuppett <[email protected]> * Update .config/s3.config.php Co-authored-by: Adam Jenkins <[email protected]> Co-authored-by: Stephen Cuppett <[email protected]>
Awesome! Great work and thanks for everyone who contributed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if S3 Primary Storage could be auto-configured similar to the database or Redis settings. Changing the primary storage in the config file after the installation step leads to some strange effects and prohibits a "serverless" deployment where there is no persistent file system other than S3. All file system extensions i looked up for docker requires root access in the container which are not given for serverless deployment options such as AWS Fargate
The text was updated successfully, but these errors were encountered: