2012/10/4 Max Rydahl Andersen <firstname.lastname@example.org>
Oh I was wondering why EAP wasn't supported.
Didn't realize the forge openshift install was jboss specific.
One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible.
i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools
added support for naming the remote used so you could align them.
If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned.
all of the above is available for use from the new openshift client.
>>> Pete and Lincoln talked about some of them in JavaOne here are some:
>>> * support for embedding cartridges
>>> * support for eap
>>> * tail files
whats this one ?
>>> I also got those:
>>> * setup when openshift application exists
>>> * snapshot management ?
>>> * key management ?
>>> * alias management
>>> * enable scaling on create app ?
>>> * Use alternate openshift config file
Define other config file than ~/.openshift/express.conf - Similar to --config option
>>> * config port forward ?we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ?