BowerStudios.com

sqlmag.com

Git fetch and merge vs git pull

Shutterfly User Api

• SSH option from x11 forwarding
• More ssh tips

• How to send Wake on LAN packet
• Etherwake - send Wake on Lan packet

• Saiku - Lightweight OLAP solution - datawarehousing
• Usercake - A user management application
• Selfoss - self hosted rss reader in php - Using as a Google Reader replacement

As a former user of Pivotal Tracker (great product), the recent combined branding of Spring/Pivotal had me scratching my head.

This post explains it a bit.

This situation is if you are running grails in the console, and want to connect to it with your ide (eclipse, netbeans, intellij, etc)

You have two options for starting grails, either
grails-debug run-app

or the option from rlovtangen who uses a similar config, but allows the command line app to run and connect as needed with the debugger, instead of requiring a debugger connection before proceeding.

Then just connect as usual with your debugging env, example here

This took me a few tries to get right, so posting here to remember and clarify:

If you are creating objects that are not Grails "Artifacts" (controllers, services, etc) and you instantiate your log in the class like so:
private static final log = org.apache.commons.logging.LogFactory.getLog(this)

then in the log4j config section of the Config.groovy, you can set the log level like this:
info ('net.sf.ehcache.hibernate')

If you are using the injected "log" var in a Grails Artifact, you will access it like this:
'grails.app.services.com.bowerstudios.example.MyService'

Note the "grails.app.services" preceding the package.

Lifted from the Grails docs:
The standard artifact names used in the logging configuration are:
conf - For anything under grails-app/conf such as BootStrap.groovy (but excluding filters)
filters - For filters
taglib - For tag libraries
services - For service classes
controllers - For controllers
domain - For domain entities