That's how we do it :) You also get other nice stuff, rss feeds for commits and stuff
On Dec 1, 5:55 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Thanks for the reply. I followed your example but when pushing the > branch to heroku my webapp isn't changed (so far so good) but i do see > the application restarting. This worries me and I still can't push to > heroku during office hours when my client is working on the app. > > So I signed up for github like you said. this is going to be the > central repository where all my and my colleagues commits get pushed > and when I want to deploy on heroku I push to heroku from my local > repository. Does this sound allright to you? > > On 1 dec, 16:56, albemuth <[EMAIL PROTECTED]> wrote: > > > You can also have a development branch and push it to heroku. The app > > in production is tied to the master branch, so commit/push to the dev > > branch and once you're happy, merge with master and push to see it in > > production. > > > Something like this > > > git branch dev > > git checkout dev > > ...make changes... > > git commit -a > > git push origin dev > > > BTW github is giving away a free month for it's paid accounts, highly > > recommend you try it > > >http://github.com/blog/247-cyber-monday-sale > > > On Dec 1, 3:35 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > wrote: > > > > On 1 dec, 01:14, "Josh Coffman" <[EMAIL PROTECTED]> wrote:> I'm also new > > > to git, rails, etc. git is entirely different than > > > > subversion.. > > > > Yes i noticed > > > if you haven't already, read up on distributed source> control. > > > > I have > > > > I've got git installed, and when I commit, it commits to my local> git > > > repository. I think that's how git always works. > > > Agree > > > > You then push changes > > > > to heroku when ready. actually, I'm pushing to unfuddle as my offsite > > > > repo. I haven't yet, but I will later push to Heroku to deploy it. > > > > Yes ok so you have a central repository on another place (unfuddle) > > > than heroku and deploy to heroku from there. > > > > > -j > > > > > Josh | [EMAIL PROTECTED]<[EMAIL > > > > PROTECTED]>|http://computeristsolutions.comhttp://www.linkedin.com/in/joshuacoffman|http://twitter.com/joshcoffman > > > > > On Sun, Nov 30, 2008 at 2:01 PM, [EMAIL PROTECTED] < > > > > > [EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > I'm new to Heroku and just getting used to git and ruby on rails. My > > > > > background is Java EE and subversion. I'm planning to create an > > > > > application for a customer of mine on heroku. it is a little > > > > > administrative application. > > > > > > I noticed that when I am editing code online it shows immediately in > > > > > "production" this is not i want especially not after deploying version > > > > > 1.0 of my app. > > > > > > So i made a working copy on my laptop and edited some sources and > > > > > pushed it back to heroku. Instead of just committing, the database got > > > > > changed and my app got restarted. This was much more than i intended > > > > > to do. I just wanted to commit not deploy my changes. > > > > > > I am used to a very controlled cycle from development to production > > > > > and for now i would like to stick with that what is the preferred way > > > > > of working with heroku? > > > > > > Do I have to create a git repository on a server for my team and push > > > > > to that repository when they want to share code. and when i want to > > > > > deploy i push from that repository to heroku? > > > > > > Thanks anyway, > > > > > > Joris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
