[root@wdc01 /]# grep -r -i "searchstring" ./

and on servers that grep doesn’t support the -r option:

[root@wdc01 /]# find ./ -exec grep "searchstring" /dev/null '{}' \; -print

and to exclude files from the search:

[root@wdc01 /]# find ./ -not -name "*.svn*" -exec grep "searchstring" /dev/null '{}' \; -print

and to search by extension:

[root@wdc01 /]# find ./ -not -name "*.svn*" -name "*.php" -exec grep "searchstring" /dev/null '{}' \; -print

The problem lays in trying to get said app on an actual device. Apparently if your iPhone isn’t jail broken you can’t live test your app without a yearly subscription to Apples Developer Program.

Needless to say, after spending 8-9 hours building an app and not being able to test it on my iPhone I’d had it.

So, instead of a tutorial on your first iPhone app, you get me bitching about Apple wanting $99 a year to test new apps on my personal iPhone and a link to Apples “Your First iOS App” tutorial.

I will post up a small how-to for an iPhone app once I’m over being mad about the $99/year.

But hey. Xcode is cool! Go download it and check it out.

Cloud Computing Makes Documents Easily Accessible

One of the most frustrating issues that comes along with mobile platforms is the fact that storing documents and other data on these devices can be difficult; this is especially true for smart phone users. The cloud has changed everything, however, making it possible to access documents and data quickly and easily. As a result, there's no need to store anything on the device itself while the data lives in the cloud. Many people find this to be the biggest benefit of cloud computing and how it impacts the mobile world.

Cloud Computing Allows for Easy Syncing

Another major benefit that the cloud has brought to mobile technology is the ability to sync documents, calendars and other information. For example, many people like to do their scheduling on a laptop or PC, as typing things out is typically easier on these platforms. Thanks to the cloud, you can create schedules on your PC and sync them up with your phone so that you'll have them on the go. Syncing is the wave of the future, and further supports the notion of a streamlined interplay between different platforms of technology.

Cloud Computing is Effortless

For those who are new to the world of cloud computing, it's not uncommon to feel a bit intimidated by it all. The fact is, however, cloud computing is extremely effortless, requiring little to no work on the part of the user in order to maintain powerful functionality. Most applications sync with the cloud automatically, and usually offer a walk-through on how to sync certain items for those who prefer to do so manually. As a result, no one should worry about cloud computing being too confusing, as it is designed with simplicity in mind; perfect for mobile platforms.

I am just short of 6 feet tall and 195 pounds, which is down 10 from when I decided I was getting a bit old to be eating fast food three meals a day about six months ago.

I haven’t actually started working out yet but I did buy some equipment, change my diet, and started taking some vitamins and supplements.

I now take AM and PM multi-vitamins, Greens+ twice a day, and fish oils twice a day. Additionally, I have cut out most fast food and poorly prepared and fatty foods.

I have a fresh fruit protein shake for breakfast, and a light lunch and dinner.

Just this little amount has increased my energy levels by at least three times, improved my mood, and decreased the amount of sleep that my body thought it required.

I no longer have problems getting up in the morning, nor getting to sleep at night. I’m now sleeping 5 to 7 hours a night and feel great and have ample energy to get through the day and to keep up with my new physically demanding girlfriend.

I am not going to post pictures but will update my progress throughout the process. This week I’m starting cardio! (Not bad since I bought exercise equipment over six months ago intending on working out…)

[root@wdc01 /]# du -x --block-size=1024K | sort -nr | head -10

First the style

<style type="text/css">
    #terms-and-conditions-content{display:none}
</style>

Then the JavaScript

<script type="text/javascript">
    // <![CDATA[
        $(document).ready(function(){ $('#terms-and-conditions').click(function(e){ e.preventDefault();
        var url = $(this).attr('href');
        $('#terms-and-conditions-content').load(url);
        $("#terms-and-conditions-content").dialog({ width:800,modal: true,buttons: { "Close": function() { $(this).dialog("close"); } } }); }); });
    // ]]>
</script>

Then the HTML

    <a id="terms-and-conditions" href="/terms.html">Click Here</a>

Should be straight forward. Just point the link to the file you want to pull into the Dialog box.

Don’t forget that the Dialog is a part of jQuery UI, not just the standard jQuery – you will need to include both.

<script type="text/javascript" src="http<?=$_SERVER['HTTPS']=='on'?'s':''?>://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script>
<script type="text/javascript">
    // <![CDATA[
        !window.jQuery && document.write('<script src="/js/jquery-1.6.2.min.js"><\/script>')
    // ]]>
</script>
<script type="text/javascript" src="/js/jquery-ui-1.8.16.custom.min.js"></script>

I found that using “find” and “mv” worked the best to round them up and put them in the root of the directory structure.

mikej@wdc01 ~/# find * -type f -exec mv {} . \;

Actually I was surprised how easy it was to install SSL certificates for Nginx on Ubuntu.

I don’t remember if it was needed or not at this point or just when I was installing self signed SSL certificates for testing but, make sure you have the ssl-cert package installed:

admin@www1:~/sudo aptitude install ssl-cert openssl

Then make the CSR:

admin@www1:~/sudo openssl req -new -newkey rsa:2048 -nodes -keyout server.key -out server.csr

This will start the process to generate two files: the Private-Key file for the decryption of your SSL Certificate, and a certificate signing request (CSR) file used to when ordering your SSL Certificate.

When you are prompted for the Common Name, which is your domain name, enter the fully qualified domain name for the site you are securing. Either www.afterdarkmike.com or afterdarkmike.com. Remember accessing the opposite of which you select via web browser will generate a miss-match domain security warning, with most browsers stopping you there.

If you are generating a Wildcard SSL Certificate for your Nginx server, make sure your common name starts with an asterisk (e.g. *.afterdarkmike.com).

Open the .csr file with a text editor (nano,vi,etc) and copy and paste it (including the BEGIN and END tags) into your SSL order form. Save the certificate files, you will need them later.

In my case I was purchasing a GeoTrust RapidSSL Certificate for a clients website we host and manage at After Dark Communications.

At the time of posting, your RapidSSL order will be shipped via an email which will include the SSL Certificate as well as the intermediate CA bundle. Copy them both into one file, including the —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—– header/footers and save it as commonname.crt. ex afterdarkmike.com.crt.

So your file will look like:

-----BEGIN CERTIFICATE-----
Web Server CERTIFICATE blahblah blah blah blahblah blah
...
blahblah blah blah blahblah blah
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
INTERMEDIATE CA CERTIFICATE blahblah blah blah blahblah blah
...
blahblah blah blah blahblah blah
-----END CERTIFICATE-----

Upload it to the server.

Now to set up Nginx.

Edit the Nginx Virtual Hosts File:

server {
	listen 443;
	ssl on;
	<strong>ssl_certificate /etc/ssl/ssl.crt;</strong>
	<strong>ssl_certificate_key /etc/ssl/domain.key;</strong>
	server_name your.domain.com;
	access_log /var/log/nginx/nginx.vhost.access.log;
	error_log /var/log/nginx/nginx.vhost.error.log;
	location / {
		root /home/www/public_html/your.domain.com/public/;
		index index.html;
	}
}

Adjust the file names to match the certificate files and restart Nginx.

2011-10-03 03:31:43 1RAZFn-0006hC-I2 <= www-data@corp.host.com U=www-data P=local S=648
2011-10-03 03:31:43 1RAZFn-0006hC-I2 ** sales@host.com R=nonlocal: Mailing to remote domains not supported
2011-10-03 03:31:43 1RAZFn-0006hE-Ig <= <> R=1RAZFn-0006hC-I2 U=Debian-exim P=local S=1619
2011-10-03 03:31:43 1RAZFn-0006hC-I2 Completed

In my default Ubuntu VPS image, the “local mail only” feature is set.

Executing the following command and selecting the “internet site; mail is sent and received directly using SMTP” option will solve your issue. You should be able to select the default option for the rest of the questions.

admin@db:~$ dpkg-reconfigure exim4-config

admin@db:~$ sudo /etc/init.d/mysql restart
* Stopping MySQL database server mysqld <strong>[fail]</strong>
* Starting MySQL database server mysqld [ OK ]
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: '<strong>Access denied for user 'debian-sys-maint'@'localhost'</strong> (using password: YES)'

This MySQL user is created for Ubuntu to be able to start/stop the database and to preform other maintenance operations.

The issue is that with each update to MySQL, the user’s password in the database is overwritten.  Ubuntu searches the file /etc/mysql/debian.cnf in order to find this user’s password, but obviously the password was out of sync after copying the databases from the old database server.

First, check the contents of the /etc/mysql/debian.cnf file:

admin@db:~$sudo cat /etc/mysql/debian.cnf

The contents of the file should look something like the:

# Automatically generated for Debian scripts. DO NOT TOUCH!
[client]
host     = localhost
user     = debian-sys-maint
<strong>password = PASSWORD</strong>
socket   = /var/run/mysqld/mysqld.sock
[mysql_upgrade]
user     = debian-sys-maint
<strong>password = PASSWORD</strong>
socket   = /var/run/mysqld/mysqld.sock
basedir  = /usr

The PASSWORD   is what we’re looking for.

Next, you will want to issue a command to MySQL to tell it to grant the debian-sys-maint user all necessary privileges using the new password.

Login to your MySQL server using your root account and the root password:

admin@db:~$ mysql -u root -p

Issue the GRANT command now to grant those permissions:

mysql> GRANT ALL PRIVILEGES ON *.* TO 'debian-sys-maint'@'localhost' IDENTIFIED BY 'PASSWORD';

Restart MySQL, you should no longer be getting the “access denied” error message.

admin@db:~$ sudo /etc/init.d/mysql restart
* Stopping MySQL database server mysqld [ OK ]
* Starting MySQL database server mysqld [ OK ]
* Checking for corrupt, not cleanly closed and upgrade needing tables.

You may need to kill the MySQL server processes in order to get MySQL to shut down.