madeupname / juggernaut Goto Github PK

Support for simple informational web pages (e.g., About, History, Mailing List).

Store page content in DB

• URL
  • support URLs like http://www.ocjug.org/?page=history
• Title
• Content
  • HTML
• Basic editing of above with those of Admin privileges

If it's easy, can use CKeditor: http://stefanogualdi.github.com/grails-ckeditor/docs/index.html

Meeting

• timestamp date
• startTime
• endTime
• String title
• String description
• String speaker
• Location location

Location

• name
• address
• city
• state
• zip

meeting:location is many:1

Add security to restrict content updates to an admin user. This will be accomplished via the Spring Security plugin. References:

Home: http://grails.org/plugin/spring-security-core
Manual: http://grails-plugins.github.com/grails-spring-security-core/docs/manual/
Tutorials: http://grails-plugins.github.com/grails-spring-security-core/docs/manual/guide/23%20Tutorials.html

To make things easier, we'll also use the spring-security-ui plugin, which provides some user management functions:

http://grails.org/plugin/spring-security-ui

Note the dependencies the above page lists, which you must manually install before installing the UI plugin.

Add Twitter Bootstrap to style site. Will be a customized version.

First attempt used a Twitter Bootstrap plugin, but there was a problem with customized/overridden Less files that import other Less files from a plugin directory. Now using the lesscss-resources plugin (http://grails.org/plugin/lesscss-resources) and have copied all relevant Bootstrap files under web-app/twitter-bootstrap.

Update the Meeting class, controller, and views to support generating iCalendar files. There is an iCalendar plugin for this.

Add CRUD screens for Meeting (issue #1). Will require option menus for start/ stop times, so scaffolding won't work. Also gives us a chance to get experience with Grails basics.

Basic page with links to the pages managing meetings, locations, etc.

Update config to use Postgresql instead of the in-memory DB. I've installed PG 9.1.

BuildConfig.groovy - add dependency:

runtime 'postgresql:postgresql:9.1-901.jdbc4'

User.groovy - specify table name as "person" as user seems to be a reserved word for Postgresql
Config.groovy - specify external config file for DB properties:

file:${userHome}/.grails/${appName}-config.groovy

Expect we'll need to change this or add locations when we deploy to cloud providers.

juggernaut-config.groovy example:

dataSource {
    driverClassName = "org.postgresql.Driver"
    username = "juggernaut"
    password = "password"
    dialect = "org.hibernate.dialect.PostgreSQLDialect"
}

environments {
    development {
        dataSource {
            dbCreate = "create-drop" // one of 'create', 'create-drop', 'update', 'validate', ''
            url = "jdbc:postgresql://localhost:5432/juggernaut-dev"
        }
    }
    test {
        dataSource {
            dbCreate = "update"
            url = "jdbc:postgresql://localhost:5432/juggernaut"
        }
    }
}

This overrides other config properties. Of course, being external to the source tree (and having DB credentials), this never gets checked in.