BowerStudios.com

Flattery is like cologne -- to be smelled, but not swallowed.

From David Larochelle's blog

You can use:
COPY TABLE_NAME TO STDOUT WITH CSV HEADER
to push the output to a csv file.

There are multiple ways to do this. I was particularly interested in getting it to run without the additional "groovy " in the front. Silly, but it was interesting.

I found an interesting question on unix.stackexchange.com regarding how to specify the interpreter for a script which came in handy in case you are using gvm (sdktool).

The result
Create a file - myscript.groovy - with contents:

#! /usr/bin/env groovy
println "executing some groovy"

Make the file executable:
chmod +x myscript.groovy

Now we can run it:
./myscript.groovy

Really doesn't save us much from:
groovy myscript.groovy

But it IS possible. It is also documented at docs.groovy-lang.org

Apparently, the goal was to have a format that was readable AND writable by scripts. Makes sense.

You can still create an additional config for the app in grails-app/conf/application.groovy

Interesting Project for performing backups with Bash.

This can happen when going from an https secured site to an http site. The browser does not send the referrer to the server in this instance.

thatJeffSmith.com

First we need to find out what cluster we're working with:
$ pg_lsclusters
Result:
Ver Cluster Port Status Owner Data directory Log file
9.3 main 5432 online postgres /var/lib/postgresql/9.3/main /var/log/postgresql/postgresql-9.3-main.log
Now, reload it using the version and cluster name
$ sudo pg_ctlcluster 9.3 main reload

First Dog: "Hey, I got a great joke for you. Wanna hear it?"
Second Dog: "Sure!"
First Dog: "Knock, Kn--"
Second Dog: loses it

This one took me a bit to get, so I add the helpful video link :-) It is best seen written I think... and given to Dog owners. I'm not sure of its origin.

After releasing a new version of my Sanitizer plugin, I ran into the following error when trying to install the Sanitizer on another machine:

::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.grails.plugins#sanitizer;0.10.0: not found
::::::::::::::::::::::::::::::::::::::::::::::

Thanks to Tim's helpful answer on stackoverflow, I was able to see the artifacts were happily sitting in the Grails Plugin Repository. The plugin portal had been updated as well. However, I wasn't able to access them in Grails 2.2.4. Grails 2.3.11 was able to access them fine.

I'm still primarily using 2.2.4, so a bit more digging was in order.

Finally I stumbled on another stackoverflow post from Scott that mentioned that the url for the repo had changed.

Adding this to your repositories block in your BuildConfig.groovy will put you back in business:
mavenRepo "http://repo.grails.org/grails/repo/"