Recently I tried to use the Gallery Multiroot module/plugin to setup a new site based upon an existing Album in our gallery. Since we started sorting albums chronologically, we wanted to sort out the Dachshund photos separately. To do this, I used the Multiroot feature. Unfortunately, I couldn’t get this to work as I’m already using the Multisite plugin to host several Galleries off of my web server. The magic touch was to use the following file, the first line is key and had to be added to make things work in the Multisite configuration.
define('GALLERY_CONFIG_DIR', "/var/virtualwww/gallery.raschnet.com"); //I had to add this line
require('/usr/local/share/gallery2/embed.php');
$ret = GalleryEmbed::init(
array('embedUri' => '/',
'g2Uri' => 'http://gallery.raschnet.com/',
'apiVersion' => array(1, 2)
));
if ($ret) {
print '<body>' . $ret->getAsHtml() . '</body>';
return;
}
$gallery->setConfig('login', true);
$gallery->setConfig('defaultAlbumId', 28426);
$gallery->setConfig('breadcrumbRootId', 28426);
GalleryMain();
Now live: DRNA Gallery
Related posts
Made some tweaks to the blog:
- using tags instead of categories
- google ads
- amazon wishlist
- I learned lots more about widgets
- integration with my delicious
Related posts
To run the class I posted yesterday, I typically use a class called DaemonRunner. This class sets up for proper signal handling, and ‘executes’ the class extended from Daemon.
declare(ticks=1);
class DaemonRunner {
public static function exec($className) {
$argv = $_SERVER['argv'];
$daemon = new $className($argv);
$daemon->init();
while (!$daemon->isDone()) {
$daemon->run();
}
$daemon->shutdown();
}
}
The first statement is a PHPism. This allows PHP to check for signals every 1 tick. A tick is simply a low-level PHP interpreter step. The way I’ve setup my daemon and signal handling by default, the PHP will finish its current iteration and then quit when receiving a signal. This ensures that the database, and whatever background stuff aren’t left in inconsistent states. As with anything, you’re free to modify, extend, or otherwise alter this behavior.
Related posts
PHP (or any language for that matter) can just as easily be used as a daemon as on the web. This can be especially useful when solving problems that can’t “complete” in less than 500 ms which one shoots for on the web. As you write an application to handle things such as those mentioned below, be sensitive to the processing, disk space, and time needed to process these requests in planning how to handle these. As an example jobs of a small size might be handled inline by the code that handles the form submission, but for larger jobs it queues them for background processing.
great for background/async processing of:
- photos
- movies
- reports
- imports of data
advantages:
- use the same codebase as your app
- use the same expertise on your team of programmers
challenges:
- signals
- one thread
- memory (this will have to be a whole separate article)
- starting and stopping
A typical Daemon class I use:
abstract class Daemon {
protected $done = false;
public function __construct($argv) {
}
public function init() {
pnctl_signal(SIGTERM, array($this, "onSignal"));
pnctl_signal(SIGINT, array($this, "onSignal"));
}
abstract public function run();
public function shutdown() {}
public function isDone() {
return $this->done;
}
public onSignal($signal){
switch ($signal) {
case SIGTERM:
case SIGINT:
$this->done = true;
break;
default:
// handle all other signals
}
}
}
As you can see, we’ve started to tackle some of the challenges here. The idea is to handle signals, specifically I usually care about SIGTERM (default when using ‘kill’ on *nix) and SIGINT (from pressing Ctrl-C). Both will cause the program to exit gracefully.
I’ll be posting the class I use to run Daemon’s tomorrow.
Related posts
