There's an awesome free Git book available here: http://git-scm.com/book
It serves as a great beginner to intermediate intro to Git and does an awesome job of demystifying how Git works. In terms of Git workflow processes, a GitHub employee published a blog post about how they do things there. It seems to be one of the more popular workflows. Here's a link to that blog post: http://scottchacon.com/2011/08/31/github-flow.html On Tuesday, December 11, 2012 2:13:12 PM UTC-8, KT wrote: > > Hi all - > > As just an RoR hobbyist, I kinda just make things work as I go. It means > sloppy coding and a host of other bad practice. BUT, I'd like to get your > input on the best way to go for development vs production environments. > > I currently have 2 VMs: "trix" is my production server. I cloned "trix" > as "dukes" to make it my development server. > > I also have a VM, "pongo", as my Git server. I'm having a hard time > "getting" Git, though, and I'm wondering if it's the right way to go. > > I was originally going to develop on dukes, push my changes to pongo, then > pull/merge to trix via git. Is this an ok way of doing things? > > If so, can someone help me with the basics on how to actually DO this? It > doesn't seem like it would be too complicated, but I'm just not > understanding the whole git branch-remote-origin-master-whatever stuff... > thanks in advance. > -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
