Monthly Archives: August 2012

OpenLogic CloudSwing

OpenLogic CloudSwing is an open platform-as-a-service (PaaS) solution that enables developers and IT staff to easily deploy and operate applications in the cloud. Designed for the enterprise, CloudSwing acts as your central dashboard for applications across all of the public and private clouds you use.

BitNami Alfresco Cloud VM

BitNami Alfresco Cloud VM is a pre-configured, ready to run image for running Alfresco on Amazon EC2. Alfresco is an Enterprise Content Management (ECM) system featuring Document Management, Web Content Management, Collaboration Management, Records Management and Image Management.

VMware Player is no longer free-of-charge

With the release of VMware Player 5 VMware have made it no longer free-of-charge for office use only personal use. So you’ll have to switch to VirtualBox or be sure to download VMware Player 4 instead and do not upgrade it !

VMware Player 5 is now available for commercial use with support offerings as a component of VMware Fusion Professional.

openshift environment variables

you can find out your openshift mysql host, openshift mysql user and openshift mysql password by looking at your openshift environment variables

  • $ ssh myopenshiftuser@myopenshiftdomain
  • $ env | grep OPENSHIFT
more information on environment variables

OpenShift provides several environment variables to reference for ease of use.

The following list are some common variables but far from exhaustive:

$_ENV[‘OPENSHIFT_APP_NAME’] – Application name
$_ENV[‘OPENSHIFT_GEAR_DIR’] – Application dir
$_ENV[‘OPENSHIFT_DATA_DIR’] – For persistent storage (between pushes)
$_ENV[‘OPENSHIFT_TMP_DIR’] – Temp storage (unmodified files deleted after 10 days)

When embedding a database using ‘rhc app cartridge add’, you can reference environment variables for username, host and password:

$_ENV[‘OPENSHIFT_DB_HOST’] – DB host
$_ENV[‘OPENSHIFT_DB_PORT’] – DB Port
$_ENV[‘OPENSHIFT_DB_USERNAME’] – DB Username
$_ENV[‘OPENSHIFT_DB_PASSWORD’] – DB Password

and you can use these in your drupal, wikkawiki, wordpress config file as follows


/** The name of the database for your lamp app */
define('DB_NAME', $_ENV['OPENSHIFT_APP_NAME']);
/** MySQL database username */
define('DB_USER', $_ENV['OPENSHIFT_DB_USERNAME']);
/** MySQL database password */
define('DB_PASSWORD', $_ENV['OPENSHIFT_DB_PASSWORD']);
/** MySQL hostname */
define('DB_HOST', $_ENV['OPENSHIFT_DB_HOST']);

openshift repo layout

your actual php code can be found in ~/app-root/runtime/repo/php

more openshift repo layout info

Repo layout
===========
php/ – Externally exposed php code goes here
libs/ – Additional libraries
misc/ – For not-externally exposed php code
../data – For persistent data (full path in environment var: OPENSHIFT_DATA_DIR)
deplist.txt – list of pears to install
.openshift/action_hooks/pre_build – Script that gets run every git push before the build
.openshift/action_hooks/build – Script that gets run every git push as part of the build process (on the CI system if available)
.openshift/action_hooks/deploy – Script that gets run every git push after build but before the app is restarted
.openshift/action_hooks/post_deploy – Script that gets run every git push after the app is restarted
Notes about layout
==================
Please leave php, libs and data directories but feel free to create additional directories if needed.
Note: Every time you push, everything in your remote repo dir gets recreated please store long term items (like an sqlite database) in ../data which will persist between pushes of your repo.