PlayHymn3

A (very) simple service to stream hymns played by me

Changelog

• 10/22/2015 I have a blog now, where I'm blogging through the pieces of this project. Go there!
• 4/12/2015 finally got something through the pipeline!
• 3/25/2015 Added simple bootstrap to index.html
• 3/25/2015 Added second http connector to Tomcat to serve the html, so no more running two Tomcat instances! ^__^

History

I attend Trinity Reformed Church of Gaithersburg, an awesome new church plant in Maryland.

Our church utilizes the tradition of worshipping the Lord with hymns, older-style songs with rich theology.

Many of us, however, have not been sufficiently exposed to the style and nature of hymns, and it has been a struggle for us to collectively join together in song every Sunday.

As the church pianist, I am responsible for learning the songs and leading the worship.

I decided that it would be beneficial for our church to have a resource with which they can acquaint themselves to the songs a few days before each service, for the purpose of familiarizing themselves with their words and tunes.

This project is the manifestation of that desire.

Usage

build using maven

mvn package

to run,

java -jar -Dserver.port=9000 target/PlayHymn3-0.1.0.jar

Navigate to http://localhost:9000

About

Disclaimer: I'm just getting my feet wet with Spring and jQuery, and this is my first web project.

There's a Spring Boot example that shows how to build a RESTful resource that is pretty straightforward. It accepts GET requests and returns a JSON object.

There's also another one that shows how to host static content.

I figured it would be easy to bind the two examples together, throw in an SQL database for the back end to serve responses from, deploy on heroku, and voila!

I wasn't sure how to get heroku to allow me to use CORS. I am given a port to bind to from heroku's config vars, but I don't know how to reach the other end.

For the sake of finishing the project, I just bound the port to the back end. Unfortunately, only the back end will be RESTful; the front end will just be regular and plain-looking :/

Next try will involve a more mature framework like Ruby On Rails, possibly.

Todo

• Does GWT use CORS?
• setup spring "test" profile so that testing done with mock SQL server with CORS
• come up with better name
• can users submit feedback that can be easily submitted as a Git issue?
• add better description
• deploy on heroku
• host files on s3
• fix popState in jQuery (to make it REALLY RESTful)
• learn JPA or Hibernate or something else to tie hymn database
• query aforementioned db for hymn
• add audio to db
• switch db to postgres for easy use with heroku
• add to html
• add unit tests!!!
• reformat html for pagination, identified by week rather than hymn
• handle null cases and build proper http headers
• add links to previous week's hymns
• how to run this on heroku