Transporter software snippet:
$dusty = new Person($attributes, $experiences, $startLocation);
$dusty = transport($dusty, $newLocation)
function transport($person, $newLocation)
{
return new Person($person->attributes, $person->experiences, $newLocation);
}
Like many others, I recently upgraded my Production server to PHP 5.3. I’m not quite sure of the reason anymore. I think I was trying to integrate a PHP profiler that required something in 5.3. Whatever my original reason, after I got 5.3 installed on my server, it started slowly hemorrhaging memory and occasionally freezing up, always during the middle of the night while I slept of course. So, today I set about downgrading PHP 5.3.2 to PHP 5.2.13. Here is what worked for me.
First off, I’m running Ubuntu-Hardy, and both my PHP 5.3 and 5.2 distributions came from dotdeb.org. I have a Production server and a Test server that I try to keep as similar as possible. The first thing I did was make a backup of my Test server with PHP 5.3 installed and my app functional. Then I began hacking away on my Test server trying to successfully downgrade to PHP 5.2. When I screwed the Test server up beyond repair, I restored from backup. Likewise, when I made progress I documented my steps, restored from backup, and tried to repeat my success. I did this several times and eventually made a script that successfully downgraded PHP. I rehearsed this script 3 times on my Test server, backed-up my Production server, then repeated the script on my Production server. IT WORKED!
NOTICE: I probably have a couple of unnecessary steps in here that I didn’t bother to investigate their necessity. You may also need to uninstall and reinstall different PHP modules than I did, depending on the requirements of your applications.
deb http://php53.dotdeb.org stable all deb-src http://php53.dotdeb.org stable all
deb http://http.us.debian.org/debian stable all deb http://security.debian.org/ stable/updates main contrib deb http://packages.dotdeb.org/ stable all
After my production server rebooted, I had to fidget with Apache to get it started again. You may have to:
Hope this helps!
A common practice for Twitter application developers is creating a MySQL table to store user objects returned from Twitter’s API. I’m trying to optimize my user table for Friend Or Follow, and it occurred to me how many developers must be reinventing this MySQL table schema, so let’s get it right once and for all.
Here’s where I’m starting. If you see anything that I’m missing, or notice a data type that could be optimized let me know in the comments and I’ll update the post to reflect your suggestions.
Cassandra is a highly scalable, eventually consistent, distributed, structured key-value store. It’s an alternative to SQL if you don’t need relational data structures. The best part is it’s super fast, and distributed. The worst part is there’s not much documentation or community, at least compared to MySQL. So, I’m doing my small part to contribute to Cassandra. Here’s how I installed Cassandra on Ubuntu 8.04.2 LTS (hardy), but these directions should work on pretty much any Linux distro.
1. First upgrade your software as is with the following two commands (just for good measure):
sudo apt-get update sudo apt-get upgrade
2. Now, open up your Debian package sources list with Nano for editing using the following command:
sudo nano /etc/apt/sources.list
3. Next, add the following sources to your /etc/apt/sources.list file.
deb http://www.apache.org/dist/incubator/cassandra/debian unstable main deb-src http://www.apache.org/dist/incubator/cassandra/debian unstable main
After you add these two lines, press cntrl+X to close Nano. It’ll ask “Save modified buffer?” Press Y. Press Enter when Nano asks “File Name to Write.”
4. Run the update to install Casandra with this command:
sudo apt-get update
5. ERROR! At this point you receive an error similar to this:
W: GPG error: http://www.apache.org unstable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F758CE318D77295D
6. Use the following three commands to ignore the signature error, and continue installing:
NOTE: You must replace the key value ‘F758CE318D77295D’ with the key value you received in your error message.
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys F758CE318D77295D sudo apt-key add ~/.gnupg/pubring.gpg sudo apt-get update
7. Install Cassandra:
sudo apt-get install cassandra
8. Next you need to change Cassandra’s default port number from 8080 to something else, because the 8080 port typically conflicts with SSH terminal connections. Use Nano to open up the Cassandra configuration file using the following command:
sudo nano /usr/share/cassandra/cassandra.in.sh
9. Then change the port number 8080 on the following line to 10036, and save the file:
-Dcom.sun.management.jmxremote.port=10036 \
10. Start Cassandra with the command:
/etc/init.d/cassandra start
Once you have Cassandra running, test it with Cassandra’s command line tool CLI. Use the example found on the Cassandra Wiki.
On November 1st I shaved my face clean for a friendly bet amongst my friends on who could grow their mustache the longest before their significant other gave them ultimatum to shave it. As it turns out, our little bet coincided exactly the same day Movember started. What is Movember? Movember is an annual, month-long celebration of the moustache, highlighting men’s health issues – specifically prostate and testicular cancer. This of course is brilliant, and I couldn’t help but join the cause.
You can help fight against prostate and testicular cancer by becoming a sponsor of my mustache. “Ridiculous” you say? Ok, sponsoring a mustache is a little silly, but this Movember, the money raised in the U.S. will be split between the Prostate Cancer Foundation and the Lance Armstrong Foundation to fund research to find better treatments and a cure for prostate cancer, and there’s nothing silly about that.
DONATE HERE
The link so nice, some times you have to click it twice [to make it work].
