Overview

A BrowserCMS module to allow storage of images and files on the Amazon S3 storage facility

Note: This is fork of the original bcms_s3 project. It has been updated to work with BrowserCMS 3.5.0 and will be published as a gem named bcms_aws_s3 (mainly due to gem ownership).

• Allows uploaded files to be stored on Amazon S3.
• Option to change caching to suit heroku and/or use 'www' as the prefix for the non-cms site.

Note that all file uploaded here are publicly accessible on AWS S3, though the paths are pretty hard to guess.

$ gem install bcms_aws_s3

And the following to your gem file

gem "bcms_aws_s3"

Create a config/s3.yml with your credentials (see below). All files uploaded to the CMS will not be pushed and stored on Amazon s3.

Adding this gem to your project will automatically configure the CMS to use AWS for storage. If you want to add the gem, but keep using the existing filesystem, configure the following in your config/application.rb.

config.cms.attachments.storage = :filesystem	# This gems sets this value to :s3 when required.

Create a config/s3.yml file that contains your credentials and bucket. This should be in the following format:

access_key_id: your AWS access key
secret_access_key: your AWS secret access key
bucket: your unique bucket name

Before you can upload files, you will need to create an S3 bucket (one or more) and configure that. You can configure in either:

# config/s3.yml 
bucket: your_project_bucket_name

Which will use the same bucket in development, testing and production. Or in an environment file (if you want buckets for each environment)

# config/environments/production.rb
config.cms.attachments.s3_bucket = "your_project_bucket_production"

# config/environments/development.rb
config.cms.attachments.s3_bucket = "your_project_bucket_development"

1. Final 3.5.0 release
2. Ensure :style param works for S3 (since it does in core now)
3. cname's don't work currently
4. Attachments are public

If using this module in conjunction with deployment on heroku you should probably turning heroku caching on by setting Cms::S3.heroku_caching in config/initializers/browsercms.rb to true.

In order to avoid putting your secret AWS key in the s3.yml file, you can take advantage of heroku's config vars. Use ERB to read the values from the environment. This way you can safely commit your s3.yml file to the repository without revealing your amazon credentials.

access_key_id: <%= ENV['s3_access_key_id'] %>
secret_access_key: <%= ENV['s3_secret_access_key'] %>
bucket: <%= ENV['s3_bucket'] %>

For developing on your local machine, export the s3 variables to your environment.

export s3_access_key_id='your AWS access key'
export s3_secret_access_key='your AWS secret access key'
export s3_bucket='your unique bucket name'

Set the config vars on heroku to get it working there as well.

heroku config:add s3_access_key_id='your AWS access key'
heroku config:add s3_secret_access_key='your AWS secret access key'
heroku config:add s3_bucket='your unique bucket name'

If your non cms domain is www.myapp.com rather than app.com this can be enabled by setting Cms::S3.www_domain_prefix in config/initializers/browsercms.rb to true.

If you've set up CNAMES in your DNS to point to your bucket, then you can enable the use of that instead of the FQDN ending in amazonaws.com by setting Cms::S3.options[:s3_cname] in your s3.yml file.

1. The s3.yml should be excluded from public repositories (e.g github) since it contains your secret AWS key which should never be revealed to the public.
   Please note. This no longer applies since the access keys and buckets are now specified in environmental variables and therefore the s3.yml file now contains just references to these environmental variables.
2. Changing from local storage to S3 storage will require you to re-upload all your files (or copy the tree to s3)

• Original work on S3 storage for BrowserCMS by Neil Middleton
• v2.1 by Anthony Underwood