Posted: January 1st, 2012 | Author: Alex Korn | Filed under: Uncategorized | Tags: PHP | No Comments »
On Facebook today, I noticed one of my friends posted a picture with the label “1/365″. Like other people, she’s attempting to post one picture every day of the year. An admirable goal!
This got me thinking: I wonder how long it takes most people to give up on resolutions? Well, the best (read: easiest and cheapest) way to figure this out is to see how many Google results there are for “1/365″, “2/365″, etc.
This is how quickly we give up on our resolutions*:
It appears most people give up after the first week, and the vast majority give up after the first month or two. But if they stick with it for the first 10 months or so, they’re talking about it a lot until the end of the year.
The technical details
First off, Google’s estimates of how many results a query has are grossly exaggerated (thanks, James). The chart above uses Andrew Zich’s Google Search Matrix.
I had to remove some outliers, which I set to be the average of up to 3 days on either side of them.
- “7/365″: 719k (mostly in the form of “24/7/365″)
- “364/365″: 1.8m (apparently a lot of sites just have numbers in sequence)
Below is the PHP script I used to generate the numbers initially. Note that the Google homepage (and thus the text around the number of results) looks different when you aren’t logged in.
echo '<html><table>';
$matches;
for ($i = 1; $i <= 365; ++$i)
{
$url = 'http://www.google.com/search?q=' . urlencode('"' . $i . '/365"');
$result = file_get_contents($url);
preg_match('/of about <b>(.*)<\/b> for/', $result, $matches);
echo '<tr><td>' . $i . '</td><td>' . str_replace(',', '', $matches[1]) . '</td></tr>';
}
echo '</table></html>';
Here is the chart created with the numbers that Google estimates on the first page of results:
The general shape of the data is the same, but the actual numbers of results are very different between the two.
The disclaimer
Oh man, this is so unscientific it almost hurts. Just because someone stops posting about their resolutions doesn’t mean they’ve given up. Not everyone who’s come up with a resolution posts about it online. Etc etc etc. I sacrificed a lot of scientific rigor to come up with a catchy title.
Posted: July 22nd, 2011 | Author: Alex Korn | Filed under: Uncategorized | Tags: key repeat, lion, os x | No Comments »
To enable key repeat in Mac OS 10.7 Lion, open up your Console, enter the following line, then restart your computer.
defaults write -g ApplePressAndHoldEnabled -bool false
The default behavior in 10.7 is to have a special keys selector pop up when holding down a key, similar to the behavior in iOS. This can be handy for typing accented letters, but makes things like navigating in Vi much more difficult. As of now, there is no way to change this setting in the user interface.
Posted: May 2nd, 2011 | Author: Alex Korn | Filed under: Uncategorized | Tags: fonts, Mac OS X, netbeans | 3 Comments »
The quick version
For those who want to turn off text anti-aliasing in NetBeans 7 on Mac OS X without reading my tirades, just make the following changes to the definition of netbeans_default_options in /Applications/NetBeans/NetBeans\ 7.0.app/Contents/Resources/NetBeans/etc/netbeans.conf (or something similar if you didn’t install it in the default location):
Add:
-J-Dswing.aatext=false -J-Dawt.useSystemAAFontSettings=off
Change:
-J-Dapple.awt.graphics.UseQuartz=false
Restart NetBeans and you should have non-anti-aliased fonts.
The full story
The perfect programming font: many have searched; few have found.
It’s Monaco, 10pt, no anti-aliasing.
But I digress. My goal here is not to discuss fonts (but seriously, I love discussing fonts), but to write the most keyword-heavy post for those trying to figure out how to turn off text anti-aliasing in NetBeans 7 on Mac OS X. By default, NetBeans uses anti-aliasing for its editor, which, for most fonts, is great, but not for Monaco 10pt.
When I used NetBeans 6.x, I found this page to be quite useful. However, when I tried turning off anti-aliasing with NetBeans 7.0, it did not work.
After a bit of exploring, I found the key to be setting -J-Dapple.awt.graphics.UseQuartz=false. I believe Quartz refers to the 2D graphics rendering API for OS X, but for the sake of your non-anti-aliased font, you certainly don’t need it.
In-Application Setting
NetBeans has been well aware of the issue for quite some time, so don’t expect the anti-aliasing setting to be modifiable inside the application any time soon.
Posted: April 28th, 2011 | Author: Alex Korn | Filed under: AWS, Hosting, Tutorials | Tags: PHP | 2 Comments »
For those who have sent emails in PHP, the following code should look quite familiar:
mail($to, $subject, $message);
Unfortunately, this will silently fail on Amazon Web Services. But you do need to send those emails, right? Well, it’s pretty easy to get emails sent from AWS with Amazon Simple Email Service (Amazon SES). However, in my research on this, I found several false leads and no good tutorials, so here goes: step by step, how to send emails with AWS.
First step: sign up.
AWS SDK for PHP
Next, install the source code code for AWS SDK for PHP. Run the following in the directory where you store external libraries (using sudo when needed):
yum install git
git clone git://github.com/amazonwebservices/aws-sdk-for-php.git AWSSDKforPHP
Now that you have the the AWS SDK on your server, include AWSSDKforPHP/sdk.class.php into your application. You now have access to the AmazonSES class.
The following is a basic function to emulate PHP’s mail().
function amazonSesEmail($to, $subject, $message)
{
$amazonSes = new AmazonSES(AWS_KEY, AWS_SECRET_KEY);
$response = $amazonSes->send_email(AWS_SES_FROM_EMAIL,
array('ToAddresses' => $to),
array(
'Subject.Data' => $subject,
'Body.Text.Data' => $message,
)
);
if (!$response->isOK())
{
// handle error
}
}
Note that you need to define the AWS_KEY and AWS_SECRET_KEY for your application. You can find these by going to your AWS Security Credentials page and looking under “Access Keys”.
Validating the sending email address
Next, define AWS_SES_FROM_EMAIL to be the email address from which you want to send emails, e.g. no-reply@example.com. If you try to send an email at this point, you’ll get a MessageRejected error with the message “Email address is not verified.” Several pages I visited recommended I download the Amazon SES Scripts (Perl), but don’t do it! You’ll need to subject yourself to a world of pain in the form of installing Perl modules* (and probably Perl too, given that your reading a post on PHP!).
Instead, you can actually use AmazonSES to verify email addresses in PHP.
$amazonSes = new AmazonSES(AWS_KEY, AWS_SECRET_KEY);
$amazonSes->verify_email_address($fromEmailAddress);
Much easier than the Perl script shenanigans. This will send an email to your sending email address with a link to verify that you own that email address. Do the same for your recipient addresses (since you’re in sandbox mode, which has restrictions including the requirement to validate your recipient address). Verify each address and you should be good to go to send emails.
Setting up production access
At this point you’ll be able to send a couple test emails, but the volume is fairly limited. Request production access and you should be granted the ability to send many more emails.
Reference
Visit the AWS SDK for PHP reference page for much more information on how AWS SDK for PHP works.
Amazon SES Scripts (Perl)
If you do want to install the Amazon SES Perl scripts and are getting an error along the lines of “Can’t locate XML/LibXML.pm in @INC…”, you can use yum to install all of the necessary packages to get them to run.
yum -y install perl-Digest-SHA perl-URI perl-libwww-perl perl-MIME-tools perl-Crypt-SSLeay perl-XML-LibXML
Thanks to this post for that hint.
(^ Back up)
Posted: March 25th, 2011 | Author: Alex Korn | Filed under: Tutorials | Tags: design patterns, PHP | No Comments »
The observer pattern is a handy design pattern often used in UI-focused languages like JavaScript, but not often used in PHP. Prior to PHP 5.3, the observer pattern was cumbersome to use and required a lot of objects – one for every possible observer. However, anonymous functions (Closures) in PHP 5.3 can replace the previously used Observer objects. This makes the observer pattern much more practical by reducing the number of classes that you need to make, often for one-time use.
Let’s write up our basic Observable object. You may want to make this class abstract since it’s probably not useful on its own.
class Observable
{
/**
* @var array Map<string eventName, List<Closure observer>> $_observers
*/
protected $_observers = array();
/**
* @param string $eventName
* @param array $data
*/
protected final function _fireEvent($eventName, array $data = null)
{
if (isset($this->_observers[$eventName]))
{
foreach ($this->_observers[$eventName] as $observer)
{
$observer($data);
}
}
}
/**
* @param string $eventName
* @param Closure $observer With parameter (array $data)
*/
public final function addObserver($eventName, Closure $observer)
{
if (!isset($this->_observers[$eventName]))
{
$this->_observers[$eventName] = array();
}
$this->_observers[$eventName][] = $observer;
}
/**
* @param string $eventName
* @param Closure $observer The observer to remove
*/
public final function removeObserver($eventName, Closure $observer)
{
if (isset($this->_observers[$eventName]))
{
foreach ($this->_observers[$eventName] as $key => $existingObserver)
{
if ($existingObserver === $observer)
{
unset($this->_observers[$eventName][$key]);
}
}
}
}
}
Now that we have the basic observable class, let’s look at a simple example:
class Person extends Observable
{
protected $_name;
protected $_friends = array();
public function __construct($name)
{
$this->_name = $name;
}
public function getName()
{
return $this->_name;
}
public function getIntroducedTo(Person $person)
{
$this->_friends[] = $person;
$this->_fireEvent('introduced', array('other' => $person, 'me' => $this));
}
}
$sally = new Person('Sally');
$sally->addObserver('introduced', function(array $data)
{
echo 'Hi, ' . $data['other']->getName() . ', my name is ' .
$data['me']->getName() . '.';
});
$sally->getIntroducedTo(new Person('Harry'));
The output will be "Hi, Harry, my name is Sally.". Note that you can easy modify the greeting Sally uses from outside that Person object without changing the functionality of adding the friend.
And there you have it – the observer pattern and an example, in less than 75 lines of code!
Posted: March 17th, 2011 | Author: Alex Korn | Filed under: AWS, Hosting, Tutorials | Tags: amazon, apache, ec2, linux, mysql, PHP | 22 Comments »
Do you know nothing about Amazon Web Services (AWS) or Linux server administration, but want to get a PHP/MySQL server set up on AWS? I was once like you, relying upon my web host to have PHP and MySQL installed and configured, so it was a bit daunting initially to work with AWS, but it’s actually rather simple. Read on and I’ll show you how to set up PHP and MySQL on one of Amazon’s free servers step by step. You can have a functioning site up and running within half an hour.
Amazon Web Services
First things first: Amazon Web Services has a ton of different products, but the one you want is Amazon Elastic Compute Cloud (EC2). Go there, and click “Sign Up for Amazon EC2″.
Once you’ve gotten that set up, go to the AWS Management Console, and click on “Instances” in the Navigation panel. An Instance is just a virtual server – so let’s create one! Click “Launch Instance” under “My Instances”, and select “Basic 64-bit Amazon Linux AMI”. On the Instance Details phase, select “Micro” (which is Free tier eligible). Continue until you need to enter the “Name” – if you don’t know what else to call it, just use “Web/DB server”.
Next you create a Key Pair – this will be the credentials you’ll use to SSH into the box. The instructions here should be fairly straightforward. Next is the Security Group, which will be used to specify the firewall used for your instance. Feel free to use the default Group for now. Continue to the Review phase and launch it!
You should now be able to SSH into your instance using your .pem file with ssh -i [FILE NAME].pem ec2-user@ec2-[IP ADDRESS].compute-1.amazonaws.com. Alright, we’ve got a server up and running! However, you may notice that this server has very little installed on it. which php? Nothing. which mysql? The same. Let’s install some software.
Configuring the Linux Server
Below I’ll show you how to set up PHP and MySQL on the server. I’ve separated PHP and MySQL so that it’s easier to adapt this to having two instances.
PHP
First, the basics for PHP:
sudo yum install php-mysql php php-xml php-mcrypt php-mbstring php-cli mysql httpd
Press ‘y’ for each of the prompts that shows up. Note that you’re logged in as ec2-user, so you need to sudo all of these commands.
You should now be able to create and run a PHP test file. Next, let’s get MySQL up and running.
MySQL server
First, install and begin running the server:
sudo yum install mysql-server
sudo /etc/init.d/mysqld start
Next, set the root password. I’ve found this password generator to be just dandy.
mysqladmin -u root password '[PASSWORD]'
Now we set up two users for MySQL: the administrator, which you’ll use to create and modify tables; and the app user, which the app will use to query the DB (with more limited privileges). Log into MySQL as root (mysql -u root -p) and enter each of the following lines:
CREATE DATABASE [DB NAME];
CREATE USER '[DB NAME]_admin'@'localhost' IDENTIFIED BY '[ADMIN PASSWORD]';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER ON [DB NAME].* TO '[DB NAME]_admin'@'localhost';
CREATE USER '[DB NAME]_user'@'localhost' IDENTIFIED BY '[USER PASSWORD]';
GRANT SELECT, INSERT, UPDATE, DELETE ON [DB NAME].* TO '[DB NAME]_user'@'localhost';
You may want to fine-tune your database settings further than this, but this is a good start.
Make it web-accessible
We now have PHP and MySQL running on the box, but cannot access it through a browser. We need to configure the web server and set up an Elastic IP.
Web Server
First, let’s create a test PHP file that will be accessed by the browser. Create directories so that you can put your file in /opt/app/current1. Make an index.php file that contains whatever you want.
If you want to FTP transfer files to your server, you’ll want to give the ec2-user permissions to modify files in your web directory:
sudo chown ec2-user /opt/app/current
To set up the web server, httpd, we need to first modify its configuration file, located at /etc/httpd/conf/httpd.conf. Open it up with vim, emacs, or your favorite text editor, and go to the bottom of the file. Here you’ll see a small section on the VirtualHost (between <VirtualHost *:80> and </VirtualHost>). Uncomment it out and set DocumentRoot to /opt/app/current. Restart (or start) httpd:
sudo /etc/init.d/httpd restart
Elastic IP and Security Groups
In the AWS Management Console, click on “Elastic IPs”, then “Allocate New Address” under “Addresses”. Once the address is created, click on it, then “Associate Address”. Select the instance and associate it.
Now click on “Security Groups” in the Navigation panel. Select the Security Group that you used for the instance (probably the default one). Under the “Inbound” tab, add an HTTP rule (port 80). Click “Apply Rule Changes”, and you should now be able to access your website! In your browser, go to http://ec2-[IP ADDRESS].compute-1.amazonaws.com/, where the IP address is the Elastic IP you made with periods replaced with hyphens.
Hello World! or Putting it all together
We now have all the pieces we need to access MySQL from PHP and serve that to the browser-accessible website. So let’s log into mysql and create a sample table:
mysql -u [DB NAME]_admin -p
[type password]
mysql> use [DB NAME];
mysql> CREATE TABLE test (message VARCHAR(255));
mysql> INSERT INTO test (message) VALUES ('Hello world!');
Now modify your index.php file (/opt/app/current/index.php) to be the following:
<?php
$conn = new mysqli('localhost', '[DB NAME]_user', '[USER PASSWORD]', '[DB NAME]', '');
$result = $conn->query("SELECT message FROM test;");
$row = $result->fetch_assoc();
echo $row['message'];
?>
We now have a fully functioning PHP and MySQL server!
Taking it further
That’s it for the basics, but there’s so much more that you can do now.
sudo pear upgrade
sudo yum install php-pear
sudo pear channel-discover pear.phpunit.de
sudo pear channel-discover pear.symfony-project.com
sudo pear channel-discover components.ez.no
sudo pear install phpunit/PHPUnit
I’ve found it handy to set up an administration area for my sites using a different port on the same URL. Note that port 80 is the default for web traffic, but 8080 is also commonly used.
Create /opt/app/admin. Then, in httpd.conf, add the line Listen 8080 after Listen 80 and add another VirtualHost entry, using <VirtualHost *:8080> and pointing to the /opt/app/admin directory. Update your Security Group to allow traffic over port 8080. Make sure to restart Apache and you should now be able to access your admin folder through your browser at yourdomain.com:8080.
You can then download phpMyAdmin into /opt/app/admin/pma and unzip it. Using the [DB NAME]_admin user, you can now manage your databases there through your browser.
Using two Instances
It can be very beneficial to performance to separate the web server and the DB server. To do this, you’ll need to set up two Instances, one of which has the web server httpd running and an Elastic IP, and the other of which has the MySQL server mysqld running.
They can use the same Security Group, but you’ll have to add the MySQL rule (port 3066) for Inbound traffic to allow the servers to talk to each other.
On the web box, instead of using “localhost” as the MySQL host, use the Internal IP address of the MySQL box. On the DB box, set up your grant permissions to allow from anywhere in '%.ec2.internal' (or just from your IPs).
Notes
-
/opt/app/current is a Rails convention that I enjoy. What you should do is put your releases in /opt/app/releases/[release #], then have /opt/app/current be a symlink to the current release.
Another (much more) common standard is to put web-accessible code in /var/www/html. Feel free to put your HTML code wherever you want; just make sure to update httpd.conf appropriately (and restart Apache).
^ Back up
Thanks to Ryan Ausanka-Crues at Palomino Labs for help with this.
Posted: July 1st, 2010 | Author: Alex Korn | Filed under: Browsers | Tags: Google Chrome, Mac OS X, WTF | No Comments »
I, along with many of my friends and coworkers, have run into issues with maximizing Google Chrome windows on Mac OS X. It seems that, when clicking on the green button in the title bar, that the window resizes vertically, but not horizontally. And when you’re actually trying to get the window to fill up the full screen, this is highly unfortunate.
What’s going on
The green button is not the Maximize button in OS X; it’s the Zoom button. As described in Chrome’s issues tracker, Chrome’s intended behavior for this button is to “size-to-best-fit, not fill-screen”. Therefore, it will only make the window wider if there is some visible content on the page that’s wider than the window is currently, i.e., if there’s a horizontal scrollbar. This page shows it quite wonderfully: there’s a 65k-pixel-wide div at the bottom that will make the window expand to the full screen size when you Zoom. Hide the div, and the window will only expand vertically.
How to make Zoom fill the full screen
Despite this somewhat unexpected default behavior, there are a couple ways to fill the screen anyway when Zooming:
-
Press Shift when you click on the Zoom button. This, as implemented by Chrome, will make the window fill the full screen.
-
This one has some subtlety: Under System Preferences->Keyboard->Keyboard Shortcuts->Application Shortcuts, add a shortcut for Chrome. Make the Menu Title be “Zoom” (it’s under the Window menu). Since Command+M is the keyboard shortcut for Minimize, let’s make the Keyboard Shortcut for Zoom be Command+Shift+M. Go back to Chrome and try it out your keyboard shortcut. Voila! But wait–if you just click on Zoom in the menu, it will continue to resize only vertically. What’s going on here? Because you’re pressing Shift while activating Zoom with the keyboard shortcut, it works just like pressing Shift while clicking the green button. No joke.
Versions and such:
- Chrome version: 5.0.375.86
- OS X version: 10.6.4
Posted: May 19th, 2010 | Author: Alex Korn | Filed under: JavaScript | Tags: Google Chrome, Holmes, JavaScript, Mozilla Firefox, PHP | 1 Comment »
So you’ve been writing some JavaScript files (or HTML files or images) and testing them in Google Chrome or Mozilla Firefox. Unfortunately, you’ve deleted the JavaScript files, forgot to check them into the repository, didn’t make a backup, and they’re gone. Don’t fear! There is still hope!
Your missing file is stored in your browser’s cache, which can be accessed by typing about:cache into the URL box in Chrome or about:cache?device=disk in Firefox. This will list links to every file in your cache (and thus may take a moment to open). Individual files can be accessed by going to chrome://net-internals/view-cache/[[URL]] in Chrome or about:cache-entry?client=HTTP&sb=1&key=[[URL]] in Firefox.
The cached version will look like the following in Chrome:
[[URL]]
HTTP/1.1 200 OK
Date: Wed, 19 May 2010 15:17:36 GMT
Server: Apache
Last-Modified: Wed, 19 May 2010 15:13:53 GMT
ETag: "18aa1e6-1761-486f3e7ebae40"
Accept-Ranges: bytes
Content-Length: 5985
Content-Type: application/javascript
00000000: fb 00 00 00 01 00 00 00 34 62 bc 3d 8a e5 2d 00 ........4b.=..-.
00000010: ef 1a be 3d 8a e5 2d 00 e3 00 00 00 48 54 54 50 ...=..-.....HTTP
00000020: 2f 31 2e 31 20 32 30 30 20 4f 4b 00 44 61 74 65 /1.1 200 OK.Date
00000030: 3a 20 57 65 64 2c 20 31 39 20 4d 61 79 20 32 30 : Wed, 19 May 20
00000040: 31 30 20 31 35 3a 31 37 3a 33 36 20 47 4d 54 00 10 15:17:36 GMT.
00000050: 53 65 72 76 65 72 3a 20 41 70 61 63 68 65 00 4c Server: Apache.L
00000060: 61 73 74 2d 4d 6f 64 69 66 69 65 64 3a 20 57 65 ast-Modified: We
00000070: 64 2c 20 31 39 20 4d 61 79 20 32 30 31 30 20 31 d, 19 May 2010 1
00000080: 35 3a 31 33 3a 35 33 20 47 4d 54 00 45 54 61 67 5:13:53 GMT.ETag
00000090: 3a 20 22 31 38 61 61 31 65 36 2d 31 37 36 31 2d : "18aa1e6-1761-
000000a0: 34 38 36 66 33 65 37 65 62 61 65 34 30 22 00 41 486f3e7ebae40".A
000000b0: 63 63 65 70 74 2d 52 61 6e 67 65 73 3a 20 62 79 ccept-Ranges: by
000000c0: 74 65 73 00 43 6f 6e 74 65 6e 74 2d 4c 65 6e 67 tes.Content-Leng
000000d0: 74 68 3a 20 35 39 38 35 00 43 6f 6e 74 65 6e 74 th: 5985.Content
000000e0: 2d 54 79 70 65 3a 20 61 70 70 6c 69 63 61 74 69 -Type: applicati
000000f0: 6f 6e 2f 6a 61 76 61 73 63 72 69 70 74 00 00 on/javascript..
00000000: 2f 2a 2a 0a 20 2a 20 40 61 75 74 68 6f 72 20 41 /**. * @author A
00000010: 6c 65 78 20 4b 6f 72 6e 20 3c 61 6c 65 78 6b 6f lex Korn <alexko
...
The last section (in both browsers) displays the hexadecimal representation and the text of your file. The last column of this section displays newline characters as periods in many text editors, so we can’t use it to recover the file. We’ll have to use the hexadecimal. I wrote the following PHP script, which will extract and convert the hexadecimal representation into the text version:
<?php
$cacheString = ''; // COPY THE LAST SECTION IN HERE (Use /'/\\\'/g to escape quotation marks)
$matches = array();
preg_match_all('/\s[0-9a-f]{2}\s/', $cacheString, $matches);
foreach ($matches[0] as $match)
{
echo chr(hexdec($match));
}
?>
Voilà! Your once-lost code is now found!
A couple notes:
- If your server has compression enabled (such as gzip), you’ll have to go through the extra step of unzipping the content
- Chrome version: 5.0.375.38 beta
- Firefox version: 3.6.3
Update 2011/05/14: I changed the \b’s in the RegEx to \s’s as recommended in this post on recovering gzipped files.