EditPad delivers everything you need to accomplish tasks in a timely, efficient manner. One of the problems I had using multiple operating systems is transferring and editing files without corrupting them because of the differences in how Windows and Linux handle carriage returns.

For example, imagine you have an Apache web server with various shell scripts you want to execute. If you need to edit those scripts and–for whatever reason–only have access to Windows, just use Notepad and you’re good to go, right? Save your changes and upload the file again. Wrong! Opening the file in most Windows text editors will show a jumble of smashed together text. Instead of having separate lines of code, it will essentially be one continuous line of text with no breaks. Take a look:

Whoops! Looks like you’re going to have the loathed HTTP Error 500 Internal Service screen if you’re modifying your .htaccess file. We all know how picky Apache can be if you make a mistake in spacing, etc. Plus, there is the remote chance some garbled line may actually be executed and do … god only knows what!

Normally, you can get around this problem with text documents by using DOS2UNIX or UNIX2DOS. These programs, available for *nix systems and Windows, convert text documents to their appropriate formatting. While this is an effective solution, why not have the ability to simply save the document into *nix format natively in a text editor? This is one feature where EditPad really shines. Not only can you convert files to *nix format using the Convert > To UNIX (LF Only) menu option, but it will also convert to Windows and Macintosh formats. In fact, if you simply paste the smashed together text into EditPad from a lesser text editor, it will fix it for you–on the fly!

In addition to supporting multiple file formats, the paid version of EditPad, EditPad Pro, supports syntax for HTML, XML, CSS, Delphi, Java, C#, C++, VB, Perl, PHP, Python, Ruby, Eiffel and even SQL! Ah, a programmers dream. Take a look at how it neatly colors functions and keywords:

PHP Syntax Coloring

SQL Syntax Coloring

While the syntax coloring options shown (which are fully customizable) only come with EditPad Pro, which costs $49.95, EditPad Lite comes with many of the features the average user would need to edit documents:

1. Open as many files in EditPad at a time as you want.
2. Change between the open files by clicking on their tabs. No hassle with heaps of overlapping windows.
3. Unlimited undo and redo.
4. Undo changes after saving them, as long as you did not close the file.
5. Directly edit Unicode text files and text files.
6. EditPad supports all Windows and ISO-8859 as well as DOS, KOI8 and EBCDIC code pages.
7. Block functions: save parts of the text to disk and insert a file in the current text.
8. You have the option to keep the EditPad window on top of all other windows.
9. Fully supports double byte character systems (DBCS) such as Chinese, Japanese or Korean.
10. Word wrap, line numbering and auto indent can be made for each file type individually.
11. Configure appearance to your own taste and eyesight.
12. Uppercase, lowercase, invert case and initial caps conversion.
13. Free for non-commercial use. (Professionals should use EditPad Pro).
14. Quite a bit more!

As you can see, no matter which version of EditPad you try, there are features available which are intelligently designed to help you get things done simply, smartly and effectively. I encourage you to check out EditPad Lite. If you like it and want the syntax coloring or other advanced options, go ahead and buy the Pro version. It will be money well spent.

The importance of running a thorough, regularly scheduled back up cannot be overstressed regardless of whether your site is just starting out or has hundreds of viewers per day. Backing up your important files goes a long way towards preventing or easily repairing many headaches that may come along with broken installations or updates, hacking attempts or if you simply want to move to another domain or hosting provider. After all, an ounce of prevention is worth a pound of cure. In this post, I will show you a basic script you can use as part of your scheduled back up. It will copy your website to a backup folder, zip the contents of the folder and optionally keep a working mirror of your website–automatically!

Why backup?

The problem with backing files up is that most people just don’t see the need to do so until something has happened. Unfortunately, by then it’s usually too late to fix the problem. In reality, if you do not have your website scheduled for a regular daily backup, you are playing a dangerous game Russian roulette with your information. Once a routine backup plan is put into effect, it will give you the peace of mind that comes along with knowing that if problems should occur, you will have… a back up!

Most hosting providers do back up everything on their servers, but that doesn’t necessarily mean they do it often. They may backup the operating system and important information to keep the server running on a daily basis, but most don’t run daily backups of the websites they are hosting. To be honest, it’s just not worth the disk space for them–there could literally be hundreds, even a thousand websites being hosting on a shared server. Of those that do run backups, many charge for restoring the back up they have on copy and it may be weeks or a month old at best. To be honest, they maintain back ups for themselves. It’s your responsibility to back up your own information.

Paid versus shell scripts

There are many back up solutions that rely on the software you have installed on your site. A quick search will bring up a plethora of paid and free plugins available for OsCommerce, WordPress, CRE Loaded, Joomla, etc. There is a problem with these plugins, though: most rely on your installation to work or be somewhat functional and they run the risk of breaking if you update the plugin or the software. While they are generally much easier to use, they are not the most effective way to back up your site and some only back up the specific software installation, not any other files you may be hosting.

So, how do you get around this? The answer is very simple: good, old reliable shell scripts. Shell scripts have been around forever and they are without a doubt the most reliable way of backing up your information. They aren’t as user friendly as web site plugins, but they are free, fast, have a proven track record and there is a wealth of information available about how to use them. They do not rely on anything to be installed except, of course, the operating system your host is running, but that’s assumed. Since they run locally where your information is stored, they are faster than downloading and backing up your site via FTP. It is nice to have a copy of your site downloaded via FTP on hand in case of a major disaster and I do recommend this as well, but that’s for another topic.

Getting started

Before you do anything, though, you need to make sure you have: SSH (shell access) and the ability to run CRON jobs. Godaddy, for example, requires you to activate SSH by phone before you can run CRON jobs, and since you need both, you should go ahead and get it activated before continuing to read. The back up I will show you has been tested on Godaddy via SSH and their CRON job manager, but should work just as well on any other hosting provider that runs Linux with little or no modification necessary. The first script is designed for WordPress and selectively backs up only WordPress and any files in the immediate root directory. It assumes that you have installed WordPress in the root directory. For example: http://www.yourblog.com NOT http://www.yourblog.com/wordpress. The second script can be used for backing up your entire web site–it merely backs up everything in the public html directory. Again, you can easily modify these scripts to suit your needs. You need only to change the directory or directories that you wish to back up in the scripts.

Plan of action

1. Create a directory in your root called ‘backups’
2. Create another directory inside backups called ‘dailyback.’
3. Protect backups with a user name and password using .htaccess and .htpasswd.
4. Create an empty file inside backups with a plain text editor (no Microsoft Word et al–Notepad or gedit are good enough!) call it backup.sh since this is a shell script we’re creating.
5. Into the contents of this file, copy and paste the following script (if you have problems copying and pasting the script, you can download the whole script at the bottom of this page):

#!/bin/bash
#Compliments of www.fortasse.com
#Displays a greeting and backs up files
#Begin Script
TERM=linux
export TERM
NOWDATE=`date +%m%d%y` # Sets the date variable format for zipped file: MMddyy
clear # clears terminal window
echo
echo "Hi, $USER!"
echo
echo "Beginning backup of files @ `date`"
echo "Backing up wp-content..."
#Copy wp-content
cp -r $HOME/html/wp-content $HOME/html/backups/dailyback
echo "Done!"
echo
#Copy wp-admin
echo "Backing up wp-admin..."
cp -r $HOME/html/wp-admin $HOME/html/backups/dailyback
echo "Done!"
echo
echo "Backing up wp-includes..."
#Copy wp-includes
cp -r $HOME/html/wp-includes $HOME/html/backups/dailyback
echo "Done!"
echo
echo "Backing up files in WordPress the root folder /html/ ..."
#Copy miscellaneous files in /html/ only
cp $HOME/html/*.* $HOME/html/backups/dailyback
echo "Done!"
echo
echo "Zipping directory structure..."
tar -cvzf $HOME/html/backups/$NOWDATE.tar.gz $HOME/html/backups/dailyback/*
echo "Backup complete!"
#Uncomment the following lines if you DO NOT want to keep a mirror of your site:
#echo "Cleansing backup folder..."
#rm -r $HOME/html/admin/dailyback/*


You will need to do a couple of things before you can run this. If you’re on Godaddy, you shouldn’t need to make any changes to the script. If you’re not on Godaddy, you might need to change the /html/ folder to /public_html/ or whatever it is that your host uses. Make any other changes you need to the directory structure and uncomment the last two lines if you don’t want to keep a working mirror of your WordPress blog. Upload it to your web site and test it out by opening an SSH connection and going to the directory you uploaded it to and type:
cd ~/html/backups
sh backup.sh

Technically, you don’t need to do all of that copying. You could simply remove almost everything but the last line and tell the script what directory you want to backup. However, I prefer to keep both a working copy (aka mirror) and a zip at all times. It’s a lot faster to simply copy the mirror back over if something broke than to have to unzip and restore the archive. Let’s look at an example of a barebones script that simply zips everything in the public html folder:

#!/bin/bash
#Compliments of www.fortasse.com
#Displays a greeting and backs up files
#Begin Script
TERM=linux
export TERM
NOWDATE=`date +%m%d%y` # Sets the date variable format for zipped file: MMddyy
clear # clears terminal window
echo
echo "Hi, $USER!"
echo
echo "Beginning backup of files @ `date`"
echo
echo "Zipping directory structure..."
#Remove the v in -cvzf below if you don't want to see the output
tar -cvzf $HOME/html/backups/$NOWDATE.tar.gz $HOME/html/*
echo "Backup complete!"


In this case, everything in the public html folder was zipped and the corresponding zip file placed in the ~/html/backups/ directory. This is really effective if you don’t want to selectively back up certain files or directories. I run several backups on my server, at different rates and times and for specific files or directories. Not every web site hosted on my account will necessarily go down at the same time. Therefore, making individual back ups of different installations and/or web sites allows me to have a much finer degree of control over my backups. If I zipped the entire site in one file, I would have to worry about over-writing new content on other unaffected web sites contained in the same root when I expand the zip file. That would be another nightmare altogether!

Backing up your database with MySQLDump

Backing up your database is also very important. If your database goes, in most cases you’ll having nothing. Zilch. Zero. No posts, no users, no links, no tags. You get the point. Thankfully, this is fairly easy to do using a shell script.

Do it!

1. Create a directory called ‘database’ inside the the /html/backups directory.
2. Copy and paste the following code into the bottom of the backup.sh script.

echo "Backing up WordPress database"
mysqldump -h YOUR.DBSERVER.COM -uUSERNAME -pPASSWORD DATABASENAME > $HOME/html/backups/database/$NOWDATE.sql
gzip -9 $HOME/html/backups/database/$NOWDATE.sql
echo
echo "Job finished!"

Replace YOUR.DBSERVER.COM with wherever your database is stored. It might be locally stored on the machine, or it could be located on a remote server in the case of Godaddy. Replace USERNAME with your username, PASSWORD with your actual password and DATABASENAME with the name of the database you want to backup. Keep the spaces, all dashes and everything else you see intact. -p and PASSWORD are supposed to be connected. Do not make a space between them, or it may not work. Like the file back up script, this will back up the database, zip it and put it in an archive with a time stamped file name.

Final steps

You will need to set this script to run through your hosts CRON Job manager. In Godaddy, this is a very simple task. You need to upload the file, open up your Hosting Control Center, go to Cron Jobs and select the file and time you wish to run the shell script. NOTE: You may get a ‘Permission Denied Error!’ In this case, try setting the permissions of the backup.sh file to 755. For other hosting companies, you may or may not have to use CRON Tab or some other CRON job manager. The commands are simple, but call your hosting company if you have any questions. In either case, you should set up the job to send you an e-mail upon completion. At least for the first few days, to make sure the script is working properly. Caveat: If you left to verbose (-v option) on for tar, you may get a very large e-mail.

Summary

So to briefly summarize everything, the first script copies specific directories, creates a mirror and zips the mirrored backup and places it in a backup directory. The file name is the time stamp of the backup date. The second script backs up everything in your public html file (all websites, subdomains, and anything else) and zips it up and does not create a mirror image of your site. The third will backup your SQL database and zip it in a nice little file using gzip. Simple enough, huh?

If all went as planned, you should have a working back up script for your website. I recommend using the script at least daily for the best protection. Enjoy!

• Bloated operating systems (no problem with Linux of course!)
• Gaming capabilities are severely limited due to graphics processing and CPU limitations
• Size versus function

Bloated operating systems

As most people reading this would know, there are several Linux distros which pair up beautifully with the constraints placed on small mobile and embedded devices. I still have one of the first computers I built on my own. It’s an AMD K6-III 333 MHz machine, has a video card with 12 MB of RAM with a maximum of 64 MB RAM currently installed. It used to run Windows XP, which is a fairly light weight operating system compared to Vista and Windows 7. XP is the reliable dog of the Windows family: it’s still being used in a trimmed down fashion for quite a few mobile and embedded devices. Of course, Microsoft is phasing out XP and has plans to make all newer tablets come with Windows 7 Starter Edition (which is fairly nice, but you can’t even change the desktop background with it–whats up with that!?).

Windows XP installs fine on that machine, but you can tell the machine is a bit overwhelmed when trying to run anything that requires processing power. Ubuntu and Xubuntu also install fine on this box. With Ubuntu or Xubuntu installed, however, I can still get a great amount of functionality out of a machine that was, quite frankly, dilapidated when I found it on a curb at the age of 14. Let’s face the truth: Windows is bloated. It’s the epitome of going out to a nice restaurant and gorging yourself on food and drink. The food is great, but you vomit and pass out when you get home. While Windows 7 is better, it still has quite a bit of overhead. Besides that, any flavor of Linux is fairly easy to strip down for anyone who would be interested in doing so. Most devices can be made to function fairly easily without programming specific hardware drivers and Linux tends to be a very lightweight operating system in general. Fact is, my old computer isn’t the ideal comparison subject for this review, but the point is that Linux tends to be much faster and much easier on resources. This makes it ideal for tablets, cell phones, microwaves, routers, toasters and anything else for that matter.

Gaming capabilities

I can see a lot of problems and solutions with this. For example, the trend in applications, games included, is to ‘rise up to the clouds,’ or be flash/Web based. This is awesome because it totally alleviates any problems associated with Windows being the dominant gaming platform. Every O/S runs Flash or can be made to do so and Flash apps can run on the web or as a stand alone application. The recent boom in MySpace and Facebook apps is a fairly straightforward example of this. On top of that, at least a few gaming companies have been talking about making some level of Flash based games, particularly as volume price entry-level versions.

The obviously problems here are this: not everyone has broadband (although this is increasingly less so), people feel most comfortable having a copy of a game they own (unless perhaps it is unbelievably cheap), and finally, not all types of games will work best with Flash as it is at the moment and what about screen size? Honestly, this point is somewhat open-ended because I think it depends a great deal on what happens with console games, the as-yet-to-be-released streaming console games, as well as how consumers respond to Google’s cloud OS.

Size versus function

Lastly, people are increasingly buying laptops as their sole computer and I’m not sure I can see this happening with tablets at this point unless serious strides are made in technology. What about students, for instance? Taking notes on a laptop is bad enough, but on a tablet? I personally use my cell phone for a lot of things I might otherwise use a regular computer or laptop for, (SSH, FTP, VNC and so forth) but that is usually because of necessity (i.e. I have no other computer with me). Most consumers aren’t SSHing into a host or sending a WOL packet to their computer so they can download something they need. That said, the iPhone and the Android OS are great examples of the flexibility of cell phones and their expanding role in the future, but will people want to replace their laptop or even their desktop computer with a tablet? What about their cell phone? Many tablets accept SIM cards and some can even make and accept calls.

What is currently taking place may best be described as the fusion of the desktop computer, the laptop and the cell phone. But is there one or two devices to fit all? I can’t say I would comfortably replace my desktop computer with a tablet at this point. I sure haven’t replaced it with a laptop, but I tend to be quite a bit more tech savvy than the average consumer. What I can say is that my cell phone has taken the place of my laptop when it was either inappropriate or not feasible to bring along, but I would certainly use a laptop instead if it were around.

Conclusion?

No matter what happens, the tablet has some major problems to address: it’s too large to be a cell phone, too small to be a laptop and doesn’t pack enough punch to play current cutting edge games. Perhaps the tablet will replace the laptop or become an extension of the cell phone? Either way, I’ll hold on to my wallet until I start seeing major benefits to owning a tablet.