Adding a lot of untracked files in a Git working copy can be a pain. When I want move control over "git add *" or "git add .", I sometimes run the following and pipe to xargs (and optionally use grep to filter my selection of files). This allows you conditionally add files based on your grep.

For example, if you only wanted to add jpg files..

In this tutorial, I'll show how you can use awk, grep, and sed (my favorite command line tools) to backup and archive your MySQL databases. This can be useful to schedule a cron job, transfer your databases to another server, or any other type of scripting.

First, you'll have to get acquainted with connecting to and dumping your database on the command line. Depending on your user, credentials, and where the databases are located, your command might look something like this. Please note, there is no space between the password and the "-p" flag.

To simplify my example, I'm going to shorten the mysqldump command to the follow.

Now that we're MySQL command line pros, I'll break down each command. I'll start by showing all the databases.

Now, I'll "pipe" the output from the previous command into awk to show the first column data.

And use grep to remove the first line that says "Database".

And use sed to build the mysqldump command. This one is kinda tricky, sorry. As you can see, I also embedded the date command in there to generate today's date in the format: YYYYMMDD.

Lastly, if everything looks good, you can pipe the output back to the command line.

You could even take this one step further and pipe the output through gzip to compress the dumps :)

Here's a quick script to reset ownership on a directory and then commit all changes (deletions, additions, and modifications) to subversion...

I recently had to deploy some new code to an old production environment. Like a good doobie, I made all my changes in a local checked out copy of the subversion file system. I did not want to break the production environment, so I copied the entire vhost into my home directory on the server. I tried to execute an svn update command, but it terminated with the message: object of the same name already exists. This means that a file was creating in my development environment (later revision) that was also created in the production environment. When I ran a svn stat command, there were too many additions, deletions, and modifications, so I decided to write a PHP script to compare the directory structure and files of the 2 environments. I used this script to analyze the file system and create a deployment plan...

Here's a command to add all the new files in your current path to subversion: