"Blog Setup" by Nick

Wed, 23 Jul 2008 20:20:59 +0000

ivar: we typically just include the db directory and rakefile in our war file and do these tasks on the server with a jruby installation. I haven’t really seen any best practices in this area yet. There’s been talk of having the application run its own migrations at application startup, but that seems a little dangerous...

"Blog Setup" by ivar

Wed, 23 Jul 2008 17:45:39 +0000

Having a simple recipe like this is very handy - thanks ! My next question is if you have a suggested method for handling migrations ? (or rake tasks in general)

"Blog Setup" by Song

Mon, 14 Jul 2008 07:39:44 +0000

Thanks for sharing. I am waiting for this.

"Blog Setup" by Ivan Vint

Thu, 10 Jul 2008 09:27:40 +0000

Thanks, will try to setup a test blog on my gentoo linux desktop this weekend.

"Blog Setup" by Alexander Mikhailian

Thu, 10 Jul 2008 08:37:14 +0000

As you mention using activerecord-jdbcmysql-adapter, may I point you to a recent bug at codehaus that I introduced asking not to force the utf8_bin collation in the driver.

As a next step and probably as a TODO for the 1.0 version of the ActiveRecord-JDBC, it would be nice to allow multiple encodings, and have utf-8 as a fallback enciding and not as the hard-wired rule.

This is probably more in line with the attitude of MRI 1.8.6 towards the encodings.

Blog Setup

Nick Sieger — Thu, 10 Jul 2008 05:10:27 +0000

The other day several people chimed in wondering how I set up this blog with JRuby and Glassfish. One of the reasons I didn’t include the details in the post is that it’s not really much different than any JRuby/Glassfish/Warbler deployment, but in case you don’t know what that looks like, here are the basics.

Preconditions (Java)

I’m running on a Joyent Accelerator, which runs OpenSolaris, which has JDK 6 installed by default. If you’re running on some flavor of Linux, hopefully there’s a package available for you to install, otherwise you may have to download a self-extracting binary.

Install Glassfish

This step is actually straightforward; not at all as problematic as you might expect of a piece of Java technology! In the parent directory where you want Glassfish to be installed (substituting the name of the Glassfish jar you downloaded as appropriate):

java -Xmx256m -jar glassfish-installer-v2ur2-b04-sunos_x86.jar
cd glassfish
chmod -R +x lib/ant/bin
./lib/ant/bin/ant -f setup.xml

Start Glassfish.

./bin/asadmin start-domain

You may want to add GLASSFISH/bin to your path so that you can run the Glassfish asadmin command from anywhere.

On Solaris, SMF is the subsystem that is used to ensure services are started at boot time (among other things). Glassfish works nicely with SMF. On other systems, there may be /etc/rc.d init scripts out there, or you can roll your own (asadmin start-domain and asadmin stop-domain).

Install JRuby

Download JRuby and unpack it somewhere. I recommend adding JRUBY_HOME/bin to the end of your path, so it doesn’t clash with Matz-Ruby.

Install Warbler and activerecord-jdbcmysql-adapter

In addition to Warbler, I’m using the activerecord-jdbcmysql-adapter to connect to the blog’s database. Both can be installed with Rubygems:

jruby -S gem install warbler activerecord-jdbcmysql-adapter

With Rails 2 and up, the application’s config/database.yml file should be updated for adapter: jdbcmysql:

<% jdbc = defined?(JRUBY_VERSION) ? 'jdbc' : '' %>
development:
  adapter: <%= jdbc %>mysql
  encoding: utf8
  database: testapp_development
  username: root
  password:
  socket: /tmp/mysql.sock
# same for test/production...

Otherwise, you need to jump through some extra environment.rb configuration hoops.

Configure Warbler

Warbler needs to be told about any gems that your application uses. To generate a Warbler configuration file:

jruby -S warble config

The file is generated at config/warble.rb. In it, modify the following sections:

config.gems = ["activerecord-jdbcmysql-adapter"]
...
config.webxml.jruby.min.runtimes = 2
config.webxml.jruby.max.runtimes = 4

Build and deploy the .war

jruby -S warble
asadmin deploy --contextroot / blog.war

(--contextroot / makes the application rooted at / in the server, rather than at /blog which would be the default.)

At this point, the blog application is up and running on port 8080. I had previously been running the blog with an Apache/.htaccess-based setup reverse-proxying to mongrel, so all I had to do was change the port. I haven’t touched it since.

But is this right for you?

Chances are, this setup is overkill for a simple blog. If you’re going to try it, I’d recommend at minimum running on a VPS with at least 1G of memory. But once you get the core pieces in place, updating and re-deploying the application is really just as simple as the last two commands. It’s mundane and boring in its simplicity. But boring is good when you don’t want to worry about having to keep Mongrel running, or max out the memory in your server and make it unstable.

Nick Sieger: Blog Setup