Craft CMS on Openshift (alpha)
A hackity way to install and run Craft on Redhat's Openshift Paas.
It has been configured to run on the Zend Server Gear with the MySQL cartridge. This is still very much a work in progress. Use at your own risk
Installing Tips
Be sure to add the MySQL catridge to your gear running the craft install before initiating the install. If not, you may get errors stating craft is unable to use the provided database credentials to connect. This is possibly due to Zend cacheing the output of the installer script.
The img folder is a place to store your asset uploads. It is available internally with the path "img/" and externally with {{yourdomain}}.com/img/
How does it work?
I have placed a lightly-modified copy of Craft in the .openshift/ directory. The deploy shell script in the .openshift/action_hooks/ directory copies the craft folder into the persistent-data directory on first run.
(I do this because Craft has its own auto-update system that updates both itself and the mysql database.)
What has been modified in the Craft folder?
I have added the environmental variables for the MySQL cartridge (ip address, username, password, db name) to the db.php config file.
What does the Deploy script do?
As stated above, it checks to see if there is a craft directory in the persistent data directory. If not, it moves the copy from .openshift/ and creates a symbolic link to the php/ directory where it is accessible.
The templates folder is in php/ already, so the deploy script removes the copy in data/craft/ and replaces it with a symbolic link.
The script does a little more, so check out .openshift/action_hooks/deply to find out more.
This is still very much a work in progress. Use at your own risk
Original Openshift Readme
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.
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_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 cartridge add', you can reference environment variables for username, host and password:
$_ENV['OPENSHIFT_MYSQL_DB_HOST'] - DB host
$_ENV['OPENSHIFT_MYSQL_DB_PORT'] - DB Port
$_ENV['OPENSHIFT_MYSQL_DB_USERNAME'] - DB Username
$_ENV['OPENSHIFT_MYSQL_DB_PASSWORD'] - DB Password
To get a full list of environment variables, simply add a line in your .openshift/action_hooks/build script that says "export" and push.
deplist.txt
A list of pears to install, line by line on the server. This will happen when the user git pushes.
Additional information
To access the Zend Management console go to http://app-domain.rhcloud.com/ZendServer