How do I easily deploy the production assets to Heroku, GitHub pages, or S3? about ember-app-kit

[thomasboyt]

Amazon S3 is mentioned in the docs: https://github.com/stefanpenner/ember-app-kit/wiki/Getting-Started#deploying

Heroku and GitHub pages are tricky because they involve setting up a repo for your production assets. Might be a good idea to at least have some hints on doing that.

[owain]

FYI - Yeoman has some wiki notes on using git subtree with the dist directory to deploy to GitHub Pages - https://github.com/yeoman/yeoman/wiki/Deployment

Possibly related to #27

[mikegrassotti]

@ebryn yeah it's gotta be dead-simple.

It was pretty easy to deploy my fork to gh-pages, here's what worked for me:

grunt build:dist
cd dist
git init
git add .
git commit -m "Site updated"
git remote add origin [email protected]:mikegrassotti/ember-app-kit
git push origin master:refs/heads/gh-pages --force
rm -rf .git
cd ..

This makes the app available at: http://mikegrassotti.github.io/ember-app-kit/

Thinking it might be cool to make this more generic and include as grunt publish or something. Thoughts?

[stefanpenner]

i think the hook should be.

grunt deploy
grunt deploy:staging
grunt deploy:production

EAK can provide the pipeline, maybe not the actual deploy code/config, maybe just instructions. i want to prevent to much of kitchen sink problem. That being said, we do want all of this to be nice and simple.

[ebryn]

I really would like to drive out a solution for Heroku. Right now I'm manually building from EAK and copying over to another repo for deployment to Heroku.

Maybe having a gh-pages-esque branch for Heroku deploys would make the most sense?

[ebryn]

I've got Heroku deploys working with a poorly written shell script, a connect server, and a Procfile: https://gist.github.com/ebryn/1f9989ef472bf751cf66

You can setup the deploys branch by doing:

git checkout --orphan deploys
git rm -rf .

Copy the server.js, Procfile, and npm init && npm install connect --save. Also setup a .gitignore if you'd like.

[gunn]

@ebryn making a heroku buildpack would be the cleanest option and means no need for a separate branch, just deploy with git push heroku. See https://devcenter.heroku.com/articles/buildpacks

Lineman.js takes this approach:
https://github.com/testdouble/heroku-buildpack-lineman

[mikegrassotti]

Great idea, very clean. I'm going to give this a try...

—

Sent from Mailbox for iPhone

On Tue, Sep 10, 2013 at 5:58 PM, Arthur Gunn [email protected]
wrote:

@ebryn making a heroku buildpack would be the cleanest option and means no need for a separate branch, just deploy with git push heroku. See https://devcenter.heroku.com/articles/buildpacks
Lineman.js takes this approach:

https://github.com/testdouble/heroku-buildpack-lineman

Reply to this email directly or view it on GitHub:
#25 (comment)

[alvincrespo]

👍 I did build an elegant solution to this a while back using the Ember Starter Kit and modifying it to fit the Heroku push scenario. I haven't looked into S3, but I can give it a try. @mikegrassotti thanks for the share on that - Ill try it out. @gunn Good share as well.

What section would something like this be in? I'm thinking either in a sub-section of FAQ's or a Deployment page? But I agree with @stefanpenner that we may not want to solve every solution but give techniques that might empower other devs?

[rwjblue]

@alvincrespo - I had a PR a while back that shows how to incorporate an S3 deploy (see #102). I have been meaning to add a section to the gh-pages branch for this, but haven't gotten to it yet...

[stefanpenner]

I believe good advice has been provided. But this is likely out-of-scope of the EAK project itself, at least for now.