Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under git...

bry4n says...

R A I N


What it does?

It can fetch a copy of file, project, application, framework, gem, tarball, zipball via git or downloadable URLs.  Lazy way to get them! It can be pretty handy for your productivity, development, etc ...


How does it handle platforms?

It is using two tools called "git" and "curl". These tools are required to install in order to run RAIN properly.

 

How to install them on Ubuntu? apt-get is installed by default in any debian based distros

sudo apt-get install git-core curl

 

What about OSX? macport is required to install. Grab it at http://www.macports.org/install.php (please follow the macports' instruction how to install it properly)

sudo port install git-core curl

 


How to use it?

 

To display the help screen

rain help


To add application with a source URL (specify the name and actual URL address)

rain add mustache -s git://github.com/defunkt/mustache.git

rain add yard-gem -s http://rubyforge.org/frs/download.php/67247/yard-0.4.0.gem

rain add pystache-tarball -s http://github.com/defunkt/psytache/tarball/master

rain add rails-rf -s http://rubyforge.org/frs/download.php/60599/rails-2.3.3.tgz


You can create a bundle name with multiple names or multiple URLs by seperating them with a comma without space and gap


Examples:

 

To create a bundle name with multiple application names from the list

rain add rails-bundle -s mustache,yard-gem,rails-rf

 

To create a bundle name with multiple URLs

rain add rb-urls -s git://github.com/defunkt/mustache.git,http://rubyforge.org/frs/download.php/67247/yard-0.4.0.gem


Check the list of names and URLs you added

rain list


Screenshot of "rain list"


Install gem

sudo gem install rain


More features, examples, wiki pages can be found at http://wiki.github.com/bry4n/rain/

Gemcutter page: http://bit.ly/rain-gem

Github page: http://bit.ly/rain-git


Rain is an open source. You can fork it and contribute it. Suggestion/Recommendation is acceptable. I might apply your changes/requests. Just let me know.

 

 

 

Filed under: git

glennrob says...

If you are a master of Vim and feel like a sea-change, or if you're just plain scared, you can set up Textmate as your default editor.

Whack this in your .profile (e.g. ~/.bash_profile), re-source it ( source ~/.bash_profile ), and off you go.

Filed under: git

samullen says...

I was having an issue pushing a project out the production this evening. I was tracking files in my git repository that really should have been in my .gitignore file because the application updated them. What happened was that I was not able to push my project live because Git didn't want to allow me to "pull" the files down without a proper merge. 

"Nuts to that", I say. "I'll just add the file to my .gitignore file and be done with it."

That didn't work.

It didn't work because the file was already being tracked. So, turning to the one who knows all, sees all, and reveals all (i.e. Google), I found a link to source.kohlerville.com which provided the answer.

git rm --cached filename

Don't worry, it doesn't delete your file, just the tracking of it. The next step is to add the file or directory to your .gitignore file.

Outstanding.

Filed under: git

glennrob says...

Here's great rails template snippet to set up .gitignore files throughout your whole Rails project.

It ignores unnecessary files in the root .gitignore, plus it ensures no vendor/ directories are checked into git.

 
run "touch tmp/.gitignore log/.gitignore vendor/.gitignore" 
 
run %{find . -type d -empty | grep -v "vendor" | grep -v ".git" | grep -v "tmp" | xargs -I xxx touch xxx/.gitignore} 
 
file '.gitignore', <<-EOS.gsub(/^ /, '') 
.DS_Store 
log/*.log 
tmp/**/* 
config/database.yml 
config/initializers/site_keys.rb 
db/*.sqlite3 
EOS 
 

Filed under: git

hdknr says...

The Big Idea

The Hg-Git plugin can convert commits/changesets losslessly from one system to another, so you can push via a Mercurial repository and another Mercurial client can pull it and their changeset node ids will be identical - Mercurial data does not get lost in translation.

It is intended that Hg users may wish to use this to collaborate even if no Git users are involved in the project, as it may provide some advantages if you're using Bookmarks (it will transfer bookmarks on push, which Mercurial doesn't do).

Filed under: Git

ulfklose says...

Leider haben sowohl Posterous als auch Blogger mich dazu gezwungen, das Dokument nur im PDF-Format anbieten zu können, da sich beide System entweder an der Länge und/oder den Sonderzeichen im Text verschluckt haben.

Fragen und Kommentare bitte trotzdem in die Kommentare.

(download)

Filed under: git

Ted says...

I just read that Posterous will now automatically include any public GitHub Gist URLs as code snippets within a Posterous entry. For example:

This is something that I've been wanting (or, in most cases, needing) for a long time. I'm hoping to get a lot more use out of this blog now that I can post code and cover some of the various topics that I haven't had the opportunity — or patience — to delve into previously.

Filed under: git

jeraimee says...

Just keeping this someplace for myself and figured it was a good way to start testing posterous:

mv .git/objects/pack/pack-<id of the pack> oldpack

git-unpack-objects -r < oldpack

git fsck --full

git gc --aggressive

Filed under: git

bry4n says...

The Glorious Githubbers at Github recently released a polished gem that will transmits data to the Github API using a command line. This gem also shipped friendly push/pull commands to handle your repository easily. It is ridiculously easy!

http://github.com/defunkt/github-gem

Read the README file for documentation.

Filed under: git

samullen says...

For some time, I've been looking for a hosting provider for projects I'm working on. I use the Git SCM for everything that I work on now, and I use GitHub to host any public projects I work on. GitHub provides a great service for the community, but I'm just cheap enough to not want to upgrade to one of their paid plans (Yes, I really am that cheap). Free hosting alternatives include ProjectLocker, unfuddle, and a host of others. I'm sure all of these services are adequate solutions for any project, but to be honest, I'm not only cheap, I'm also incredibly lazy. I don't want to take the time to figure out yet another site, set up my public key, create a new project and then configure it. I want something dead simple.

I originally thought I might just set up Git repositories on a USB drive and back my projects up there, but that solution requires that you always have the drive with you to use it. What I wanted was something like the USB drive in that it was just part of the filesystem, but at the same time could be everywhere I could be. The solution I came up with was to use Dropbox.

Dropbox, in their own words, "...is software that syncs your files online and across your computers."
Put your files into your Dropbox on one computer, and they'll be instantly available on any of your other computers that you've installed Dropbox on (Windows, Mac, and Linux too!) Because a copy of your files are stored on Dropbox's secure servers, you can also access them from any computer or mobile device using the Dropbox website.
I've already been using dropbox for some time, so it was really just a matter of creating a Git remote repository. That's simple:

mkdir ~/Dropbox/projects/new_project
cd ~/Dropbox/projects/new_project
git --bare init

I've got my Git remote repository ready, now I just need to "add" it to my current project and "push" the current project to my new remote repository. Again, simplicity itself:

cd ~/projects/new_project
git remote add origin ~/Dropbox/projects/new_project
git push origin master

The main drawback with this solution is that I now need to have the "Dropbox" application installed on whatever computer I'm working on. This isn't going to be a problem for me, but I can see how it would be a problem for some. Another drawback is the 2-3 GB limitation. Again, it's not a problem for me, but it may be for some.

The big "wins," on the other hand, are: an external private repository for projects; easy project collaborate with others by "sharing" the project folder; and best of all, it's all free until it's outgrown. 

To be honest, I'm pretty sure I'm not sharing any sort of huge revelation; this post was a really just an excuse for me to try to get more storage on my Dropbox account. You see, you start out with 2GB for free and you get another 250MB with every referral up to 3GB. So how about clicking on this link and getting me to my goal? I'm not only cheap and lazy, I also have no shame.

Filed under: git