Initial version to allow a user to run a custom version of Node.js on

OpenShift. The user can easily switch between Node versions(e.g. 0.8.9 to
0.9.1) by just editing the .openshift/markers/NODEJS_VERSION file.

Author: ramr

.openshift/action_hooks/build

@@ -0,0 +1,32 @@
+#!/bin/bash
+# This is a simple build script and will be executed on your CI system if
+# available.  Otherwise it will execute while your application is stopped
+# before the deploy step.  This script gets executed directly, so it
+# could be python, php, ruby, etc.
+
+
+#  Source utility functions.
+source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+#  Setup path to include the custom Node[.js] version.
+_SHOW_SETUP_PATH_MESSAGES="true" setup_path_for_custom_node_version
+
+
+#  So we we moved the package.json file out of the way in pre_build,
+#  so that the OpenShift git post-receive hook doesn't try and use the
+#  old npm version to install the dependencies. Move it back in.
+tmp_package_json="$(get_node_tmp_dir)/package.json"
+if [ -f "$tmp_package_json" ]; then
+   #  Only overlay it if there is no current package.json file.
+   [ -f "${OPENSHIFT_REPO_DIR}/package.json" ]  ||    \
+      mv "$tmp_package_json" "${OPENSHIFT_REPO_DIR}/package.json"
+fi
+
+
+#  Do npm install with the new npm binary.
+if [ -f "${OPENSHIFT_REPO_DIR}"/package.json ]; then
+   echo "  - Installing dependencies w/ new version of npm ... "
+   echo
+   (cd "${OPENSHIFT_REPO_DIR}"; export TMPDIR="/tmp"; npm install -d)
+fi
+

.openshift/action_hooks/deploy

@@ -0,0 +1,16 @@
+#!/bin/bash
+# This deploy hook gets executed after dependencies are resolved and the
+# build hook has been run but before the application has been started back
+# up again.  This script gets executed directly, so it could be python, php,
+# ruby, etc.
+
+
+#  Source utility functions.
+source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+
+#  On slave/serving gears, need to do the install as part of deploy
+#  so check if its needed. Just ensure the custom Node[.js] version is
+#  installed.
+ensure_node_is_installed
+

.openshift/action_hooks/post_deploy

@@ -0,0 +1,4 @@
+#!/bin/bash
+# This is a simple post deploy hook executed after your application
+# is deployed and started.  This script gets executed directly, so
+# it could be python, php, ruby, etc.

.openshift/action_hooks/post_start_nodejs-0.6

@@ -0,0 +1,41 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.
+
+#  Source utility functions.
+source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+#  Get the node version.
+ver=$(get_node_version)
+
+
+#  Set URI to the custom sample /env route.
+app_uri="http://$OPENSHIFT_GEAR_DNS/env"
+
+#  Wait a bit to give the server time to come up.
+sleep 5
+
+#  Check if the app_uri is available - user code could have removed the
+#  one in the sample -- we just print this for sanity testing.
+zcode=$(curl --write-out %{http_code} -s -o /dev/null "$app_uri")
+
+if [ "$zcode" -eq 200 ]; then
+   echo ""
+   echo "  - Using Node.js version $ver, checking app URI ... "
+   echo "  - test URI = $app_uri"
+   echo "  - Version from test URI = $(curl -s $app_uri | grep 'Version')"
+   echo ""
+fi
+
+

.openshift/action_hooks/post_stop_nodejs-0.6

@@ -0,0 +1,14 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.

.openshift/action_hooks/pre_build

@@ -0,0 +1,21 @@
+#!/bin/bash
+# This is a simple script and will be executed on your CI system if
+# available.  Otherwise it will execute while your application is stopped
+# before the build step.  This script gets executed directly, so it
+# could be python, php, ruby, etc.
+
+
+#  Source utility functions.
+source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+#  Ensure custom node version if not installed.
+echo ""
+ensure_node_is_installed
+
+
+#  We need to move the package.json file out of the way in pre_build, so
+#  that the OpenShift git post-receive hook doesn't try and use the old
+#  npm version to install the dependencies.
+mv  "${OPENSHIFT_REPO_DIR}/package.json"  "$(get_node_tmp_dir)"
+
+

.openshift/action_hooks/pre_start_nodejs-0.6

@@ -0,0 +1,25 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.
+
+
+#  Source utility functions.
+source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+#  Setup path to include the custom Node[.js] version.
+ver=$(get_node_version)
+echo ""
+echo "  - pre_start_nodejs: Adding Node.js version $ver binaries to path"
+_SHOW_SETUP_PATH_MESSAGES="true" setup_path_for_custom_node_version
+

.openshift/action_hooks/pre_stop_nodejs-0.6

@@ -0,0 +1,29 @@
+#!/bin/bash
+
+# The pre_start_cartridge and pre_stop_cartridge hooks are *SOURCED*
+# immediately before (re)starting or stopping the specified cartridge.
+# They are able to make any desired environment variable changes as
+# well as other adjustments to the application environment.
+
+# The post_start_cartridge and post_stop_cartridge hooks are executed
+# immediately after (re)starting or stopping the specified cartridge.
+
+# Exercise caution when adding commands to these hooks.  They can
+# prevent your application from stopping cleanly or starting at all.
+# Application start and stop is subject to different timeouts
+# throughout the system.
+
+
+#  First time in .openshift/lib/utils might not exist, so add a check
+#  to ensure file exists.
+if [ -f "$OPENSHIFT_REPO_DIR/.openshift/lib/utils" ]; then
+   #  Source utility functions.
+   source "$OPENSHIFT_REPO_DIR/.openshift/lib/utils"
+
+   #  Setup path to include the custom Node[.js] version.
+   ver=$(get_node_version)
+   echo ""
+   echo "  - pre_stop_nodejs: Adding Node.js version $ver binaries to path"
+   _SHOW_SETUP_PATH_MESSAGES="true" setup_path_for_custom_node_version
+fi
+

.openshift/cron/README.cron

@@ -0,0 +1,22 @@
+Run scripts or jobs on a periodic basis
+=======================================
+Any scripts or jobs added to the minutely, hourly, daily, weekly or monthly
+directories will be run on a scheduled basis (frequency is as indicated by the
+name of the directory) using run-parts.
+
+run-parts ignores any files that are hidden or dotfiles (.*) or backup
+files (*~ or *,)  or named *.{rpmsave,rpmorig,rpmnew,swp,cfsaved}
+
+The presence of two specially named files jobs.deny and jobs.allow controls
+how run-parts executes your scripts/jobs.
+   jobs.deny  ===> Prevents specific scripts or jobs from being executed.
+   jobs.allow ===> Only execute the named scripts or jobs (all other/non-named
+                   scripts that exist in this directory are ignored).
+
+The principles of jobs.deny and jobs.allow are the same as those of cron.deny
+and cron.allow and are described in detail at: 
+   http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-Automating_System_Tasks.html#s2-autotasks-cron-access
+
+See: man crontab or above link for more details and see the the weekly/
+     directory for an example.
+

.openshift/cron/daily/.gitignore

@@ -0,0 +1,16 @@
+Run scripts or jobs on a weekly basis
+=====================================
+Any scripts or jobs added to this directory will be run on a scheduled basis
+(weekly) using run-parts.
+
+run-parts ignores any files that are hidden or dotfiles (.*) or backup
+files (*~ or *,)  or named *.{rpmsave,rpmorig,rpmnew,swp,cfsaved} and handles
+the files named jobs.deny and jobs.allow specially.
+
+In this specific example, the chronograph script is the only script or job file
+executed on a weekly basis (due to white-listing it in jobs.allow). And the
+README and chrono.dat file are ignored either as a result of being black-listed
+in jobs.deny or because they are NOT white-listed in the jobs.allow file.
+
+For more details, please see ../README.cron file.
+

.openshift/cron/hourly/.gitignore

@@ -0,0 +1 @@
+Time And Relative D...n In Execution (Open)Shift!

.openshift/cron/minutely/.gitignore

@@ -0,0 +1,3 @@
+#!/bin/bash
+
+echo "`date`: `cat $(dirname \"$0\")/chrono.dat`"

.openshift/cron/monthly/.gitignore

@@ -0,0 +1,12 @@
+#
+#  Script or job files listed in here (one entry per line) will be
+#  executed on a weekly-basis.
+#
+#  Example: The chronograph script will be executed weekly but the README 
+#           and chrono.dat files in this directory will be ignored.
+#
+#           The README file is actually ignored due to the entry in the
+#           jobs.deny which is checked before jobs.allow (this file).
+#
+chronograph
+

.openshift/cron/weekly/README

@@ -0,0 +1,7 @@
+#
+#  Any script or job files listed in here (one entry per line) will NOT be
+#  executed (read as ignored by run-parts).
+#
+
+README
+

.openshift/cron/weekly/chrono.dat

@@ -0,0 +1,40 @@
+#  Utility functions for bash session - sourced in via the user's
+#  bash profile ($OPENSHIFT_DATA_DIR/.bash_profile).
+
+#  Source utility functions.
+source $OPENSHIFT_REPO_DIR/.openshift/lib/utils
+
+
+#  Internal function to setup path and remove the wrappers.
+function _setup_path_and_remove_wrappers() {
+   #  First invocation of npm or node, so setup the custom path and
+   #  unset the wrappers. Add the custom node binaries to the PATH.
+   [ -z "$ZDEBUG" ]  ||  echo "Setting path to include custom Node version"
+   setup_path_for_custom_node_version
+   unset node
+   unset npm
+   unset _setup_path_and_remove_wrappers
+
+}  #  End of function  _setup_path_and_remove_wrappers.
+
+
+#  Temporary wrapper function to setup path before invoking npm.
+function npm() {
+   #  Setup path, remove wrappers and reinvoke npm.
+   _setup_path_and_remove_wrappers
+   npm "$@"
+
+}  #  End of function  npm.
+
+
+#  Temporary wrapper function to setup path before invoking node.
+function node() {
+   #  Setup path, remove wrappers and reinvoke node.
+   _setup_path_and_remove_wrappers
+   node "$@"
+
+}  #  End of function  node.
+
+
+#
+# EOF