-
Notifications
You must be signed in to change notification settings - Fork 112
Add S3 Storage Backend #1236
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
Add S3 Storage Backend #1236
Conversation
|
||
Akeeba Amazon S3 Connector version 2 has dropped support for PPH 5.3 to 7.0 inclusive. It is only compatible with PHP 7.1 or later, up to and including PHP 8.0. | ||
|
||
The most significant change in this version is that all methods use scalar type hints for parameters and return values. This _may_ break existing consumers which relied on implicit type conversion e.g. passing strings containing integer values instead of _actual_ integer values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good news for these consumers, scalar type hints also do implicit conversion from strings to integers!
// Protection against direct access | ||
defined('AKEEBAENGINE') or die(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh? What's the point of this in all the files?
I'll check this out with my test node mordor.social and a Minio server. Thank you! |
I think you have to use v2/legacy flag, afaik |
} else { | ||
if (empty($this->getRegion())) { | ||
$this->setRegion('us-east-1'); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not
} elseif (empty($this->getRegion())) {
$this->setRegion('us-east-1');
}
It's working :-)
I needed to fix the akeeba library as well (will create a PR for them), but at least I didn't have to include the official AWS library, which contains more than 8.300 files! I thought that would be insane for our specific use case.
I tested the S3 Backend with a Amazon S3 bucket and it worked well
I'd say it's ready :-)
btw. the tests will get fixed after #1238