Thoughts on cartridge format

gistfile1.txt

cartridge
   github repo (c9v3 repo)
   	.openshift/
      bin/
      	control  <- scripts to start/stop etc.
      	setup    <- configuring container vs host
      	teardown
      env
      metadata/
      	manfest.yml *****
      	   <--  SHORT_CARTRIDGE_NAME
      	   <--  versioning info
      	   <--  scaling
      	   <--  dependencies  
      	   	nodejs/npm: 
      	   		Limitation) can't say we need nodejs here.  
      	   		Alternative 1) nodejs rpm, install script (setup above).  
      	   		    	    2) or rely on applcation choosing nodejs cartidge
      	   	node_modules:
      	   		Limitation) only have access to CBA approved artefacts
      	   		Alternatives)  
      	   			js dependencies, then we package as part of CI, commit them.

      	        tmux:
      	                Limitation) tmux install will download source, or run rpm
      	                Alternatives)
      	                          1) Assume a tmux cartridge already installed, 
      	                             would need to setup/symlink tmux path appropriate.


      	   <--  input variable
      	   <--  output variables
      	   <--  protocols
      	   			http(s)
      	   			ws
      	   <--  endpoints
      	   			1 PORT (8181)
      	   			PROXY_PORT


      /usr


on a gear

/opt/...../<SHORT-CARTRIDGE-NAME>/.....


/////

Example Application - 
/ 
	.Gemfile
		gem "rhc"
	.ruby-version
		1.9.3-p545

rhc create-app
rhc add-cartridge nodejs <or npm>...
rhc add-cartridge --from-code http://githib.com/..path to c9v3 fork.
rhc add-cartridge cba-scala
rhc add-cartridge cba-github-project 
	*specualtive> rhc <add-variable> internal-github project root as input variable to cba-github-project
	
Would need to make it easy to assemble this application - could be done from a shared snapshot...