Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.Start your free trial
bill burles3,788 Points
pursuade me to use git
do people on their own use git or is it just really useful for collaborating with other people?
At the moment I do websites on my own and just use dropbox to store files. Had a quick peep at git and it looks bit complex for no return?
Am I missing something - bar enhancing skills and cv should I be using it day to day?
I'm the only person who will ever work on my own website and it's great to know that I can edit and lose track of all the files I change. Then with beanstalk I can just commit + push and it will deploy all those files to my server. I also have caching setup and have a deployment hook to make sure that's cleared on every push.
Using git with deployments takes so much hassle out of that whole process. It's nice to never have to touch ftp.
Randy HoytTreehouse Guest Teacher
Having a record of all your history and comments is great. Deployment is great. All professional software developers use source control for every project: it's just so clearly the right way to do it.
It's really hard to convince someone about the benefits of source control who hasn't experienced them. So let me tell you my own journey to source control. Like you, I worked on my own files for a long time: I would edit them directly on my server, and I would keep backups off the server.
Then one day I wanted to contribute some code to a WordPress plugin on GitHub. I emailed the owner my changes, and he told me just to do a pull request on GitHub. It took a bit of time to figure it all out, but I eventually did. I submitted the pull request for the code, and it was included.
Then I started a couple of collaborative projects, and I had to figure out even more of Git to set those up. It was complex and a little painful, yes, but it was worth it.
Now, when I start a personal project, I wouldn't even consider not using Git. No one persuaded me to do it: instead, I used it first for a collaborative project and now wouldn't even think of not using it. The first thing I do is create an empty Git repository and pull it down to my development environment. No questions. No deliberating. I just do it. Whatever else I'll need to do with the code base -- deploy to a production server, invite a collaborator, whatever -- I know I can do because I have a Git repository for it.
@Steve, +1 for no more FTP!
James Barnett39,199 Points
Tommy MorganTreehouse Guest Teacher
Mercurial is easier to use, but its simplicity comes at a cost :) For everything that Mercurial does more easily than git, there's a potential issue that could bite you once you start doing more complicated interactions (which inevitably happen if you're working in a team).