Creating Long-Lived Web Apps with Ruby on Rails/

...

Use the Simplest Content Type We Can

Learn the content type we should be using in the APIs.

We'll cover the following...

Updated application

The HTTP Accept header allows for a wide variety of configurations for how a client can tell the API what sort of content type it wants back (the Content-Type header is for the server to specify what it’s sending). We can ignore it altogether and always serve JSON, or we could require the content type to be application/json, create our own custom content type for all our resources, or even make a content type for each resource. The possibilities and associated carrying costs are endless.

We would not recommend ignoring the Accept header. It’s not unreasonable to ...

Prologue

Getting Started

The Rails Application Architecture

Start Our App Off Right

Business Logic

Routes and URLs

HTML Templates

Helpers

CSS

Minimize JavaScript

Carefully Manage the JavaScript We Need

Testing the View

Models I

The Database

Build an E-learning Website with Ruby-on-Rails and PostgreSQL

Business Logic Code is a Seam

Models II

End-to-End Testing

Controllers

Jobs

Other Boundary Classes

Authentication and Authorization beyond Rails

Create a Bill Split Application Using Ruby on Rails

API Endpoints

Sustainable Process and Workflows

Operations

Conclusion

Appendices

Use the Simplest Content Type We Can