Setting up your environment

Using a SSH client such as Putty – connect to your web server and create a directory in your users home named “bin”

$ cd ~
$ mkdir bin
$ cd bin

Next we need to download a stable copy of Zend Framework via subversion using the following command :

$ svn checkout http://framework.zend.com/svn/framework/standard/branches/release-1.10/

If svn (Subversion) is not installed you can download via wget using the following command :

$ wget http://framework.zend.com/releases/ZendFramework-1.10.3/ZendFramework-1.10.3-minimal.tar.gz

Next we need to untar (decompress) the framework :

$ tar -zxvf ZendFramework-1.10.3-minimal.tar.gz

Rename the decompressed folder :

$ mv ZendFramework-1.10.3-minimal Zend

** Note if you used subversion to acquire Zend Framework – you probably have downloaded the release directory – use the command above replacing the first argument with the release directory name.

Move the scripts from the Zend/bin directory into the ~/bin directory; make them executable; rename zf.sh to just zf (for simplicity) :

$ mv Zend/bin/* .
$ chmod +x zf.sh
$ mv zf.sh zf

The next step is to add the zf script to the users include path, this allows us to use the zf command without having to specify the absolute path. Copy and paste the next 6 lines into your shell :

cat << EOF >> ~/.bashrc
if [ -d ~/bin ] ; then
PATH=~/bin:"\${PATH}"
fi
export PATH
EOF

You must now log out and back in to activate this path. Once you are logged back in you can test the zf command by typing :

$ zf show version

If you see “Zend Framework Version: 1.10.3″ you are ready to start your first project.

Creating your first project

Change to your web server document root, assuming you are using a Debian based server you can find it usually in /var/www (RHEL generally defaults to /var/www/html) :

$ cd /var/www

Create a project using the following command :

$ zf create project <project_name>

Where <project_name> is the name of your project in lowercase alpha numeric form (no symbols, spaces, uppercase letters (hyphens and underscores are OK))

Link your Zend library to your projects library directory as such :

$ ln -s ~/bin/Zend /var/www/project_name/library

Where /var/www is your web server document root and project_name is the name of your project.

If all went well – point your browser to your web server hostname or IP / your project name / public ( http://example.com/project_name/public ).

That is all for now – we’ll get into the actually writing some code next time. Leave me some comments below!

One of the biggest problems switching hosts is migrating email accounts, luckily we use Zimbra and it was extremely simple – this is how I did it :

imapsync –nosyncacls –subscribe –syncinternaldates –host1 old.server.tld –user1 user@domain.tld –password1 password –host2 new.server.tld –user2 user@domain.tld –password2 password

IMAP Sync is a wonderful application that can easily be installed on RHEL5 / CentOS using the DAG repository (just google “DAG”).  There are three or four Perl dependencies to get it working however once you have everything installed you are ready to import.

This is more or less a note for my own records – hopefully you will find it useful as well.

For those who don’t know – creating stylesheets that render identically in both Internet Explorer and Good browsers is a saught after talent.  I could get into a whole mess about how yucky it is working with IE but instead you can Google it yourself, someone else has no doubt already written about this much better than I can.

A quick explanation of !important is as follows :

Firefox renders it, Internet Explorer doesn’t.  For Example :

margin-left:10px !important;

margin-left:5px;

Firefox will push whatever div over 10 pixels while Internet Explorer will get confused, skip the line and render the 5px margin.

It is important to put !important before any other “contradicting” statements as it could play mind games and mess you up something awful.

Take a look at the in-progress template and tell me what you think…

http://rxbalance.enumplus.org

I have been in Denver Colorado for the past week at a natural health conference (I was the IT insurance in case something broke).  It turned out quite well, though I never got to see the rockies – a crying shame!  Anyway all was not lost, I was able to hit up the duty free in Niagara Falls late Wednesday evening for some wicked deals!

I ended up walking away with a 40oz bottle of rum (with Mai Tai mixer) and a carton of delicious Marlboro Reds for $50 on the dot – I couldn’t be happier!  Anyway it is Friday night and time to get full use of my purchases.

# mysqldump –all-databases -u root -p  > dump.sql

Once you import this database on the new host there is a good chance you will not be able to restart mysql as the debian-sys-maint user account passwords will not match.

# mysql -u root -p < dump.sql

So the easiest way to fix this issue is to :

web:~# cat /etc/mysql/debian.cnf 

# Automatically generated for Debian scripts. DO NOT TOUCH!

[client]

host     = localhost

user     = debian-sys-maint

password = PASSWORD

socket   = /var/run/mysqld/mysqld.sock

[mysql_upgrade]

user     = debian-sys-maint

password = PASSWORD

socket   = /var/run/mysqld/mysqld.sock

basedir  = /usr

desktop gregory # vmware
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4′ not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0′ not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4′ not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0′ not found (required by /usr/lib/libstdc++.so.6)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_3.4′ not found (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1: version `GCC_4.2.0′ not found (required by /usr/lib/libstdc++.so.6)

You have probably seen this yourself if running any Ubuntu flavored distributions, heres my fix :

desktop gregory # rm /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1
desktop gregory # ln -s /usr/lib/gcc/i486-linux-gnu/4.2/libgcc_s.so /usr/lib/vmware/lib/libgcc_s.so.1/libgcc_s.so.1

Now I wil never forget…

My TIBook only has USB 1.1 (12mbps) so it was VERY nice to be able to use ethernet (100mbps) to backup my data.

It was good to see other people were interested in doing this as well – I am sure it is old news but here are the two tutorials I followed :

This wonderful blogger has created a super easy to follow tutorial for setting up your NAS to support AFP (netatalk)

HowTo: Make Ubuntu A Perfect Mac File Server And Time Machine Volume [Update6]

This one shows you how to easily create a sparseimage to transfer over to your NAS if you continually get “could not create disc” errors :

Making Time Machine work with the ReadyNAS

Time Machine is an amazing application and adding a network layer on top just increases it’s value.  I hope you find these links as useful as I did.

On the Client (the box you will be using to connect)

$ ssh-keygen -t dsa -f ~/.ssh/id_dsa -P ''

On the Server (copy ~/.ssh/id_dsa.pub to this machine)

$ cat id_dsa.pub >> ~/.ssh/authorized_keys
$ chmod 600 ~/.ssh/authorized_keys

Back on the Client

$ ssh -i ~/.ssh/id_dsa root@<hostname>

Where hostname is the SSH server.
You may be asked to put in your password one last time, I do not believe I had to myself.
Now you can just ssh <username>@<hostname> and voila, you are in!

You can imagine how much time this saves me whilst administering ~ 10 boxes.

A Brick (I probably do not have permission to use this)

If you are suffering the loss of a beloved GXP as well, do not fret – geekhut has the fix!

What you need :

• A router that is not currently serving you data (I used m0n0wall on an old p3) <= we will discuss that later.
• Firmware
• Sailor hat, for absolutely no reason

Procedure

1. Plug your router in as you normally would, internet access is not needed at this time.
2. Plug your phone into any one of the LAN ports
3. Configure your router’s IP to : 168.75.215.1, Subnet : 255.255.255.0
4. Plug a computer into the LAN port of the Phone (it didn’t seem to work for some reason when I plugged it into the switch…)
5. Install a TFTP server on that computer, Windows sure has a lot of shitty ones – instead I temporarily loaded my tftp.plist (I think i used -f) on my Mac.
6. Unzip the Firmware you downloaded earlier into your tftpboot directory, Leopard is funky and puts it under /private/tftpboot.
7. Statically set your Computer (the one plugged in behind the phone with TFTPD) to IP : 168.75.215.188 (same subnet as above.)
8. Cross your fingers, power cycle your phone – read the screen carefully.

* Things are strong because they matter.

I hope you now have a working phone again, you can send your love in comments.

There are a million how-to’s out there for those who love dicking around writing your own script, but I don’t have time for that – that’s why I use this.  I have lost this link so many times, it is definitely worth bookmarking.

All you have to do is upload the tgz to your local modules in FreePBX and then click install / enable – no coding, no headaches plus it works very well.

There is one step not documented and it pisses a lot of people off – so if you plan to use this script, run the following as root :

mkdir /tmp/wakeup
chmod 777 -R /tmp/wakeup
chown asterisk:asterisk -R /tmp/wakeup

You now have a hotel quality wake up module – just dial *62.

Enjoy!