Skip to content
This repository was archived by the owner on Mar 22, 2019. It is now read-only.

Configure S3-based deployments via s3cmd#467

Closed
joefiorini wants to merge 1 commit intoemberjs:masterfrom
joefiorini:s3-deploy
Closed

Configure S3-based deployments via s3cmd#467
joefiorini wants to merge 1 commit intoemberjs:masterfrom
joefiorini:s3-deploy

Conversation

@joefiorini
Copy link
Contributor

This completes part of the infrastructure requirements for implementing automated website deployments via travis as discussed in #237.

This PR contains all commands necessary to create the bucket, setup the website configuration, set the bucket policy (ensuring that all files will be world-readable) and perform the first deploy. You can run this via: rake s3:setup. Subsequent deploys can be run vai rake s3:deploy. You will need 3 environment variables set:

  • S3_ACCESS_KEY_ID
  • S3_SECRET_ACCESS_KEY
  • BUCKET_URL

The BUCKET_URL must be in the form of s3://{BUCKET_NAME}.

To run the initial setup commands you must have the latest alpha of s3cmd installed (on a Mac via Homebrew brew install --dev s3cmd). For other platforms, make sure you install at least 1.5.0-alpha3.

To run the deploys via Travis, we should be able to add:

install:
  - sudo apt-get install s3cmd

to our .travis.yml and get access to s3cmd that way.

I tested all of this (minus travis integration) using my own S3 account, you can see the site running at http://emberjs.joefiorini.com/.

@mharris717
Copy link
Contributor

On OSX it's brew install --devel s3cmd, not --dev

@mharris717
Copy link
Contributor

I needed to setup an s3cmd config file with s3 creds before this would work. Is there something about passing them as ENV vals that I'm missing?

@joefiorini
Copy link
Contributor Author

@mharris717 You should be able to just pass them in as env vars. Make sure you're using AWS_ACCESS_KEY and AWS_SECRET_ACCESS_KEY as the variables.

@mharris717
Copy link
Contributor

Ah, your original post had different ENV names.

Thanks!

@joefiorini
Copy link
Contributor Author

Ooops, sorry about that!

On Tue, May 7, 2013 at 9:09 PM, mharris717 notifications@github.com wrote:

Ah, your original post had different ENV names.

Thanks!


Reply to this email directly or view it on GitHubhttps://github.com//pull/467#issuecomment-17580866
.

@mharris717
Copy link
Contributor

FYI it's AWS_ACCESS_KEY_ID not AWS_ACCESS_KEY

I still can't get it it work. It's nbd, right now using a hack where I write the creds to a temp .s3cfg file, then point s3cmd at it. Will just leave that in for now.

Thanks again.

@wagenet
Copy link
Member

wagenet commented Aug 28, 2013

This is inactive and it seems like it may not work. Closing for now.

@wagenet wagenet closed this Aug 28, 2013
@joefiorini
Copy link
Contributor Author

I think this was taken on in @mharris717's PR. If it's actually not
working, I'm happy to take a look at it.

On Wed, Aug 28, 2013 at 1:42 PM, Peter Wagenet notifications@github.comwrote:

This is inactive and it seems like it may not work. Closing for now.


Reply to this email directly or view it on GitHubhttps://github.com//pull/467#issuecomment-23433403
.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants