Add fully-filled out example entry to sample data.
Update Developer Portal copy and links to docs.
Enforce numericality of Phone extension field.
Use Unicorn instead of Passenger.

By default, it’s best to stick to the recommended Heroku server with
the recommended configuration.

https://devcenter.heroku.com/articles/rails-unicorn

https://devcenter.heroku.com/articles/concurrency-and-database-connectio
ns#multi-process-servers
Clarifies seed users roles

- Adds code comments to seeds.rb that says what the users are being set
up for.
- Adds links to line number in the readme to appropriate list of users.
Merge pull request #248 from codeforamerica/updates-seed-user-comments

Clarifies seed users roles
Add fields to Services table per v0.2 of HSDS.

Fields that have not been added because their purpose is questionable
or the data is already captured elsewhere:

- sms
- language_line
Add new service fields to admin interface.
Merge pull request #249 from codeforamerica/update-services

Update services
Update sample data.
Enumerize service status and make it required.

Possible values are `active`, `defunct`, and `inactive`. The default
value is `active`.
Expose alternate_name in search results.
Update root endpoint URLs.

Separate plural from singular URLs, add pagination parameters, and
update search parameters.
Merge pull request #251 from codeforamerica/update-root-endpoint

Update root endpoint URLs.
Optimize nearby endpoint.

The most common way the nearby endpoint would be used is to display
locations near the one currently being visited on a map. A client would
only need a few location attributes to make use of this endpoint, such
as the name, alternate name, latitude, longitude, address, and slug.

By creating a special serializer that only returns a few attributes, we
improve the performance of the nearby endpoint.
Merge pull request #252 from codeforamerica/update-nearby-serializer

Optimize nearby endpoint.
Remove slug check from category specs.

Slugs are not used for categories.
Add ability to filter locations by activity status

Now that the OpenReferral spec requires a `status` field for Services,
it’s possible that all of the Services for a particular Location could
become `inactive` and/or `defunct`.

If that’s the case, I would assume that you would no longer want to
include that Location in search results because you wouldn’t be calling
that location or visiting it if it no longer provides any services.

To enable this filter, I added a boolean `active` field to the
Locations table that automatically gets updated if the Location’s
overall Services status changes.

To only show active locations, pass in the `status=active` parameter.
For example:
https://ohana-api-demo.herokuapp.com/api/search?status=active

To only show inactive locations, pass in `status=inactive`.

For clients that display information about a particular Location, it
might make sense to display a warning or other message if the Location
currently doesn’t have any active services. You can determine if that’s
the case by checking if the Location’s JSON contains an `active`
attribute set to `false`.
Filter out inactive locations from nearby query.
Merge pull request #253 from codeforamerica/inactive-services

Add ability to filter locations by activity status