BowerStudios.com

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/"

Thanks to sponsorship from Infinum, I made some changes to the Grails Sanitizer to simplify its internals and make it easier to maintain. It is using the latest version of OWASP's Antisamy Project

I published 3 versions with very minor differences to allow the plugin to work with different versions of Grails:
0.10.0 is for Grails 2.2.x
0.11.0 is for Grails 2.3.x
0.12.0 is for Grails 2.4.x

Source code and issue tracker are on Github

1. First, add the Postgres driver to Oracle Sql Developer:

   Tools > Preferences > Database > "Third Party JDBC Drivers" > Add Entry

   Navigate to a save location of the Postgresql JDBC driver from jdbc.postgresql.org

2. Next, In Oracle Sql Developer, crate a new connection. Give it a Connection Name, Username, HostName, and Port. Now Save.
3. Exit Sql Developer
4. Open ~/.sqldeveloper/system4.0.3.16.84/o.jdeveloper.db.connection.12.1.3.2.41.140908.1359/connections.xml
5. Update the customUrl for the connection you just created to something like:

   <StringRefAddr addrType="customUrl">
   <Contents>jdbc:postgresql://localhost:5432/mydatabasename?ssl=true</Contents>
   </StringRefAddr>

   Basically, we're adding the ?ssl=true parameter to the connection string.

I ended up resizing my extended partition with parted. Then I used fdisk to create a new logical partition.

Useful links:

• Joomlaworks.net
• turnkeylinux.org
• bowerstudios.com