Delve into creating, optimizing, and securing a Rails API from scratch. Gain insights into building a full-fledged, efficient Rails API, ready for immediate use.

rails.tar.gz

Routes changes

validating_the_user_model

unit_tests

show_user

migration_file

create_tokens

feed_the_database

presentation_of_JSON_API

validating_the_order_model

list_orders

decrementing_product_quantity

extending_the_placement_model

feed_the_database-2

feed_the_database-3

Setting Up the Authentication Token

validating_the_product_model

unit_tests_for_order_model

the_placement_model

decrementing_product_quantity-2

activation_of_CORS

This course is a comprehensive tutorial that will teach you the best way to build your next API with Rails. You’ll learn to create a Rails API from scratch and to optimize and secure a Rails API. By the end of this course, you’ll have a full-fledged Rails API ready to be used.

Building your own API with Rails

## Default migration file
The **migration file** contained in the `db/migrate` folder that was generated by `rails generate model` contains the migration that describes the changes which will be made to the database. This file should look like this:

class CreateUsers < ActiveRecord::Migration[6.0] 
  def change 
    create_table :users do |t| 
      t.string :email 
      t.string :password_digest 
      t.timestamps 
    end 
  end 
end 

>**Note:** The inserted date at the beginning of the migration file name should be different for you since it corresponds to
the migration file creation date.
## Adding validation parameters
We will make a small change to the migration to add some database validations. With Rails, it's common practice to make these verifications directly in the Ruby model. It is good practice to do also do this in the database schema. We will add three additional constraints:
 
- The `email` is mandatory. We use the property `null: false`. 
- The `email` must be unique. We add an index for the email column with the property `unique: true`. 
- The `password` is mandatory. We use the property `null: false`. 

Thus, the migration in the `db/migrate` directory becomes:
> **Note**: Click the "Run" button to run the error checker for all `.rb` files.

# Default migration file
The **migration file** contained in the `db/migrate` folder that was generated by `rails generate model` contains the migration that describes the changes which will be made to the database. This file should look like this:

>**Note:** The inserted date at the beginning of the migration file name should be different for you since it corresponds to
the migration file creation date.
# Adding validation parameters
We will make a small change to the migration to add some database validations. With Rails, it's common practice to make these verifications directly in the Ruby model. It is good practice to do also do this in the database schema. We will add three additional constraints:
 
- The `email` is mandatory. We use the property `null: false`. 
- The `email` must be unique. We add an index for the email column with the property `unique: true`. 
- The `password` is mandatory. We use the property `null: false`. 

Thus, the migration in the `db/migrate` directory becomes:
> **Note**: Click the "Run" button to run the error checker for all `.rb` files.

Let's add some constraints for the users' parameters.

Getting Started

The API

User Model

Authenticating the Users

User's Products

Building JSON

Placing Orders

Improving Orders

Optimizations

Wrap up

Appendix

Migration File

Default migration file