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.

Groovy/Grails: How to disable a controller

Originally published .

(image removed, src was: https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiCG0Kg4cLXOi8v7CsxAfbFXd5nZV6o6Pp7JfwXHxN5ZWOwGGVKL4YDo6x5Sv46zsqm1EBOCs3OGJrhDBB44_nUYiq7OjY1UPOsJBqk7U-qCJGZ1Dvx_xegGAHQxXKNW1Gb1gHx3g/s400/Selection_012.png)

Let’s say you have a plugin. That plugin includes a controller. You don’t want to use the controller provided by the plugin (for whatever reason) but instead you want use your own controller.

What do you do?

Filters my friend. Filters.

Next to your Config.groovy file in the grails-app/conf directory create for your self a file called DisableFilters.groovy and then add a class definition. Here’s a filter definition that disables everything in the application… (making your grails application headless).


class DisableFilters {

def filters = {

all(controller:’’, action:’’) {

before = {

// return false

}

after = {

}

afterView = {

}

}

}

}

Now you’ll notice there is a before closure and it returns false. This closure fires before the request is passed to its destined controller/action. The *** means match all. So if you had a specific controller name or specific controller name pattern you wanted to disable you could easily disable all these by matching the name here.

Notice the nifty after which would execute after the controller and action complete. Finally you have the afterView closure which would execute after the entire call chain was done and the browser has left. I’ll leave the uses for these up to your imagination.

In the filter body you have access to everything you have in a grails controller so you have a great deal of flexibility here with what you can do. You could look at usernames, session data, whatever your heart desires. You can even redirect the request to another URL using the same conventions as you would have in a controller. So have at it!

Explore the map · Browse by topic and date