Will Turner CaptainOfFlyingDutchman

Download videos from egghead

Install the React Developer Tools Chrome Extension.
Go to the egghead website, i.e. Getting Started with Redux
Click View -> Developer -> Javascript Console, then the React tab, then the <NextUpLessonList ...> tag.
Click back to the Console tab, then run:

Every new version of Grails brings some enhancements, and challenges on developer side too. Starting Grails 2.3.x we used different approach to debug our application, and now we are again on same place with Grails 3.0.x.

As Grails is now using Spring Boot and Gradle, we have to hook into bootRun gradle task that gets added by Spring Boot Gradle plugin. You won't find this task anywhere in your build.gradle file but inside Gradle tool window of IntelliJ IDEA. To facilitate debugging again we just need to hook into this bootRun task as follows:

bootRun {
    addResources = false
    jvmArgs = ["-Xdebug", "-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"]
}

External configuration in Grails 3

Working on Grails 3 I realized that I no longer can specify external configuration using the standard grails.config.locations property in Config.groovy file.

Reason is obvious! There is no Config.groovy now in Grails 3. Instead we now use application.yml to configure the properties. However, you can't specify the external configuration using this file too!

What the hack?

Now Grails 3 uses Spring's property source concept. To enable external config file to work we need to do something extra now.

Upgrading a Grails app from version 1.3.7 to version 2.4.4

So, you want to upgrade your app to Grails 2.4.4 from that legacy 1.3.7 version today!

But wait! There are few challenges waiting for you in the process.

1. Start

Thinking, from where should we start upgrading, as it was quite a task for such

	set nocompatible " be iMproved, required
	filetype off " required

	" set the runtime path to include Vundle and initialize
	set rtp+=~/.vim/bundle/Vundle.vim
	call vundle#begin()
	" alternatively, pass a path where Vundle should install plugins
	"call vundle#begin('~/some/path/here')

	" let Vundle manage Vundle, required