So if you’re moving your production environment, or even just adding another server to your production environment, bash scripts will be of great help to you. The reason for scripting out your deployment is simple: reproducibility. Don’t take chances migrating a live environment manually. Deployment scripts are testable and version-able.

WARNING: This isn’t a tutorial on bash-scripting. I presume you already know at least some of the basics.

The strategy of this script is simple: Setup all of the variables up front, then execute the following:

1. Checkout all code into a holding folder (servername.hold)
2. Switch to the appropriate version of code (git checkout tags/release-0.1)
3. Create any necessary folders that are not versioned (like cache and log folders)
4. Apply any necessary ownership/permissions (apache, 0700)
5. Move the folder from the holding location, to the operating location

The strategy is simple enough in fact, that you could have multiple site deployment scripts that merely setup the variables for use with the same operational script. Anyways, here’s an example of how to get this done.

#!/bin/bash

#move the files from the holding area, to the actual area
echo `mv $HOLD_LOCATION $PROD_LOCATION`


As you can see, everything from the operational section down is basically plug and play. The variables are set, and it’s off to the races. Note that the library repository is just something that’s common for what I typically deal with. That may not apply to your situation. This script shouldn’t serve as the definition of what a production deployment script should be. Rather, this is just an example of one that’s been quite helpful to me.

Regardless, the first thing I always do, is check that the email address is valid. It might sound funny, but just like that hot girl might have given you a phony number, you might have the wrong email address. This happens a lot more often then you might think.

So, how do you check the email? Enter Telnet to the rescue. Don’t worry, Telnet is cross platform. If you have Linux, Mac, or Windows (geez), you can use Telnet to figure out if the e-mail address you’re trying to reach is valid. It’s one of the few things that seem to work on damn near any operating system you can think of.

Sooo go ahead and fire up Terminal (or Command Prompt). Once you’ve gotten that done, you’ll need to type in ‘telnet’. You’ll see a window, something similar to the one below:

Now, you’ll need to get the domain name of the mail server you’re trying to check the email address against. This is not as easy as just checking the domain name itself. Nearly always, the mail server for a domain is mail.domain.com. So, if you’re checking the valid email address for JoeBalls@physics.org, then the mail server is probably mail.physics.org. It’s a much bigger topic than I’ve got to cover here. I’ll get to that later. So let’s just say the right email server is mail.physics.org. 

So, type in ‘open mail.physics.org smtp’ in the command prompt. In case you’re a little confused, it should look like the following:

So, after you enter this, you’ll see the telnet program try to connect to an IP address. If it works, then you’ll get a message about an escape character, as well as the mail server’s welcome message. If you’ve gotten here, then pat yourself on the back. You’ve at least gotten a valid mail server. We’ll assume for now, it’s the right one.

The next thing to do, is type in the following command: ‘HELO mail.example.com’. It’s probably more effective to use a valid mail server for this, but this is supposed to be a simple tutorial. So anyways, after you type in ‘HELO …’, you’ll see something similar to the following:

This is kinda like saying ‘Hi, I’m Cory’. Ehh, don’t worry about it. Now, you’ll have to enter who this test email is from. Usually can use anything that looks like a valid email address. I usually use dude@example.com. So, here it is:

So, the way to check the validity of the email (That’s right, we’re at the climax …. drumroll please ….), is to type ‘RCPT TO:’ and the email address you want to check. I’m using Gmail as a mail proxy these days, so I don’t mind handing out my email address: corycollier@corycollier.com. Go ahead and spam me, I dare you.

Yeah, so go ahead and test that email. So, it looks like ‘RCPT TO: corycollier@corycoller.com’, and a visual representation looks like:

Wait, it didn’t tell me anything??!?

Ahhh, but yes it did. This mail server returned a number, before it returned anything else. That number, is ALWAYS a three digit number. 2xx, 3xx, 4xx, or 5xx. 2xx indicates success. So, the 250 blah blah blah, basically means that the email address is valid. Sorta anti-climatic? Maybe, but what’s the end result? You’ve just made sure that an email address is valid. Give yourself another pat on the back.

So, just in case you were wondering, I wrote this tutorial on Melissa’s MacBook. Thanks honey for volunteering your computer long enough for me to write this. Then again, you’re watching American Idol, so I doubt you need the computer right now. And, since this is a tech tutorial, I doubt you’ve read this far.

Shadow Copy is a snapshot of a drive, at a particular moment in time. It’s comparable to incremental backups, kinda.

While Shadow Copy is not intended to replace regular backups, it’s a very handy tool to quickly find files that users lose all of the time. Note, this is only available on Windows Server machines. Your XP and Vista machines aren’t going to do this.

Heres how to use it:

First, make sure the Shadow Copy service is running in the services mmc. You’re looking for the service called ‘Volume Shadow Copy’. Make sure it’s started, and it’s set to Automatically start. Once you have that covered, you can move on.

On the server you wish to use Shadow Copy on, navigate to ‘My Computer’.

Right Click the Drive (usually ‘C:’) that you want to use Shadow Copy on.

Click Properties

Click the tab ‘Shadow Copies’

Click the enable button if it’s not grayed out. If the button is grayed out, then you’re already running Shadow Copy. We’ll assume you’re not, so at least pretend to click the enable button.

Now, click the ‘Settings’ button. You should see the following dialog box:

This is where you set the maxium size you want your shadow copy database to be. As a general rule of thumb, you should never use less than 10% of what your max storage capacity is.

You can also set how often you make Shadow Copies. Keep in mind that the more often you make a Shadow Copy, the more space you will need. The default settings are twice a day, at 7:00am, and 12:00pm. I’ve never found a reason to change this, but I’m sure some of you out there will find plenty of reasons.

Now that Shadow Copy is setup, it’s time to see it in action. Back in the first dialog box we saw , click the ‘Create Now’ button to manually create your first Shadow Copy. Don’t worry, you won’t have to do this again.

Now here’s the sort of tricky part. In order to access the shadow copies that have been created via file or folder, you have to view the folders via net connection.

You can either type in the UNC name of the server (i.e. \\YOUR-SERVER-NAME) and navigate to the folder or file you want, or you can view them over a mapped network drive

Once you do that, THEN you can right click your file, or folder, click on properties, and then click on the ‘Previous Versions’ tab.

From here, you can view a previous version, copy or restore. Usually, your best bet is to view the files you want to restore first. It doesn’t help anyone to restore old files that were wrong to begin with. Get someone else’s (think management) OK before restoring files.

For a PC, You’ll need to know the name of the server that has the files you’re looking for. If you don’t know the name of the server, the IP address will suffice.

Open ‘My Computer’

You should something similiar to the above picture. The details will differ with your computer. They’ll look quite different if you’re using Vista.

OK, Now click the ‘Tools’ Menu and click ‘Map Network Drive’

Select the drive letter you wish to map, then type 2 backslashes and the folder name in the folder textbox. You should follow that with the path to the folder you want mapped. If you don’t know, you can click the browse button, and locate it.

You should see something like the following by now.

That’s all there is to it. It’s pretty much the same for Vista, though the location of the ‘Map Network Drive’ is more direct. Just look in the toolbar of your explorer.