Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ryanj/sudobot
a snarky configuration of scorebot, made for #sudoroom IRC
https://github.com/ryanj/sudobot
Last synced: 13 days ago
JSON representation
a snarky configuration of scorebot, made for #sudoroom IRC
- Host: GitHub
- URL: https://github.com/ryanj/sudobot
- Owner: ryanj
- Created: 2012-12-12T20:29:35.000Z (almost 12 years ago)
- Default Branch: master
- Last Pushed: 2012-12-13T02:34:31.000Z (almost 12 years ago)
- Last Synced: 2024-10-11T00:12:05.613Z (about 1 month ago)
- Language: Shell
- Size: 133 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Running a custom/latest Node[.js] version on Red Hat's OpenShift PaaS
====================================================================
This git repository is a sample Node application along with the
"orchestration" bits to help you run the latest or a custom version
of Node on Red Hat's OpenShift PaaS.Selecting a Node version to install/use
---------------------------------------To select the version of Node.js that you want to run, just edit or add
a version to the .openshift/markers/NODEJS_VERSION file.Example: To install Node.js version 0.9.1, you can run:
$ echo -e "0.9.1\n" >> .openshift/markers/NODEJS_VERSIONThe action_hooks in this application will use that NODEJS_VERSION marker
file to download and extract that Node version if it is available on
nodejs.org and will automatically set the paths up to use the node/npm
binaries from that install directory.See: .openshift/action_hooks/ for more details.
Note: The last non-blank line in the .openshift/markers/NODEJS_VERSION
file.determines the version it will install.Steps to get a custom Node.js version running on OpenShift
----------------------------------------------------------Create an account at http://openshift.redhat.com/
Create a namespace, if you haven't already do so
rhc domain create
Create a nodejs-0.6 application (you can name it anything via -a)
rhc app create -a palinode -t nodejs-0.6
Add this `github nodejs-custom-version-openshift` repository
cd palinode
git remote add upstream -m master [email protected]:ramr/nodejs-custom-version-openshift.git
git pull -s recursive -X theirs upstream masterOptionally, specify the custom version of Node.js you want to run with
(Default is v0.8.9).
If you want to more later version of Node (example v0.9.1), you can change
to that by just writing it to the end of the NODEJS_VERSION file and
committing that change.echo "0.9.1" >> .openshift/markers/NODEJS_VERSION
git commit . -m 'use Node version 0.9.1'Then push the repo to OpenShift
git push
That's it, you can now checkout your application at:
http://palinode-$yournamespace.rhcloud.com
( See env @ http://palinode-$yournamespace.rhcloud.com/env )Feel free to change or remove this file, it is informational only.
Repo layout
===========
node_modules/ - Any Node modules packaged with the app
deplist.txt - Deprecated.
package.json - npm package descriptor.
.openshift/ - Location for openshift specific files
.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 restartedNotes about layout
==================
Please leave the node_modules and .openshift 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 the OpenShift
data directory, which will persist between pushes of your repo.
The OpenShift data directory is accessible relative to the remote repo
directory (../data) or via an environment variable OPENSHIFT_DATA_DIR.Environment Variables
=====================
OpenShift provides several environment variables to reference for ease
of use. The following list are some common variables but far from exhaustive:
process.env.OPENSHIFT_GEAR_NAME - Application name
process.env.OPENSHIFT_GEAR_DIR - Application dir
process.env.OPENSHIFT_DATA_DIR - For persistent storage (between pushes)
process.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:
process.env.OPENSHIFT_DB_HOST - DB Host
process.env.OPENSHIFT_DB_PORT - DB Port
process.env.OPENSHIFT_DB_USERNAME - DB Username
process.env.OPENSHIFT_DB_PASSWORD - DB PasswordWhen embedding a NoSQL database using 'rhc app cartridge add', you can reference environment
variables for username, host and password:
process.env.OPENSHIFT_NOSQL_DB_HOST - NoSQL DB Host
process.env.OPENSHIFT_NOSQL_DB_PORT - NoSQL DB Port
process.env.OPENSHIFT_NOSQL_DB_USERNAME - NoSQL DB Username
process.env.OPENSHIFT_NOSQL_DB_PASSWORD - NoSQL DB PasswordTo 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 node modules to install, line by line on the server. This will happen
when the user does a git push.Additional information
======================
Link to additional information will be here, when we have it :)