I don’t think Vert.x on OpenShift could be easier

verxIf you’re here, you already know how cool vert,x is, and you might be discovering how easy OpenShift makes your life.

Getting started with vert.x and OpenShift is so easy that this post isn’t even necessary, but I thought I’d point out some interesting features along the way.

First, create a new vert.x cartridge on OpenShift.


As of right now, OpenShift only supports vert.x 2.1, but it’s better than nothing. One thing I wonder about is how the autoscaling feature would work in terms of the vert.x event bus, the HA fail over stuff, or related scaling technology:


Second, clone the OpenShift repo on your local environment



That’s it. Now start coding

The cartridge comes out of the box with a server.js, which looks a lot like the starter examples on the vert.x site. I only really have two observations on it: First, I have issues with the team’s tab spacing (and js-lint would throw a fit). I’m only OCD about this one topic. However, I particularly like how the team thoughtfully added the ip and port variables and logic.

Because of this forethought, fresh off your git pull you can instantly see your verticle  simply by running vertx run server.js.


Cool, huh? Have fun out there.

Getting started with JBoss AS 7 and OpenShift — the absolute minimum

tweet-openshitStep one: First of all, do yourself a huge favor and take advantage of RedHat’s free giveaway for Getting Started With OpenShift.

openshift-getting-startThe O’Reilly edited free ebook doesn’t cover Java or JBoss or enterprise stuff specifically, but it’s generally written at just the right level to get you started as a developer. Honestly, I played around with Heroku and a few other PaaS services, and I struggled a little until I found OpenShift and the book. Do it!

Step two: sign up for an OpenShift account. You’re a developer, you’re smart enough to figure this one out.


Step three: download and install the OpenShift RHC Client tools so that you can interact with the OpenShift server through the command line. Are you assuming you’d rather work with GUI? I get it, but the command line tools are more powerful. Just take it on faith for now.

openshiftTo install the RHC Client Tools, you actually need to install Ruby first to get access to the gem package management service, but don’t worry too much about it; the process is pretty straight forward. The documentation explains it well, and it’s easy.

Step three: deploy a fresh JBoss AS 7 instance (cartridge on a fresh gear, in OpenShift lingo) in less than a minute by typing the following:

[code lang=”java”]
rhc create-app test jbossas-7

You’ll see something like this:


Nicely done. You’ve just deployed a JBoss AS 7 instance. Point your browser at the URL listed and you’ll see something line this.


Pretty amazing considering how much work used to go into setting up a new application server on the ‘net.

I’ll do some more posts to go into more detail later, but I hope this gives you the confidence to go forward. The OpenShift service is pretty amazing.