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

jekyll-s3 doesn't make files world readable when using a version greater than 0.0.5 #14

Closed
spilth opened this Issue Dec 27, 2012 · 7 comments

Comments

Projects
None yet
3 participants
@spilth

spilth commented Dec 27, 2012

I tried upgrading to jekyll-s3 versions 2.0.0 to take advantage of the syncing feature for my blog, but after running jekyll-s3 all my URLs return 403 Forbidden.

I used Transmit to inspect the files on Amazon and see that the Read permission is only set to Owner.

When I use 0.0.5, that permission is set to World, making it accessible to all.

Is there a configuration option that I'm missing to set the files to World Readable?

FYI, I also experience this problem with 0.0.6

@matthodan

This comment has been minimized.

Show comment
Hide comment
@matthodan

matthodan Dec 27, 2012

You should look into adding a bucket policy to your S3 bucket.

matthodan commented Dec 27, 2012

You should look into adding a bucket policy to your S3 bucket.

@spilth

This comment has been minimized.

Show comment
Hide comment
@spilth

spilth Dec 27, 2012

Thanks, I was not aware of Bucket Policies. I used the sample "Granting Permission to an Anonymous User" on Example Cases for Amazon S3 Bucket Policies and it sees to be working

I documented what I did here: http://devlog.spilth.org/2012/12/27/devlog/#m23

spilth commented Dec 27, 2012

Thanks, I was not aware of Bucket Policies. I used the sample "Granting Permission to an Anonymous User" on Example Cases for Amazon S3 Bucket Policies and it sees to be working

I documented what I did here: http://devlog.spilth.org/2012/12/27/devlog/#m23

@spilth spilth closed this Dec 27, 2012

@laurilehmijoki

This comment has been minimized.

Show comment
Hide comment
@laurilehmijoki

laurilehmijoki Dec 28, 2012

Owner

README now contains a link to Amazon's official example of setting up an S3 website
(the commit: 314ef7a).

Spilth: the version 0.0.5 used the gem aws-s3 for interacting with the S3 API. In version 0.0.6 I switched it to aws-sdk, which is a gem developed by Amazon. The aws-sdk S3 client does not set any permissions on the uploaded files, whereas the aws-s3 gem might have done otherwise. This probably caused the phenomenon you describe above.

If you find the current setup process too cumbersome, please let me know.

Owner

laurilehmijoki commented Dec 28, 2012

README now contains a link to Amazon's official example of setting up an S3 website
(the commit: 314ef7a).

Spilth: the version 0.0.5 used the gem aws-s3 for interacting with the S3 API. In version 0.0.6 I switched it to aws-sdk, which is a gem developed by Amazon. The aws-sdk S3 client does not set any permissions on the uploaded files, whereas the aws-s3 gem might have done otherwise. This probably caused the phenomenon you describe above.

If you find the current setup process too cumbersome, please let me know.

@spilth

This comment has been minimized.

Show comment
Hide comment
@spilth

spilth Dec 28, 2012

Thanks, Lauri. I think the README addition will be helpful to others.

I was able to solve my problem by using a bucket policy. I think it's a little obtuse to set up but I think that is the fault of Amazon and not jekyll-s3.

If there was a way to programmatically set the Bucket Policy via jekyll-s3 that would certainly be neat.

spilth commented Dec 28, 2012

Thanks, Lauri. I think the README addition will be helpful to others.

I was able to solve my problem by using a bucket policy. I think it's a little obtuse to set up but I think that is the fault of Amazon and not jekyll-s3.

If there was a way to programmatically set the Bucket Policy via jekyll-s3 that would certainly be neat.

@laurilehmijoki

This comment has been minimized.

Show comment
Hide comment
@laurilehmijoki

laurilehmijoki Dec 28, 2012

Owner

Thanks Spilth for your feedback.

Here's an issue on programmatically setting up the bucket as a web site: #12.

Owner

laurilehmijoki commented Dec 28, 2012

Thanks Spilth for your feedback.

Here's an issue on programmatically setting up the bucket as a web site: #12.

@laurilehmijoki

This comment has been minimized.

Show comment
Hide comment
@laurilehmijoki

laurilehmijoki Dec 30, 2012

Owner

Version 2.2.0 can programmatically configure the S3 bucket to function as a website. See README for instructions.

Owner

laurilehmijoki commented Dec 30, 2012

Version 2.2.0 can programmatically configure the S3 bucket to function as a website. See README for instructions.

@spilth

This comment has been minimized.

Show comment
Hide comment
@spilth

spilth Dec 30, 2012

Awesome!

spilth commented Dec 30, 2012

Awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment