If you want to silent some of the services, you can use something like this. It will disable the logs. https://docs.docker.com/config/containers/logging/configure#supported-logging-drivers ``` redis: image: redis:latest logging: driver: none ```

At the time of recording, it was Rails 5.1.1, but it should still be the same concept.

I agree with the concerns. It's really helpful in repeatability situations. However, it does work in single use cases as well. It could have just as easily been moved to the lib folder or something else. The main point wasn't where to put it, but rather don't clutter up the `application_controller`.

I've linked the source code. Thanks for catching that.

I would try to keep it as simple as possible. In some cases where you are trying to validate a coupon code, you may want to raise a custom error for the coupon code if it is not valid. Add a catch for that error within the RescueHandler and respond back with the appropriate message. On some cases where you may have nested_attributes_for, you should have validations within the nested attributes and those should be taken into consideration when creating and updating records. For example, if I have a `book` which has many `authors` and the authors are created via `accepts_nested_attributes_for`, when I make a post to the books with the parameters `book[authors_attributes][0][full_name] = ""`, I would get the response `{"message":"Validation failed: Authors full name can't be blank"}`