Developing OpenShift cartridges that need large binaries
When developing an OpenShift cartridge, what is the standard way to handle large binaries that it will need? Let's say a 100 MB file. Searching around the web I saw a couple cartridges that had their required binaries in the git repository, but I thought that was generally considered to be a bad idea from a git perspective.
You can either add it to your repo as you mentioned or host the file elsewhere and wget it part of your install scripts.
Fluentd on Openshift?
set-env PATH in Openshift
Updating NPM on OpenShift
How to pass variable when adding a cartridge?
OpenShift Online: Change gear size of existing scaled application
Why do OpenShift action hook scripts fail with strange errors?
Xorg on OpenShift
Putting private information on Public PaaS?
OPENSHIFT - 'wsgi.py' does not contain WSGI application 'application'
How do I install pdftk on Openshift?
Openshift hooks during gear restart
Openshift - Unable to set the env in JBoss as7 cartridges
How can I make a custom 503 page on OpenShift?
Openshift: Cron job fails to run
OpenShift Enterprise creating directories in root file system
Restoring a dokuwki to openshift