$block = block_load(<code>$module, $delta</code>);
print render(_block_get_renderable_array( _block_render_blocks( array($block) )));

where:

$module Name of the module that implements the block to load.

$delta Unique ID of the block within the context of $module. Pass NULL to return an empty block object for $module.

Reference links:

• block_load API
• Drupal.org comment

$ php -v
PHP 5.2.11 (cli) (built: Dec 12 2009 13:19:08)

$ cd ~ && tar zxvf php-5.2.11.tar.gz && cd php-5.2.11

#ifdef HAVE_LIBICONV
#define iconv iconv
#endif

#ifdef HAVE_CONFIG_H
#include "config.h"
#endif

#include "tidy.h"
#include "php.h"
#include "php_tidy.h"

#if HAVE_TIDY

#include "php_ini.h"

$ MACOSX_DEPLOYMENT_TARGET=10.6
$ CFLAGS="-arch i386 -arch x86_64 -g -Os -pipe -no-cpp-precomp"
$ CCFLAGS="-arch i386 -arch x86_64 -g -Os -pipe"CXXFLAGS="-arch i386 -arch x86_64 -g -Os -pipe"
$ LDFLAGS="-arch i386 -arch x86_64 -bind_at_load"
$ export CFLAGS CXXFLAGS LDFLAGS CCFLAGS MACOSX_DEPLOYMENT_TARGET

$ LIBS=-lresolv ./configure --with-tidy=shared && make

$ cp ./modules/tidy.so /Applications/MAMP/bin/php5/lib/php/extensions/no-debug-non-zts-20060613/

extension=tidy.so

Check with php_info() if the tidy extension is loaded correctly

Reference Links:

• Installing PHP 5.2.10 on OS X 10.6 Snow Leopard
• How to compile PHP with ‘–enable-zip’ on Mac OS-X SnowLeopard (10.6)
• http://forum.mamp.info/viewtopic.php?f=4&t=6569

• JDK 1.5 or 1.6
• Installer Jboss eap 4.3 or higher

Installation

Create jboss user


~# adduser jboss && passwd jboss


Update ~/.bashrc


#JAVA Settings
export JAVA_HOME=/usr/java/latest
export PATH=$JAVA_HOME/bin:$PATH

#JBOSS Settings
export JBOSS_HOME=/home/jboss/EnterprisePlatform-4.3.0.GA_CP07/jboss-as
export JAVAPTH=$JAVA_HOME/bin
export JBOSS_CONF=default
export JBOSS_HOST="0.0.0.0"


Install JBoss eap


~$ java -jar enterprise-installer-4.3.0.GA_CP07.jar

Follow the graphic installer and complete the installation.

Set up as service

As root:

ln -s /home/jboss/EnterprisePlatform-4.3.0.GA_CP07/jboss-as/bin/jboss_init_redhat.sh jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc3.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc5.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc4.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc6.d/K15jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc0.d/K15jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc1.d/K15jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc2.d/K15jboss


Edit the $JBOSS_HOME/bin/jboss_init_redhat.sh to allow loading the user profile:

#Add this line before any script content
. /home/jboss/.bashrc


Test

As root:

~# service jboss start


Now JBoss should be available at:

http://YOUR_ADDRESS:8080

An older version of Ortro (updated to the latest version right in these days) was already used in such departments of Telecom Italia as an experimental software for application monitoring.

But in the last time I had a confirm Ortro is, as I like to define it, mainly a “Framework” helping you to solve the daily problems encountered in monitoring and job activities.

Some months ago some people in Telecom Italia asked me if Ortro could be used as a valid alternative to a commercial product specialized in secure file transfer activity.

So I‘ve realized a proof of concept keeping in mind the 80-20 rule and after a second phase of security, performance and functional tests Ortro was result to be a valid choice to replace the commercial product.

At writing time some real pilot projects was identified for an “on the job” final test.

The results of these activities are the actual version of Ortro (1.3.4) and the advanced file transfer plugin.

Following these positive results Telecom Italia asked me to verify if Ortro could be also used as an alternative to some commercial enterprise scheduler software Telecom is using.

So another challenge is started…

Stay tuned… the 1.4 is around the corner

Help and comments are always welcome, see http://www.ortro.net for full changelog and details.

Ortro 1.3.4 and the plugins may be downloaded as usual from:
http://www.ortro.net/download

Well, if this is your scenario, let’s go to configure Nginx.

Requirements
- Nginx up, running and listening on 80 port
- A web server, like Apache, listening on 8080 port

server {
listen       80;
server_name  www.example.com;

access_log  /var/log/nginx/host.access.log  main;
set $prefix  prefix_;

# proxy module defaults
proxy_store_access   user:rw  group:rw  all:r;
proxy_set_header  X-Real-IP  $remote_addr;
proxy_set_header  Host       $host;

# Main location
location / {

root /tmp/nginx/;
index index.html index.htm index.php index.php.html index.php.html;

# Use this if you don't cache a context (dont_cache_path) , send all requests through the proxy
location ~ ^/dont_cache_path {
  proxy_pass http://localhost:8080;
}

# if the request uri was a directory, store the index page name
if ($request_uri ~ /$) {
  set $store_extra ${request_uri}index;
}

# set the location the proxy will store the data to. Add the index page
# name if the uri was a directory (nginx can't normally store these)
proxy_store /tmp/nginx/${prefix}${query_string}${store_extra}.html;

# go through the proxy if there is no cache
if (!-f /tmp/nginx/${prefix}${query_string}${store_extra}.html) {
  proxy_pass http://localhost:8080;
}

# workaround. headers module doesn't take into account proxy response
# headers. It overwrites the proxy Cache-Control header, causing
# private/no-cache/no-store to be wiped, so only set if not using proxy
if (-f /tmp/nginx/${request_uri}${store_extra}.html) {
  expires 0;
}

# handle static files directly. Set their expiry time to max, so they'll
# always use the browser cache after first request
location ~* (css|js|png|jpe?g|gif|ico|swf)$ {
  root /var/www/html/;
  expires max;
}
error_page 404 = /${prefix}${query_string}${store_extra}.html;
}
}

Restart Nginx and enjoy with your static web site

Reference Links:
- Nginx wiki
- how to use nginx to create static files from dynamic content
- Page-level caching with Nginx

This release add the capability to use compression during transfer and enable the recursive copy of files and folders.
Download and enjoy

This release add the capability to filter the copy using whitelist or blacklist based on the host:path string and the saving of transfer time.
Download and enjoy

Let’s go to create the class implements the Zend_Auth_Adapter_Interface starting from the Zend_Auth_Adapter_Ldap class.

My_Zend_Auth_Adapter_PearAuth

class My_Zend_Auth_Adapter_PearAuth implements Zend_Auth_Adapter_Interface
{

/**
* The array of arrays of Pear::Auth options passed to the constructor.
*
* @var array
*/
protected $_options = null;

/**
* The username of the account being authenticated.
*
* @var string
*/
protected $_username = null;

/**
* The password of the account being authenticated.
*
* @var string
*/
protected $_password = null;

/**
* The Pear::Auth container.
*
* @var string
*/
protected $_container = null;

protected $_logger = null;

/**
* Constructor
*
* @param  string $container The Pear::Auth container to use
* @param  array  $options  An array of arrays of Pear::Auth options
* @param  string $username The username of the account being authenticated
* @param  string $password The password of the account being authenticated
* @return void
*/
public function __construct($container, array $options = array(), $username = null, $password = null)
{
$this->setOptions($options);
if ($username !== null) {
$this->setUsername($username);
}
if ($password !== null) {
$this->setPassword($password);
}
$this->_container = $container;
}

public function setLogger($logger)
{
$this->_logger = $logger;
}

/**
* Returns the array of arrays of Pear::Auth options.
*
* @return array|null
*/
public function getOptions()
{
return $this->_options;
}

/**
* Sets the array of arrays of Pear::Auth options to be used by
* this adapter.
*
* @param  array $options The array of arrays of of Pear::Auth options
* @return My_Zend_Auth_Adapter_PearAuth Provides a fluent interface
*/
public function setOptions($options)
{
$this->_options = is_array($options) ? $options : array();
return $this;
}

/**
* Returns the username of the account being authenticated, or
* NULL if none is set.
*
* @return string|null
*/
public function getUsername()
{
return $this->_username;
}

/**
* Sets the username for binding
*
* @param  string $username The username for binding
* @return My_Zend_Auth_Adapter_PearAuth Provides a fluent interface
*/
public function setUsername($username)
{
$this->_username = (string) $username;
return $this;
}

/**
* Returns the password of the account being authenticated, or
* NULL if none is set.
*
* @return string|null
*/
public function getPassword()
{
return $this->_password;
}

/**
* Sets the password for the account
*
* @param  string $password The password of the account being authenticated
* @return My_Zend_Auth_Adapter_PearAuth Provides a fluent interface
*/
public function setPassword($password)
{
$this->_password = (string) $password;
return $this;
}

/**
* Authenticate the user
*
* @throws Zend_Auth_Adapter_Exception
* @return Zend_Auth_Result
*/
public function authenticate()
{
require_once 'Pear/Auth.php';

$messages = array();
$messages[0] = ''; // reserved
$messages[1] = ''; // reserved

$username = $this->_username;
$password = $this->_password;

if (!$username) {
$code = Zend_Auth_Result::FAILURE_IDENTITY_NOT_FOUND;
$messages[0] = 'A username is required';
return new Zend_Auth_Result($code, '', $messages);
}
if (!$password) {
/* A password is required because some servers will
* treat an empty password as an anonymous bind.
*/
$code = Zend_Auth_Result::FAILURE_CREDENTIAL_INVALID;
$messages[0] = 'A password is required';
return new Zend_Auth_Result($code, '', $messages);
}

//Override $_POST variables required by Auth pear package.
$_POST['username'] = $username;
$_POST['password'] = $password;

$_auth = new Auth($this->_container, $this->_options, '', false);

//Enable logging
if (isset ($this->_options['enableLogging']) && $this->_options['enableLogging'] &&
!is_null($this->_logger)) {
$_auth->logger = $this->_logger;
}

$_auth->start();

if ($_auth->getAuth()) {
//Destroy Pear::Auth session to avoid unespected behaviour
$_auth->logout();
$messages[] = "$username authentication successful";
return new Zend_Auth_Result(Zend_Auth_Result::SUCCESS, $username, $messages);
}

$messages[] = "$username authentication failed.";
return new Zend_Auth_Result(Zend_Auth_Result::FAILURE, $username, $messages);
}
}

and now let’s go to use it, for example in our controller

....
$auth = Zend_Auth::getInstance();
$config = new Zend_Config_Xml('APPLICATION_HOME/configs/auth_ldap.xml', 'production');
$options = $config->ldap->toArray();
$authAdapter = new Zend_Auth_Adapter_PearAuth('LDAP', $options, $username, $password);
$result = $auth->authenticate($authAdapter);
if(!is_null($result) && $result->isValid()) {
$authorized = true;
}
....

In the example above I’ve used the LDAP container but this should be valid for all supported containers by Pear::Auth.

Hope this helps