Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead

Smallest-to-largest weight downloads. Qwen3.5 0.8B is our starting choice for page Q&A. GPU estimates are not total RAM: leave room for the browser, context and temporary buffers. Hardware changes speed and capacity; answers still need checking.

Session-only loading avoids saving model weights, uses extra RAM and downloads again after unloading. Turn it off to save downloads. Delete-data-on-exit or private browsing may impose a much smaller storage limit than the displayed estimate.

You sign in on OpenRouter; it gives this page a key for your account.

A free account does not make every model free. Choose a model with a listed :free variant; merely adding that suffix does not create one. Check free-model availability and pricing.

Chat

AI assistant, not Shawn Hartsock. It does not speak for him.

Inspect the page excerpt

Up to 4,800 characters, not the whole site. Recent conversation turns are retained within the model’s context limit.

Ask about this page, or just say hello.

Ready when you are.

Not saved or uploaded automatically. Closing keeps this conversation in this tab; changing pages starts a new one. Model replies can be wrong.

Multiple versions of Grails in Hudson

Originally published .

I have an interesting situation. I have a Hudson CI server that has to work with two different versions of Grails. I have a somewhat inelegant but functional solution.

First, Grails is set up in:

/usr/local/grails-versions/

each version of grails lives in here so that we have…

/usr/local/grails-versions/grails-0.6

/usr/local/grails-versions/grails-1.0

/usr/local/grails-versions/grails-1.0.1

/usr/local/grails-versions/grails-1.0.2

I create a symbolic link to the current version like so:

 $ ln -s /usr/local/grails-versions/grails-1.0.1 /usr/local/grails

now you can write your hudson jobs to run /usr/local/grails/bin/grails and if you upgrade simply move the symbolic link. Like so:

 $ rm /usr/local/grails && ln -s /usr/local/grails-versions/grails-1.0.2 /usr/local/grails

Next. Set up your hudson project to ping your SVN server or whatever specifics are needed in your environment to get the code to build. Be sure to name your project a single word … for example my_project. When you get to the “Build” section you are going to select the “Command” option.

For the sake of argument let’s say that you older Grails application is written in Grails 0.6. The command will look something like…


cd my_project &&

GRAILS_HOME="/usr/local/grails-versions/grails-0.6" &&

/usr/local/grails-versions/grails-0.6/bin/grails prod war &&

mv *.war /path/to/build/archive

… where I move my Hudson produced War files to an archive to get picked up by other programs later. You might choose to do something else.

The odd thing I noticed by experimentation is that it’s not enough to call on the right grails command… you have to also set the GRAILS_HOME for that command context. If you don’t do both then you won’t run the right version of Grails.

Explore the map · Browse by topic and date