Setting up your own remote Git repository
An alternative to using GitHub is to set up your own remote Git repositories:Setting up a new remote git repository
Setting up a new Rails app with Git
Labels: git, version control
Posted at 6:43 PM | 0 comments read on
Capistrano + Git deployment and version control screencast
Good screencast on deploying a Ruby on Rails site using Capistrano and Github (Git for version control). Part of the Learning Rails series.Labels: capistrano, git, version control
Posted at 6:40 PM | 0 comments read on
Version control with Git and Github screencast
Fantastic screeencast for version control using Git and Github. The tutorial is part of a Learning Rails series but this episode is general Git and Github information.Highly recommended!
Labels: git, version control
Posted at 6:38 PM | 0 comments read on
Setting up a remote git repository
Several tutorials on the subject:Version control with Git: remote repositories
Git - setting up a remote repository and doing an initial ‘push’
Git: Easy way to setup a private remote repository
Initialize a remote git repository
Setting up a new remote git repository
Labels: git, version control
Posted at 7:37 PM | 0 comments read on
Django deployment using Git and Fabric
Good articles by Will Larson on deploying Django apps using Git and Fabric:Deploying Django with Fabric
Installing a Development Deployment of LifeFlow, a Django Blog Solution
Posted at 6:33 PM | 1 comments read on
Version control live websites using Git
Articles about using Git for deployment and versioning of live web sites:Using Git to Maintain Your Website
Using Git to manage a web site
A web-focused Git workflow
And specifically for Django:
Development to Deployment in Django
A Tale of Three Repositories
The foundation of my development-deployment pipeline is three repositories (it's a bit simpler using distributed version control, but you could accomplish more or less the same with Subversion or CVS).
A master repository hosted in a non-local and non-production location. I use my Slicehost slice that hosts my blog for all my private git repositories (it has daily and weekly backups, and if it does lag or crash, I can fix it myself), but you could use a paid GitHub account or one of the other similar services.
A local repository for each developer, which they push out to the master server at regular intervals.
A production repository on each production machine serving the project.
Developers do most of their work on their local machines, and push it to an appropriate branch on the master repository. They also pull from the master server occasionally to keep the repositories synchronized.
The production repositories are kept up to date by either:
Using Fabric to command them to pull the newest changes. This is the best option for large, medium and small deployments. That is, this is always the best option. Don't bother reading the others.
SSHing into the production servers and manually pulling the change set. Alternatively you could write a batch script that does this. This approach is more than sufficient for one machine deployment, but for anything more complex than that you'll want to use a deployment solution.
Setup a cronjob that pulls the changes periodically. This is the simplest and laziest of the approaches, but is a bad idea in most circumstances.
That's a good article.
Labels: django, git, version control
Posted at 6:28 PM | 0 comments read on
How to tell git to ignore files
You can put shell-style globs (e.g. *.o) in either .git/info/exclude or .gitignore.
.git/info/exclude is local to your repository only, and not shared by others who might fetch from your repository.
.gitignore is more commonly used, as it can be checked into the repository and thereby automatically shared with all users of the project.
From the gitfaq.
What is this about?
$ git ls-files -o --exclude-standard >> .gitignore
$ $EDITOR .gitignore
By the way here here's a screencast for how to set up Git for use on Ruby on Rails projects.
Labels: git, version control
Posted at 9:37 PM | 1 comments read on