Larvata

convert an existing Rails helper to a decorator method

That method is presentation-centric, and thus does not belong in a model.

Where does that come from? It's a method of the source Article, whose methods have been made available on the decorator by the delegate_all call above.

a great way to replace procedural helpers like the one above with "real" object-oriented programming

format complex data for user display

taking care of polymorphic association

.public_send

ClassMethods

testing the response body should just verify that the application is sending the right content.

Unauthorized

Forbidden

Your test should also ensure that any desired business logic gets completed as expected.

Request specs provide a thin wrapper around Rails’ integration tests, and are designed to drive behavior through the full stack

we’ll be doing json = JSON.parse(response.body) a lot. This should be a helper method.

HTTP is meant to run over a bidirectional tunnel for arbitrary binary data; when that tunnel is an SSL/TLS connection, then the whole is called "HTTPS".

"SSL" means "Secure Sockets Layer".

"TLS" means "Transport Layer Security".

not just Internet-based sockets

"HTTPS" is supposed to mean "HyperText Transfer Protocol Secure",

Other protocol acronyms have been built the same way, e.g. SMTPS, IMAPS, FTPS... all of them being a bare protocol that "got secured" by running it within some SSL/TLS.

To make the confusing perfect: SSL (secure socket layer) often refers to the old protocol variant which starts with the handshake right away and therefore requires another port for the encrypted protocol such as 443 instead of 80.

teardown

executed sequentially

the result of the exercise is verified against the developer’s expectations.

reset to its pre-setup state.

When describing a context, start its description with "when" or "with".

is_expected.to respond_with

In isolated unit specs, you want each example to specify one (and only one) behavior.

Contexts are a powerful method to make your tests clear and well organized

not isolated

est valid, edge and invalid case.

new projects always use the expect syntax

On one line expectations or with implicit subject we should use is_expected.to

When you have to assign a variable instead of using a before block to create an instance variable, use let.

provide a :namespace option for your form to ensure uniqueness of id attributes on form elements.

a form builder object (the f variable).

Replace MODEL with the class name used for the application’s users (it’s frequently User but could also be Admin)

If you add an option, be sure to inspect the migration file (created by the generator if your ORM supports them) and uncomment the appropriate section

set up the default URL options for the Devise mailer in each environment

should restart your application after changing Devise's configuration options

set up a controller with user authentication, just add this before_action

when using a :user resource, the user_root_path will be used if it exists; otherwise, the default root_path will be used

When you run Docker without using swarm mode, you execute container commands.

You can run swarm services and standalone containers on the same Docker instances.

A node is an instance of the Docker engine participating in the swarm

You can run one or more nodes on a single physical computer or cloud server

To deploy your application to a swarm, you submit a service definition to a manager node.

Manager nodes also perform the orchestration and cluster management functions required to maintain the desired state of the swarm.

Worker nodes receive and execute tasks dispatched from manager nodes.

service is the definition of the tasks to execute on the worker nodes

When you create a service, you specify which container image to use and which commands to execute inside running containers.

replicated services model, the swarm manager distributes a specific number of replica tasks among the nodes based upon the scale you set in the desired state.

global services, the swarm runs one task for the service on every available node in the cluster.

A task carries a Docker container and the commands to run inside the container

Manager nodes assign tasks to worker nodes according to the number of replicas set in the service scale.

If you do not specify a port, the swarm manager assigns the service a port in the 30000-32767 range.

Swarm mode has an internal DNS component that automatically assigns each service in the swarm a DNS entry.