-
Notifications
You must be signed in to change notification settings - Fork 5
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
Allow for alternate S3 backends #4
Comments
Cool idea! On Wed, Aug 5, 2015 at 2:14 PM, Jonathan LaCour [email protected]
Ben Werdmuller +1 (312) 488-9373 |
I'm not a PHP programmer, unfortunately (at least, its been years since I've touched PHP), so I would struggle to get this done myself. That said, I was able to play around a little bit, and at least get uploading working. You can provide a $aws = \Aws\Common\Aws::factory(array(
'key' => \Idno\Core\site()->config()->aws_key,
'secret' => \Idno\Core\site()->config()->aws_secret,
'base_url' => 'http://objects.dreamhost.com',
)); Once you do this, uploading to DreamObjects works, but it doesn't appear to actually properly load the uploads. Probably just need a few more tweaks elsewhere. Ideally, I'd like to be able to provide Continuing to enjoy Known. Thanks for your hard work! |
The latest commit allows you to include the following two optional settings in your config.ini:
Additionally, you can use the following setting to set a CloudFront-style base URL:
You're making me aware that all of the terminology here is service-specific and doesn't have to be. We should consider changing the options and terminology to be service-agnostic. |
Cool. Testing now... I'll report back :) Let me know if y'all need a free account with DreamObjects. Happy to provide one for testing purposes! |
Doesn't appear to work, yet. The content is uploaded to DreamObjects successfully, but it looks like the S3 filesystem layer is having trouble reading the content back down again, for some reason. Not sure if its properly using the base URL. I haven't enabled the cloudfront stuff yet. |
I wonder if it's a file permissions issue? I would very much appreciate a testing DreamObjects testing account if you're in the position to give one! That would allow us to test more directly. |
Go ahead and signup for the free trial - https://www.dreamhost.com/cloud/storage/ - and then ping me at jonathan at dreamhost via email, and I'll mark it as free. |
I'm fairly certain this now works. I'll spin up a copy against minio in docker this weekend to confirm https://github.com/idno/amazon-s3/pull/8/files#diff-576b8cc9365c70c29fd239c0595ab95eR24-R35 |
It'd be great if an alternate endpoint could be specified in the configuration for those of us who are using S3-compatible services (like internal S3/Ceph deployments or DreamHost's DreamObjects).
The text was updated successfully, but these errors were encountered: