damn! git
Am I the only one that finds git confusing? I get it (or git it) mostly, BUT all of the tutorials out there have assumed that you are using git with a remote server.
Personally, I like to run my own local version control system and then backup the repositories. I think that I have **finally** figured out how to do it. A short summary of my process: (you can get a helpful GIT cheat sheet from here so I won’t include the specific git commands)
- Create the Origin repository.
- Create a branch in the Origin directory. I call my ‘working’. You don’t do any development in this directory however. In my mental model this directory and the branch are like a remote server.
- Change to another directory and clone your Origin.
- Use this directory as your active work in progress directory. When you push changes to the origin you will be pushing to the *master branch of Origin.
- Whenever I need to backup my repository I go to the Origin directory, merge all of the changes into the *working branch, and then backup that directory.
Hmm. Rereading this it seems a bit convoluted. But, I am going to try this process for a bit and see how it works. I think that a good versioning plan will be tres helpful as I manage collaborative creative work.
(Edit: I know why I am doing this! Because I am doing web development locally in my htdocs directory. However, this is only one subdirectory in the larger project’s directory. I do backups on the main project’s directory. So…. the webdev folder in my main project directory is my Origin git repository. The directory in htdocs is a clone. I actively develop in the htdocs directory and then push the changes to the main project folder.
All backups happen on the main project folder.)
