search

ga-wdi-boston / ember-deployment-guide

Other
4 stars 19 forks source link

What to do after the initial deployment #16

Closed laurpaik-zz closed 7 years ago

laurpaik-zz commented 7 years ago

When we update our app, should we be rebasing gh-pages off of master every time we deploy?

raq929 commented 7 years ago

If it were me, I would delete the branch and go through the steps again. I don't think rebasing will get you the result you want.

laurpaik-zz commented 7 years ago

Okay, good to know. Bernard and I ended up deleting the gh-pages branch on Friday and went through it again, but I wasn't sure if that was a hack-ey solution or not

payne-chris-r commented 7 years ago

Yeah gh-pages is gross. I go with the nuke_pave approach as well...

jrhorn424 commented 7 years ago

Please don't backtick "nuke & pave". It makes it sound like a task that ships with the Ember template.

zchenbonterra commented 7 years ago

Lauren told me about this. SO basically, I did not delete the gh-pages branch and it is working for me. Here are the steps that I did. Please let me know if I am wrong and if I should delete gh-pages every time since I follow the guide.

  1. Checkout to gh-pages
  2. git merge master
  3. add # to /dist inside .gitignore if needed***
  4. git add and commit
  5. ember build --environment=production
  6. git add and commit
  7. git subtree push --prefix dist origin gh-pages
  8. checkout to master