Ensure Service has a Church

This code and test ensure that all Service models are connected to a
Church model.
Test all required relationships on models

These tests ensure that all required relationships in the models are
preserved.
Initial display of rides

This is a quick start to show the full list of rides available.  It
could be formatted more nicely and include more or less information,
but gets the general idea across.

Conflicts:
	app/views/layouts/application.html.erb
Test for Ride ordering

These tests check that the rides can be ordered by date or service
when listing them all.
Pass Ride ordering tests

These simple tests make sure that the previously committed tests pass
by adding the date to the Ride output and calling order on Ride with
the proper value.
Test for Service ordering

These tests ensure that the listing of services can be ordered by day
of week or starting time.
Require user email to match pattern

This provides a test and code to ensure that email addresses are more
like an address than simple text.  It is not robust, but makes them
more like an email address than previously.

Conflicts:
	app/models/user.rb
Fix user duplication tests.

The original tests could be passed if a uniqueness constraint was put
on the email address attribute instead of the name attribute.  These
modifications prevent that from being possible in the future.
Require 50 character names to be valid

If we don't add this test into the repository, then the maximum length
can be anything at all.  This simple test ensures 50 character user
names are acceptable, but 51 character user names are not.
Tests for displaying churches

These are simple tests to ensure that the full church list and
individual church listing exist and print minimal information out.
Initial commit.
Merge commit '619082'
Merge commit '626b2'

Conflicts:
	Gemfile
Merge commit 'aa5e3286eaa4312245c2cd9f422c8cdda6cec537'

Conflicts:
	Gemfile
	config/routes.rb
137 passing - first real commit...