On Thu, Jan 21, 2010 at 8:24 PM, Michael Filbin <[email protected]> wrote: > I have a project that uses a git-centric workflow (courtesy of > Heroku). Typically, I commit changes to my repository which then > triggers a hook to push the newly committed source to Heroku (my > production server). I have RSpec specification files, cucumber user > stories, and other types of supplemental files that really have no > business or value being on the production server, but really need to > be under version control. I would like to have my local repository > acting as the "central" repository containing a version history of all > files. I would then like push the entire project source to a GitHub > repository and then selective files to the Heroku production server.
If you're concerned with the weight of pushing your entire repo to Heroku on deploy, don't be. Git's plenty efficient. If you want to keep things like doco and tests/specs from getting compiled in your Heroku slug (which is not a bad idea), investigate Heroku's new support for .slugignore. ~ j. -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
