@see http://php.net/manual/en/function.bcdiv.php

ssh  -o ServerAliveInterval=30

wget --server-response --spider http://www.example.com

References

There are a number of methods for integrating Doctrine into a Zend Framework application. Many of the examples on the web detail how to configure and initialise Doctrine using your applications bootstrap however I prefer using resource plugins. The following describes how I get Doctrine up and running for a Zend Framework application using a resource plugin.

For this tutorial I’m going to assume you’ve already got a Zend Framework application up and running; if not see my previous write-up on creating one.

For this tutorial my project’s root directory is /srv/www/acme. Any time you see that directory please replace it with the path to your project’s root directory.

Step1: Download and Copy

cd ~/Downloads
wget http://www.doctrine-project.org/downloads/DoctrineORM-2.2.2-full.tar.gz
tar -zxvf DoctrineORM-2.2.2-full.tar.gz
cd /srv/www/acme/library
cp -R ~/Downloads/DoctrineORM-2.2.2/Doctrine ./

Step 2: Edit the application.ini configuration file
(application/configs/application.ini)

1) Add the following to the end of the [production] section:

Make sure to change the driver/user/pass/dbname options below to reflect your environment. Visit Doctrine’s site to learn more about which database drivers are available.

;doctrine's autoloader namespace
    autoloadernamespaces[] = "Doctrine"

;doctrine resource plugin configuration
    resources.doctrine.db.driver = "pdo_pgsql"
    resources.doctrine.db.host = "localhost"
    resources.doctrine.db.user = "postgres"
    resources.doctrine.db.password = "postgres"
    resources.doctrine.db.dbname = "acme_live"
    resources.doctrine.query.cache = "Doctrine\Common\Cache\ApcCache"
    resources.doctrine.metadata.cache = "Doctrine\Common\Cache\ApcCache"
    resources.doctrine.metadata.driver = "Doctrine\ORM\Mapping\Driver\AnnotationDriver"
    resources.doctrine.metadata.proxyDir = APPLICATION_PATH "/../data/proxies"
    resources.doctrine.metadata.entityDir[] = APPLICATION_PATH "/../library/App/Model/Entity"

;plugin prefixes/paths
    pluginPaths.App_Resource = "App/Resource"

2) Add the following to the end of the [development : production] section:

Note: This step is not required but is recommended. If you do not have (or aren’t going to create) a separate development database then skip this step

;doctrine resource plugin configuration
    resources.doctrine.db.dbname = "acme_devel"

Step 3:Create the plugin
(library/App/Resource/Doctrine.php)

class App_Resource_Doctrine extends Zend_Application_Resource_ResourceAbstract
{
    /**
     * @var DoctrineORMEntityManager
     */
    protected $em;

    public function init()
    {
        return $this->getEntityManager();
    }

    public function getEntityManager()
    {
        if (null === $this->em) {
            $options = $this->getOptions();
            $config = new \Doctrine\ORM\Configuration();
            $config->setProxyDir($options['metadata']['proxyDir']);
            $config->setProxyNamespace('Proxy');
            $config->setAutoGenerateProxyClasses((APPLICATION_ENV == 'development'));
            $driverImpl = $config->newDefaultAnnotationDriver($options['metadata']['entityDir']);
            $config->setMetadataDriverImpl($driverImpl);
            $cache = new \Doctrine\Common\Cache\ArrayCache();
            $config->setMetadataCacheImpl($cache);
            $config->setQueryCacheImpl($cache);

            $evm = new \Doctrine\Common\EventManager();
            $this->em = \Doctrine\ORM\EntityManager::create($options['db'],$config,$evm);
            Zend_Registry::set('doctrine', $this->em);
        }

        return $this->em;
    }
}

Step 4: Final steps
We’re almost done but there’s a few things our new plugin is going to expect that we haven’t taken care of yet.

1) Make sure APC is installed (click here for more information on installing APC)
Also look here for more information about Doctrine’s use of APC

2) Make sure that our proxy directory (see the resources.doctrine.metadata.proxyDir setting above) exists and it’s writeable by the webserver.

cd /srv/www/acme
mkdir -p data/proxies
chown www-data:www-data data/proxies

# The user/group my webserver (Apache) runs as is
# www-data, adjust as needed for your setup.

3) Create the directory where we’ll put our entites

cd /srv/www/acme
mkdir -p library/App/Model/Entity

… why the Model/Entity …. seems redundant? It’s a personal thing. I like to house all my “model” code in library/App/Model. As an example I’d eventually start dropping services into library/App/Model/Service and I’d put my repositories in library/App/Model/Repository. The structure has worked well for me on large projects so I’ve stuck with it.

Finished!
At this point you should now have a fully functional Doctrine Entity Manager that you can use anywhere

...
$em = Zend_Registry::get('doctrine');
...

Now all you have to do is figure out how to use it (I’ll post some examples in the near future). Until then I encourage you to start reading here.

References

Doctrine ORM Documentation

Zend Framework Resource Plugins

Zend Framework Application Setup

Environment

Ubuntu 10.10

PHP 5.3.3

Zend Framework 1.11.4

Doctrine ORM 2.0.3

Step 1: Download
http://framework.zend.com/download/latest

Step 2: Install
Follow the instructions in the “Create Your Project” section of Zend Framework’s Quick Start guide. Only follow the instructions to the “Checkpoint” (do not move on to the next step in the guide).
http://framework.zend.com/manual/en/learning.quickstart.create-project.html

Step 3: Create default module

zf create module default

Note: The exact command I used is:
~/Downloads/ZendFramework-1.11.4-minimal/bin/zf.sh create module default

Step 4: Edit the application.ini configuration file
(application/configs/application.ini)

1) Remove the following line:

resources.frontController.controllerDirectory = APPLICATION_PATH "/controllers"

2) Change the following line:

resources.frontController.params.prefixDefaultModule = "1"

-to-

resources.frontController.params.prefixDefaultModule = false

3) Add the following to the bottom of the [production] section:

resources.frontController.defaultmodule = "default"
resources.modules[] =

4) Under this line:

appnamespace = "Application"

…add these lines:

autoloadernamespaces[] = "Zend"
autoloadernamespaces[] = "App"

Step 5: Create our “App” directory
This is where I like to put all of my application’s library code/classes. If your going to use a different name for your application’s library code make sure to adjust the ‘autoloadernamespaces[] = “App”‘ line from the previous step.

mkdir library/App

Step 6: Copy Files and Clean up

Copy all the files in (application/views) to (application/modules/default/views) and clean up

cp -R application/views/* application/modules/default/views
rm -fr application/views

Copy all the files in (application/controllers) to (application/modules/default/controllers) and clean up

cp -R application/controllers/* application/modules/default/controllers
rm -fr application/controllers

Remove the leftover “models” folder

rm -fr application/models

Finished!
At this point you should be able to browse to your project and see the “Welcome to the Zend Framework!” welcome page.

Environment

Ubuntu 10.10
PHP 5.3.3
Zend Framework 1.11.4

References

Zend Framework Quick Start
Using a Conventional Modular Directory Structure

sudo add-apt-repository ppa:pmcenery/ppa
sudo apt-get update
sudo apt-get dist-upgrade

… I found this @ https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/652617/comments/14

2. Paste into the file:
Section "InputClass"
Identifier "Marble Mouse"
MatchProduct "Logitech USB Trackball"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "SendCoreEvents" "true"

EndSection

3. Reboot