vortiper.blogg.se - Gitx linux

#Gitx linux install#
#Gitx linux mac#

To commit changes I use a simple GUI for OSX called GitX. Commits are sets of changes which I document with a quick message and then push up to the master repository. As I complete major tasks or milestones, I make commits. Once I have the most recent files, I fire up my editor of choice, TextMate, and start my work for the day. This grabs everything new and updates my local repository. I do this with one quick command – git pull. Once that is up and running, I check out all the latest files from our master repository. To get started, I open up Terminal and start my local MySQL database, since the application we're building requires one.

#Gitx linux mac#

I work on a Mac, so this will be Mac specific. It was comforting to know that I couldn't really ruin anything since there was always way to restore it if I happened to make a mistake. After a while I started working directly on the Rails files. At first, I just checked in my markup templates and the developers merged them with their working code. I'm currently using Git to share files with three developers (David, Brian, and Ben) for a Rails application we're building. Here at Viget, designers are responsible for front-end development.

The distributed model means you can work on a project without a network connection (say, on your laptop on a park bench enjoying the sunshine) and synchronize it later.

The files you store are significantly smaller. Since all your operations are performed locally, things like committing changes run extremely fast. Branches will let you test out new things (like a new layout, for instance) without breaking what's already there. I can see myself using branching in the future for implementing big and possibly experimental changes. But from what I hear it's much easier to do in Git, and developers love it. To be honest, I haven't used branching yet. Since each person has a copy of it locally, you never have to worry about a central server crashing and taking all your work with it. This makes most processes super fast, and it also provides built-in backups for your repository. Everyone involved in a project will have their own fully functional Git repository on their machine. Git runs locally and does not require a network connection. The key word here is "distributed." This is one of the things that differentiates Git from other revision control solutions such as SVN. Git is open-source distributed revision controlsoftware Linus Torvalds originally developed to manage Linux kernel development. I started reading up to make sure I had a grasp on what I was doing when I typed commands into Terminal. Once installed, my learning began – and I had a lot of ground to cover. I watched and absorbed as much as I could, but it all looked pretty foreign to me. Then he had to show me how everything worked and wait patiently as I scribbled every single step and command down in my trusty notebook.

#Gitx linux install#

He had to install MacPorts, Git, MySQL, GitX (a handy little GUI), and update my Ruby gems. This was a fairly involved process, partially because my Mac was a little out of date. what kind of learning curve does this thing come with?" I barely knew what I was doing with version control in SVN, and here I was faced with the prospect of a new (and arguably less n00b-friendly) program and process.Ī few weeks later, the project really got rolling, and David was tasked with setting up my machine with all the necessary stuff to allow Git to run on my Mac. I was happily tooling along using Tortoise SVN through VMWare, sloooooI remember sitting in Ben's office thinking, "Crap. Especially when those programs involve heavy use of the command line and every tutorial written about them is so technical it might as well be in another language. Let me start by saying I'm not one of those super tech-minded designers who loves to dive into new programs.