debug-ito / openshift-cartridge-plack

OpenShift cartridge for Perl applications based on Plack/PSGI

OpenShift cartridge for Plack/PSGI Perl applications

This is a Web application cartridge based on Plack/PSGI for OpenShift. PSGI is an interface specification for Web applications written in Perl, and Plack is a PSGI toolkit implementation.

The big difference from the perl cartridge (officially supported by OpenShift team) is that the Plack cartridge allows you to run any PSGI server while perl cartridge is limited to Apache HTTPD + mod_perl configuration.

How to Use

First, create your app with the stable release. (Do not use the master branch because it may be broken when I'm debugging something.)

$ rhc create-app -a YOUR_APP_NAME -t https://raw.github.com/debug-ito/openshift-cartridge-plack/release_0.1.0/metadata/manifest.yml

Because this installs some CPAN modules in the cloud, it takes some time. Please be patient.

After that, YOUR_APP_NAME directory is created. Then edit app.psgi in YOUR_APP_NAME directory, commit the change and git push it. The PSGI application is executed in the cloud.

See README.md created in YOUR_APP_NAME directory for further details.

Acknowledgement

• perl http://www.perl.org/
• Plack/PSGI http://plackperl.org/
• App::cpanminus https://metacpan.org/pod/App::cpanminus
• Daemon::Control https://metacpan.org/pod/Daemon::Control
• bin/setup script is inspired from heroku-buildpack-perl. https://github.com/miyagawa/heroku-buildpack-perl/blob/master/bin/compile

Author

• Toshio Ito - https://metacpan.org/author/TOSHIOITO

openshift-cartridge-plack's Issues

make the cartridge hot_deploy aware

Currently this cartridge does not support hot_deploy.

If the file .openshift/markers/hot_deploy exists under the app directory, OpenShift won't stop/start the cartridge, but this does not mean the changes are loaded by the running server.

Maybe we can support hot_deploy by doing some tricks in "build" and "deploy" event handlers in the bin/control script. But how?

Clean up .cpanm build files on "tidy" event

In .cpanm directory there will be a lot of downloaded module packages, consuming non-trivial disk space.

Since the module packages are no longer needed once they are installed, it should be cleaned up by "tidy" event.