Skip to main content

php5-cli Installation on Debian 3.1

Major turmoil was caused while installing php5-cli package on our staging server. This is the pre-installation confirmation.
xxxx@hhhhh:~$ sudo apt-get install php5-cli
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
ca-certificates libapache2-mod-php5 libc6 libcurl3 libdb4.4 libidn11 libkrb53 libncurses5 libreadline5 libssl0.9.8 libxml2 locales
php5-common php5-curl php5-mysql readline-common tzdata
Suggested packages:
php-pear glibc-doc libcurl3-gssapi libldap2-dev krb5-doc krb5-user
Recommended packages:
libgpmg1 xml-core
The following packages will be REMOVED:
base-config initrd-tools kernel-image-2.4.27-2-386 ssh-krb5
The following NEW packages will be installed:
ca-certificates libdb4.4 libssl0.9.8 php5-cli readline-common tzdata
The following packages will be upgraded:
libapache2-mod-php5 libc6 libcurl3 libidn11 libkrb53 libncurses5 libreadline5 libxml2 locales php5-common php5-curl php5-mysql
12 upgraded, 6 newly installed, 4 to remove and 151 not upgraded.
Need to get 19.7MB of archives.
After unpacking 18.6MB disk space will be freed.
Do you want to continue? [Y/n]
Can't exactly remember how I managed to fix the break-ups, or even specifically what the problem(s) were, but I'll try to prepare for surprises on production machine.

After a few hours of deliberation, I decided to not install php5-cli on my Debian 3.1 and work-around.

Work Around

The work-around is to create the PDF's on my staging server by a remote SSH call from production server, let the PDF's be generated on STAG, and SCP them back to PROD. Wrote a tiny script with necessary commands, so this could pretty much be set & forget.

The only major glitch is that the STAG database is not up to date with the latest catalog/product information. So if new products are added to PROD or product descriptions changed, there is no automatic process in the work-flow which updates STAG, and hence ensures that PDFs generated are up to date.

I'm looking into setting up STAG as a MySQL replication slave to the PROD server and if there are not too many changes required on PROD itself, I'll probably end up implementing this for ensuring fresh data on STAG.

This setup might have to be reworked if we upgrade to Debian 4.0, but I think that won't be the case until we have a system wide upgrade to Network 3.0 (probably late 2008, considering we are still in process of implementing Network 2.0)