beech-api 3.9.0-beta.9-rc → 3.9.75

package/README.md

@@ -1,1649 +1,1715 @@
-[![N|Solid](https://i.ibb.co/NKxx9NQ/beech320.jpg)](https://github.com/bombkiml)
-
-# Beech API framework
-#### Auto endpoint v.3.9.0 (LTS)
-
-[![beech-api release](https://img.shields.io/github/v/release/bombkiml/beech-api)](https://github.com/bombkiml/beech-api/releases/)
-[![PyPI license](https://shields.io/pypi/l/ansicolortags.svg)](https://github.com/bombkiml/beech-api/blob/master/README.md)
-
-# What is Beech API ?
-
-The Beech API is API framework, It's help you with very easy to create API project under [Node.js](https://nodejs.org)
-
-## Let's go
-- <b>[Installation](#installation)</b>
-- <b>[Creating a project](#creating-a-project)</b>
-- <b>[Upgrade to latest version](#upgrade-to-latest-version)</b>
-- <b>[Beech CLI tool available](#beech-cli-tool-available)</b>
-- ✨ <b>Automation Endpoints with CRUD</b>
-  - [Database Connection](#database-connection)
-    - [Model](#models)
-  - [Retrieving data with Query String](#retrieving-data-with-query-string)
-    - Conditions
-    - Grouping
-    - Ordering
-    - Timestamps (Add-on in Store and Update)
-  - [Transactions](#-transactions)
-    - [Disorganized transactions](#way-1---disorganized-transactions-)
-    - [Organized transactions](#way-2---organized-transactions-)
-    - [Transactions set Isolation levels](#way-3---transactions-set-isolation-levels-)
-  - [Endpoints](#endpoints)
-  - [Helpers](#helpers)
-- 🔐 <b>System Management of Authentication</b>
-  - [Authentication Manegement](#authentication-passport-jwt)
-    - [Request Token](#request-token)
-    - [Beech Guard](#beech-guard)
-      - Verify Identity Management
-      - Two Factor (2fa, OTP, etc.)
-    - [Beech User Authentication Managements](#-beech-user-authentication-managements)
-      - Create Auth
-      - Update Auth
-- 🛠️ <b>Safe Endpoints Request</b>
-  - [Rate Limit](#-custom-endpoint-specific-rate-limit)
-  - [Slow Down](#-custom-endpoint-specific-slow-down)
-  - [Block Duplicate Request per Window](#-custom-endpoint-specific-duplicate-request)
-  - [JWT Broken Role](#jwt-broken-role)
-  - [Advance Guard (Timimg)](#-beech-advanced-guard-timing)
-- 🙂 <b>Hight Security under passport-jwt, oauth2</b>
-- 🌐 <b>Supported Official Strategy</b>
-  - [Google](#-google-strategy)
-  - [Facebook](#-facebook-strategy)
-- 🖥️ <b>CORS Origin & Server Configuration</b>
-  - [Config Base public path `./`](#cors-origin--server-configuration)
-  - [Allow origin whitelist](#cors-origin--server-configuration)
-- 📚 <b>Databases Managements</b>
-  - [Migrations](#databases-managements)
-  - [Seeder](#-creating-first-seeder)
-- ☕ <b>Testing</b>
-  - [Jest](#testing)
-- 🏃 <b>Implementration</b>
-  - [Docker](#implementation)
-  - [PM2](#-implement-with-pm2)
-
-# Environment
-
-- [`Node.js`](https://nodejs.org) >= 18.17.1+ (recommended)
-
-# Installation
-
-Beech API needed Node.js version 18.17.1 or above. You can management multiple versions on the same machine with [nvm](https://github.com/creationix/nvm) or [nvm-windows](https://github.com/coreybutler/nvm-windows).
-
-<b>So, Let's go to install</b> `beech-api`
-
-```sh
-# NPM
-$ npm install beech-api --global
-
-# Yarn
-$ yarn global add beech-api
-```
-
-Installation demo:
-
-[Demo 1](https://i.ibb.co/TBjNgVrF/1-11.gif)
-![Alt Text](https://i.ibb.co/TBjNgVrF/1-11.gif)
-
-[Demo 2](https://i.ibb.co/wrdgyzDP/ezgif-8539024298ec62a9.gif)
-![Alt Text](https://i.ibb.co/wrdgyzDP/ezgif-8539024298ec62a9.gif)
-
-After installation, you will have access to the `beech-app` binary in your command line.
-You can check you have the right version with this command:
-
-```sh
-$ beech-app --version
-```
-
-# Creating a project
-
-Create a new project run:
-
-```sh
-$ beech-app create hello-world
-```
-Run your project:
-```sh
-$ cd hello-world
-
-$ npm start
-# OR
-$ yarn start
-```
-
-❓ **Note:** The Beech API it's start server at [http://localhost:9000](http://localhost:9000) you can change new a port in `app.config.js` file.
-
-
-# Upgrade to latest version
-The Beech API upgrade to latest version command avariable :
-
-```sh
-// Project upgrade
-$ beech-app update
-
-// Global upgrade
-$ beech-app update -g, --global
-```
-
-# Beech CLI tool available
-After installation, you will have access to the `beech` binary in your command line.
-The `beech` command has a number of options and you can explore them all by running:
-
-```sh
-$ beech --help
-```
-
-The `beech` command line available:
-
-```
-Usage:
-  $ beech [options] [arguments] [special]
-
-Options:
-  ?, -h, --help                       Display this help message.
-  -v, --version                       Display the application version.
-
-The following commands are available:
-
-  $ beech make <endpoint>             Create a new Endpoints and unit test file,
-                                      You might using [special] `-R, --require`
-                                      for choose Model(s) used to endpoint file.
-  $ beech make <model> -M, --model    Create a new Models file.
-  $ beech make <helper> --helper      Create a new Helpers file.
-  $ beech passport init               Initialize authentication with passport-jwt.
-  $ beech skd init                    Initialize Job Scheduler file.
-  $ beech key:generate, key:gen       Re-Generate application key (Dangerous!).
-  $ beech hash:<text>                 Hash text for Access to Database connection.
-```
-❓ **Note:** Every to create new project will be generated new ``app_key`` in ``app.config.js`` file.
-
-❓ **Note:** If you can re-generate. Can use command ``$ beech key:generate`` or ``$ beech key:gen``
-
-# Database connection
-
-You might connection to Database with `database_config` object in `app.config.js` file. Anything can support to multiple Database connections.
-
-The connection base on `pool_base` in `global.config.js` file.
-
-- `basic` = Support only Raw Query with Only MySQL.
-- `sequelize` = Support PDO, Raw Query with various Database Engine.
-
-In case Access to Database must to Hash the `username` and `password` with Beech CLI like this.
-
-```sh
-// Hash database username
-$ beech hash:root
-Output: m42BVxQ6Q4kLdRX7xS_Hm7WbQiNqShJDvw9SLCgI431oafWBtQJoJDnoCL
-
-// Hash database password
-$ beech hash:password
-Output: FjgcgJPylkV7EeQJjea_EeifPwaHVO9onD3ATk3YYAyvjtMGu3dcDS0ejA
-
-```
-***For Example :***
-
-📂 app.config.js
-```js
-// Database configuration Only Basic & Sequelize (needed Hash)
-
-...
-
-database_config: [
-  {
-    dialect: "mysql",
-    name: "mysql_my_store_db",
-    host: "localhost",
-    username: "m42BVxQ6Q4kLdRX7xS_Hm7WbQiNqShJDvw9SLCgI431oafWBtQJoJDnoCL",
-    password: "FjgcgJPylkV7EeQJjea_EeifPwaHVO9onD3ATk3YYAyvjtMGu3dcDS0ejA",
-    database: "my_store_db",
-    port: "3306",
-
-    // Specify global options, which are used when Define is called.
-    define: {
-      charset: "utf8",
-      freezeTableName: true,
-      ...
-    },
-
-    timezone: "+07:00", // Example: GMT+2
-    // or use a named timezone supported by Intl.Locale
-    // timezone: 'America/Los_Angeles',
-
-    logging: console.log, // SQL trace logs. Learn more: https://sequelize.org/docs/v6/getting-started/#logging
-
-    is_connect: true, // Boolean, Turn ON/OFF to connect
-  },
-
-  ...
-
-],
-
-...
-```
-❓ **Caution! :**  Every re-new generate `app_key`. Must to new Hash your Access and change to ALL Database connections.
-
-❓ **Development** : You can add ```dev: true``` in ```main_config``` for a better experience.
-
-# Models
-
-The `models` keep the files of function(s) data managemnets for Retriving, Creating, Updating and Destroying (CRUD). for understanding you might make model name same your table name inside `src/models` folder.
-
-```sh
-$ beech make modelName --model
-```
-
-## # Model (Basic)
-
-  Basic model only support `MySQL` Raw Query format and freedom of your SQL query
-
-  ❓ **Note:**  The Basic pool engine it's not support auto Endpoints.
-
-
-***For example :***
-
-📂 models/Fruit.js
-```js
-module.exports = {
-
-  // Example basic function get data
-  getData() {
-
-    return {
-      id: 1,
-      name: "John Doe",
-    }
-
-  },
-
-  // Example basic function get data from MySQL table
-  getFruit() {
-
-    // calling Pool connection name by `mysql.default_db`
-    mysql.default_db.query("SELECT * FROM fruit", (err, results) => {
-
-      if (err) { throw err }
-      return results;
-
-    });
-
-  }
-
-};
-```
-
-## # Model (Sequelize)
-
-  Sequelize is a promise-based Node.js ORM tool for Postgres, MySQL, MariaDB, SQLite, Microsoft SQL Server, Oracle Database, Amazon Redshift and Snowflake’s Data Cloud. It features solid transaction support, relations, eager and lazy loading, read replication and more. <br/>You can learn more: [Sequelize docs](https://sequelize.org/docs/v6)
-  
-  You can asign more DataTypes, Learn more : [Sequelize docs](https://sequelize.org/docs/v6/core-concepts/model-basics/#data-types)
-
-  ❓ **Note:** When you generate a model it's create table structure for automatically for you.
-
-***For example :***
-
-📂 models/Fruit.js
-```js
-const { Schema } = require("beech-api");
-
-// Define table Schema with `Schema(sql.default_db)` connection name
-const Fruit = Schema(sql.default_db).define("fruit", {
-  fruit_id: {
-    field: "id", // Rename PK field to fruit_id Ref: `id` field in fruit table
-    type: DataTypes.INTEGER,
-    autoIncrement: true,
-    primaryKey: true
-  },
-  friut_uuid: {
-    field: "uuid",
-    type: DataTypes.STRING(100),
-    allowNull: true,
-    defaultValue: DataTypes.UUIDV4,
-  },
-  fruitName: DataTypes.STRING,
-  fruitQty: DataTypes.INTEGER,
-  fruitPrice: {
-    type: DataTypes.INTEGER,
-    allowNull: false, // Allow null feilds
-  },
-  sort: DataTypes.STRING,
-  createdAt: {
-    type: DataTypes.DATE,
-    allowNull: false,
-    defaultValue: DataTypes.NOW,
-  },
-  updatedAt: {
-    type: DataTypes.DATE,
-    allowNull: true,
-  },
-}, {
-  // Enables timestamps with createdAt and updatedAt
-  timestamps: true,
-  // Custom field names createdAt and updatedAt
-  createdAt: "createdAt",
-  updatedAt: "updatedAt",
-});
-
-Fruit.options = {
-  // Choose one for Allow magic generate default Endpoint (CRUD), It's like magic creating The endpoints for you (CRUD) ✨
-
-  // Option 1: Allow all methods
-  defaultEndpoint: true,
-
-   // Option 2: Allow with specific per methods
-  defaultEndpoint: {
-    GET: true,
-    POST: {
-      allow: true, // allow Auto-Endpoint
-      jwt: {
-        allow: true, // allow JWT
-        broken_role: [
-          { role: [1, 2] },
-        ],
-      },
-      // Rate Limit for POST
-      rate_limit: {
-        windowMs: 15 * 60 * 1000, // 15 minutes
-        limit: 100, // Limit each IP to 100 requests per `window` (here, per 15 minutes).
-        // store: ... , // Redis, Memcached, etc.
-        // See more: https://www.npmjs.com/package/express-rate-limit#Configuration
-      },
-      // Duplicate Request for POST
-      duplicate_request: {
-        expiration: 500, // Can't duplicate request for 5 milliseconds each IP requests per `window` (Disabled for Set expiration to 0 zero.)
-      },
-    },
-    PATCH: false,
-    DELETE: false,
-  },
-
-  limitRows: 100, // Limit rows default 100
-};
-
-// Example Finder by id (ORM), Learn more: https://sequelize.org/docs/v6/core-concepts/model-querying-finders/
-function exampleFindOneFruitById(id) {
-  return Fruit.findOne({ where: { id: id } });
-}
-
-// Example Raw Query with Model Instances. This allows you to easily map a query to a predefined model
-function exampleGetAllFruitWithModelInstance(id) {
-  return Fruit.query("SELECT * FROM fruit", {
-    model: Fruit, // When JOIN table needed register that table [Fruit, ...]
-    mapToModel: true // pass true here if you have any mapped fields
-  });
-}
-
-// Example Raw Query, Learn more: https://sequelize.org/docs/v6/core-concepts/raw-queries/
-function exampleGetAllFruit(id) {
-  return Fruit.query("SELECT * FROM fruit");
-}
-
-...
-
-// Export Schema, Function, ...
-module.exports = {
-  Fruit,
-  exampleFindOneFruitById,
-  exampleGetAllFruitWithModelInstance,
-  exampleGetAllFruit,
-  ...
-};
-```
-
-## Retrieving data with Query String
-
-Now you can add Query String with Conditional, Grouping and Ordering (Now Support Readonly for GET method)
-
-### ✨ That's cool! It's like magic Creating The Endpoints for you (CRUD) ✨
-
-<b style="font-size:12pt">For Example, Now!</b>, You can request to `/fruit` with methods GET, POST, PATCH and DELETE like this.
-
-| Efficacy |  Method  |        Endpoint        |    Body      | Mode    |
-|:---------|:---------|:-----------------------|:-------------|:--------|
-|  Create  |  POST    | /fruit                 |     { }      | Single  |
-|  Create  |  POST    | /fruit                 |     [ ]      | Bulk    |
-|  Read    |  GET     | /fruit                 |     No       | Fetch   |
-|  Read    |  GET     | /fruit/:limit/:offset  |     No       | Fetch   |
-|  Read    |  GET     | /fruit?someField=1     |     No       | Fetch   |
-|  Read    |  GET     | /fruit?orderby=sort    |     No       | Fetch   |
-|  Read    |  GET     | /fruit?groupby=id      |     No       | Fetch   |
-|  Update  |  PATCH   | /fruit/:id             |     { }      | Single  |
-|  Delete  |  DELETE  | /fruit/:id             |     No       | Single  |
-
-Add some Basic Conditions, Grouping and Ordering with `QUERY STRING` under GET methods<br/>
-
-Retrieving `fruit` data with GET : `/fruit?someField=[eq,1]&groupby=[id]&orderby=[id,desc]`
-
-***For Example :***
-
-```java
-// WHERE Conditions
-GET: /fruit?id=1                      // id = 1
-GET: /fruit?isActived=[eq,1]          // isActived = 1
-GET: /fruit?fruitName=[like,Banana%]  // fruitName LIKE 'Banana%' (Not allow with date, time)
-GET: /fruit?cost=[gt,50]&qty=[lt,10]  // cost > 50 AND qty < 10
-GET: /fruit/10/0?qty=[lt,10]          // qty < 10 LIMIT 0,10
-
-// Grouping
-GET: /fruit?groupby=id                // GROUP BY id
-GET: /fruit?groupby=[id,fruitName]    // GROUP BY id, fruitName
-
-// Ordering
-GET: /fruit?oderby=id                 // ORDER BY id ASC
-GET: /fruit?oderby=[sort,desc]        // ORDER BY sort DESC
-```
-
-For usage avariable:
-
-```java
-// Basics conditions
-3                                     // = 3
-[eq, 3]                               // = 3
-[ne, 20]                              // != 20
-[is, null]                            // IS NULL
-[not, null]                           // IS NOT NULL
-[or, [5, 6]]                          // (someField = 5) OR (someField = 6) // Not support NULL value
-
-// Number comparisons conditions
-[gt, 6]                               // > 6
-[gte, 6]                              // >= 6
-[lt, 10]                              // < 10
-[lte, 10]                             // <= 10
-[between, [6, 10]]                    // BETWEEN 6 AND 10
-[between, [2025-01-01, 2025-04-30]]   // BETWEEN '2025-01-01 00:00:00' AND '2025-04-30 23:59:59'
-                                      // When assign Datetime format will only support field datatype is `Date`, `Datetime`, `Time`
-
-// OR You can assign Datetime like this.
-[between, [2025-01-01 12:00:00, 2025-04-30 15:00:00]] // BETWEEN '2025-01-01 12:00:00' AND '2025-04-30 15:00:00'
-
-[notBetween, [11, 15]]                // NOT BETWEEN 11 AND 15
-
-// Other operators conditions
-[in, [1, 2, 3]],                      // IN [1, 2, 3]
-[notIn, [1, 2, 3]],                   // NOT IN [1, 2, 3]
-[like, %hat]                          // LIKE '%hat' (Avoid use #, % and %<Number> between wording)
-                                      // Becuase URL will be decoded it, Reccommand use startsWith, endsWith and substring when you need assing Number value)
-                                      // And NOT SUPPORT field datatype is `date`, `datetime`, `time`. Should be use with datatype is `String` or `Number` it work!.
-
-[notLike, %hat]                       // NOT LIKE '%hat'
-[startsWith, hat]                     // LIKE 'hat%'
-[endsWith, hat]                       // LIKE '%hat'
-[substring, hat]                      // LIKE '%hat%'
-
-// Grouping
-groupby=id                            // GROUP BY id
-groupby=[id]                          // ORDER BY id
-groupby=[id, fruitName]               // ORDER BY id, fruitName
-
-// Ordering
-oderby=id                             // ORDER BY id ASC (Basic usage default Ascending)
-oderby=[id, asc]                      // ORDER BY id ASC
-oderby=[id, desc]                     // ORDER BY id ASC
-oderby=[[id, desc], [sort, asc]]      // ORDER BY id DESC, sort ASC
-```
-
-## # Transactions
-
-Sequelize does not use transactions by default. However, for production-ready usage of Sequelize, you should definitely configure Sequelize to use transactions.
-
-Beech use Sequelize supports three ways of using transactions:
-
-- ### Way 1 - Disorganized transactions :
-```js
-// First, we start a transaction from your connection and save it into a variable
-const t = await Fruit.transaction();
-
-try {
-
-  // Then, we do some calls passing this transaction as an option:
-  const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
-  await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
-
-  // If the execution reaches this line, no errors were thrown.
-  // We commit the transaction.
-  await t.commit();
-
-} catch (error) {
-
-  // If the execution reaches this line, an error was thrown.
-  // We rollback the transaction.
-  await t.rollback();
-
-}
-```
-
-- ### Way 2 - Organized transactions :
-```js
-// First, we start a transaction from your connection and save it into a variable
-Fruit.transaction(async t => {
-  try {
-
-    // Then, we do some calls passing this transaction as an option:
-    const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
-    await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
-
-    // If the execution reaches this line, no errors were thrown.
-    // We commit the transaction.
-    await t.commit();
-
-  } catch (error) {
-
-    // If the execution reaches this line, an error was thrown.
-    // We rollback the transaction.
-    await t.rollback();
-
-  }
-});
-```
-
-- ### Way 3 - Transactions set Isolation levels :
-
-The possible [isolations levels](https://sequelize.org/docs/v6/other-topics/transactions/#isolation-levels) to use when starting a transaction:
-
-```js
-const { Transaction } = require('sequelize');
-
-// First, we start a transaction from your connection and save it into a variable
-Fruit.transaction(
-  {
-    isolationLevel: Transaction.ISOLATION_LEVELS.SERIALIZABLE,
-  },
-  async t => {
-    try {
-
-      // Then, we do some calls passing this transaction as an option:
-      const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
-      await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
-
-      // If the execution reaches this line, no errors were thrown.
-      // We commit the transaction.
-      await t.commit();
-
-    } catch (error) {
-
-      // If the execution reaches this line, an error was thrown.
-      // We rollback the transaction.
-      await t.rollback();
-
-    }
-});
-```
-
-# Endpoints
-
-The `endpoints` keep the endpoints basic request files currently support `GET`, `POST`, `PUT`, `PATCH` and `DELETE`.
-
-So, you might create new endpoints with constant `endpoint` object variable in `src/endpoints/` folder and file neme must be end with `-endpoints.js`
-
-```sh
-$ beech make endpointName
-```
-You might using [special] `-R, --require` for choose Model(s) used for that endpoint.
-
-***For Example :***
-
-📂 endpoints/fruit-endpoints.js
-```js
-// Require Model schema, Function & Others
-const { Fruit } = require("@/models/Fruit");
-
-exports.init = () => {
-
-  // GET method
-  endpoint.get("/fruit", Credentials, async (req, res) => {
-    // example call Fruit model for get data
-    res.json({
-      code: 200,
-      status: "SUCCESS",
-      results: await Fruit.findAll();
-    });
-  });
-
-
-  // POST method
-  endpoint.post("/fruit", Credentials, (req, res) => {
-    // @response
-    res.json({
-      code: 200,
-      status: "SUCCESS",
-      message: "POST request at /fruit",
-      result: {
-        id: req.body.id,
-        name: req.body.name,
-      },
-    });
-  });
-
-
-  // PUT method
-  endpoint.put("/fruit/:id", Credentials, (req, res) => {
-    // @response
-    res.json({
-      code: 200,
-      status: "SUCCESS",
-      message: "PUT request at /fruit/" + req.params.id,
-    });
-  });
-
-
-  // DELETE method
-  endpoint.delete("/fruit/:id", Credentials, (req, res) => {
-    // @response
-    res.json({
-      code: 200,
-      status: "SUCCESS",
-      message: "DELETE request at /fruit/" + req.params.id,
-    });
-  });
-
-  ...
-
-}
-```
-
-# JWT Broken Role
-
-The **JWT Broken Role** mechanism provides a flexible way to bypass or override role-based authorization rules when using JWT.
-
-#### It can be applied in three different levels, depending on your use case.
-
-| Priority | Level 	                         | Scope                    | Best For                        |
-|:---------|:--------------------------------|:-------------------------|:--------------------------------|
-| 3rd      | Global (``passport.config.js``) | All endpoints            |	Common authorization exceptions |
-| 2nd      | Model-level options             |	Per model & HTTP method |	Structured, reusable rules      |
-| 1st      | Endpoint middleware             |	Single endpoint	        | Custom or special cases         |
-
-This multi-layer approach allows you to design **secure, flexible, and maintainable JWT authorization flows**.
-
-### 1. Global Configuration (passport.config.js) - Priority 3
-
-You can define global JWT Broken Role rules that apply to all endpoints by configuring them in ``passport.config.js``.
-```js
-module.exports = {
-  // Enable JWT authentication
-  jwt_allow: true,
-
-  ...
-
-  // Global JWT broken role configuration
-  jwt_broken_role: [
-    {
-      role: [0, 2, 4],
-      email: "john.doe@company.com",
-    }, // Basic role matching
-
-    {
-      role: { $in: [0, 2, 4] },
-      email: { $regex: /@company\.com$/ },
-    }, // Advanced matching using operators
-  ],
-
-  ...
-};
-```
-
-**Use cases**
-
-- Apply common authorization exceptions across the entire application
-- Support both simple role arrays and advanced operators (``$in``, ``$regex``, etc.)
-
-### 2. Model-Level Configuration (Per HTTP Method) - Priority 2
-
-You can configure JWT and Broken Role rules per model and per HTTP method using model options.
-
-📂 src/models/Fruit.js
-```js
-Fruit.options = {
-  ...
-
-  // Auto-endpoint configuration by HTTP method
-  defaultEndpoint: {
-    GET: true, // Enable auto-generated GET endpoint
-
-    POST: {
-      allow: true,
-      jwt: {
-        allow: true,
-        broken_role: [
-          { role: [5, 6] },
-        ],
-      },
-    },
-
-    PATCH: {
-      allow: true,
-      jwt: {
-        allow: true,
-        broken_role: [
-          { role: [5, 6, 9] },
-          { department: "IT" },
-        ],
-      },
-    },
-
-    DELETE: false, // Disable auto-generated DELETE endpoint
-  },
-
-  ...
-};
-```
-
-**Use cases**
-
-- Fine-grained access control per HTTP method
-- Different role requirements for POST, PATCH, etc.
-- Combine role-based and attribute-based conditions
-
-### 3. Endpoint-Level Configuration (Credentials Middleware) - Priority 1
-
-For maximum flexibility, you can define Broken Role rules directly on a specific endpoint using the Credentials middleware.
-
-📂 endpoints/custom-fruit-endpoints.js
-```js
-const { Fruit } = require("@/models/Fruit");
-
-endpoint.delete(
-  "/destroy-fruit-by-id/:id",
-  Credentials([{ role: [5, 9] }]),
-  async (req, res) => {
-
-    // Only JWT tokens with role level 5 or 9 are allowed
-
-    const deleted = await Fruit.destroy({
-      where: {
-        id: req.params.id,
-      },
-    });
-
-    console.log("result:", deleted);
-
-    // @response
-  }
-);
-```
-
-**Use cases**
-
-- One-off or custom endpoints
-- Highly specific authorization rules
-- Override global or model-level behavior when necessary
-
-## Supported Basic & Operators Usage
-
-The JWT Broken Role system supports both basic value matching and advanced operators for flexible authorization rules.
-
-| Operator | Meaning            | Description                                                   |
-|:---------|:-------------------|:--------------------------------------------------------------|
-| $eq      | equal              | Matches when the value is equal                               |
-| $ne      | not equal          | Matches when the value is not equal                           |
-| $in      | value IN array     | Matches when the value exists in the specified array          |
-| $not     | value NOT IN array | Matches when the value does not exist in the specified array  |
-| $regex   | regex match        | Matches using a regular expression                            |
-| $fn      | custom function    | Matches using a custom evaluation function                    |
-
-## Evaluation Logic (Very Important !)
-```js
-[
-  { rule1 AND rule1 },
-  { rule2 AND rule2 }
-]
-        ⬇
-        OR
-```
-
-## Basic Usage for Examples :
-
-```js
-Credentials([
-  { role: [9] },         // Only role check
-  { email: 'a@b.com' },  // OR email
-])
-
-// Common Matching Patterns
-{ role: [1, 2, 3] }     // IN
-{ role: 1 }             // Equal
-{ email: 'a@b.com' }    // Equal
-{ department: 'IT' }    // Equal
-{ status: ['active'] }  // Dynamic key
-```
-
-## Operators Usage for Examples :
-
-```js
-// Equal with Role
-Credentials([
-  {
-    role: { $eq: [1, 2, 5] }
-  }
-])
-
-// Not Equal with Role
-Credentials([
-  {
-    role: { $ne: [0, 3] }
-  }
-])
-
-// Regex with Email domain
-Credentials([
-  {
-    email: { $regex: /@company\.com$/ }
-  }
-])
-
-// IN with Role
-Credentials([
-  {
-    role: { $in: [1, 2, 4] }
-  }
-])
-
-// NOT IN with Role
-Credentials([
-  {
-    role: { $not: [0, 3] }
-  }
-])
-
-// Multiple OR rules
-Credentials([
-  {
-    role: { $in: [1] },
-    email: 'john.doe@company.com'
-  },
-  // OR
-  {
-    role: { $in: [4] },
-    email: { $regex: /@company\.com$/ }
-  },
-])
-
-// Custom Function
-Credentials([
-  {
-    role: {
-      $fn: (value, user) => value >= 4 && user.department === 'IT'
-    }
-  }
-])
-```
-
-# Helpers
-
-The `helpers` keep the files of functions for process specific something in the project. So, you might create the `helpers` in path `src/helpers` folder.
-
-```sh
-$ beech make helperName --helper
-```
-
-***For Example :***
-
-📂 helpers/TextEditor.js
-```js
-module.exports = {
-
-  textUpperCase(text) {
-    return text.toUpperCase();
-  },
-  
-  textTrim(text) {
-    return text.trim();
-  },
-
-  ...
-
-};
-```
-
-# Authentication (passport-jwt)
-
-Passport is authentication middleware for Node. It is designed to serve a singular purpose: authenticate requests. When writing modules, encapsulation is a virtue, so Passport delegates all other functionality to the application. This separation of concerns keeps code clean and maintainable, and makes Passport extremely easy to integrate into an application.
-
-### Passport-jwt Initialization
-
-```sh
-$ beech passport init
-```
-
-After passport initialized the `passport.config.js` it's appeared
-
-📂 passport.config.js
-```js
-module.exports = {
-  // Allow for using passport-jwt
-  jwt_allow: true,
-
-  // custom authenticaiton endpoint name, default `/authentication`
-  auth_endpoint: "",
-
-  // your jwt secret key
-  secret: "your_jwt_secret",
-
-  // token expiry time (seconds), default 86400 sec. it's expired in 24 hr.
-  token_expired: 86400,
-
-  // Allow for using global jwt broken role
-  jwt_broken_role: [
-    // { role: [1, 2, 9] },
-  ],
-
-  model: {
-    // Main sql connection name. You must make sure connection name like inside `app.config.js` file and choose one connection name.
-    name: "default_db",
-
-    // table name of users store, default table `users`
-    table: "",
-
-    // secret user store field for authenticate, default field `username` and `password`
-    username_field: "",
-    password_field: "",
-
-    // JWT playload data, You can add it. Example: ["name", "email", ...]
-    fields: [],
-
-    // Other fields add for authentication.
-    guard: {
-      // Basic guard field, Example: ["pin", "hint", "2fa"]
-      guard_field: [],
-
-      // Advanced guard jwt request (needed some logical from front-end)
-      advanced_guard: {
-        allow: false,
-        entity: "", // default entity `timing`
-        secret: "top_secret",
-        time_expired: {
-          minutes: 1, // should length [0-60]
-          seconds: 0, // should length [0-60]
-        },
-      },
-    },
-  },
-
-  // Allow for using request with app_key entity (Every request must be using the app_key entity in headers)
-  app_key_allow: false
-
-  ...
-
-};
-```
-### Request Token
-**Authentication structure :** Simple ``users`` table:
-```
-==============================================================
-|  id  |  username | password |     name     |     email     |
---------------------------------------------------------------
-|  1   |  bombkiml |  secret  | bombkiml NC. | bomb@bomb.com |
-|  2   |  johnson  |  secret  | johnson BA.  | john@bomb.com |
-```
-
-When you config passport with ```users``` table already. You will got Auth endpoint in available.
-```js
-POST:  "/authentication"               // Request token
-POST:  "/authentication/refresh"       // Request refresh token
-POST:  "/authentication/create"        // Create new Auth data
-PATCH: "/authentication/update/:id"    // Update old Auth data (needed user id)
-```
-
-***XHR Example :***
-
-```js
-// Request with body for gether Token
-POST: "/authentication"
-payload: {
-  username: "bombkiml",
-  password: "secret"
-}
-
-// Request with header for refresh token
-POST: "/authentication/refresh"
-headers: Authorization: Bearer <your_token>
-
-// Request with body for Create Auth data
-POST: "/authentication/create"
-payload: {
-  username: "add_new_username",
-  password: "add_new_secret",
-  name: "add_new_my_name",
-  email: "add_new_email"
-}
-
-// Request with body for Update Auth data
-PATCH: "/authentication/update/1"
-headers: Authorization: Bearer <your_token>
-payload: {
-  username: "update_bombkiml",
-  password: "update_secret",
-  name: "update_my_name",
-  email: "my_update_email@bomb.com"
-}
-```
-
-# Beech Guard
-You can easy using 2 Factor authenticate with ```guard_field``` inside ```passport.config.js``` file and add your Guard field ex: ```2fa``` field for Authenticate Conditions.
-
-## # Guard (2FA, Other)
-
-📂 passport.config.js
-```js
-module.exports = {
-  ...
-
-  guard: {
-    // Other fields add for authenticate, exmaple ["pin", "hint", "2fa"]
-    guard_field: ["2fa"], 👈 // your feild guard. (Disabled to remove it.)
-
-    ...
-  },
-
-  ...
-
-}
-```
-
-## # Beech Advanced Guard (Timing)
-Advance Guard for Protection your Endpoint with Timing. You can allow in object ```advance_guard``` inside ```passport.config.js``` file. So let's go add your Advance Guard Configuration.
-
-📂 passport.config.js
-```js
-module.exports = {
-  ...
-
-  guard: {
-    ...
-
-    // Advanced guard to Request (Needed some logical from front-end)
-    advanced_guard: {
-      allow: false, 👈 // advanced guard allow for All Endpoint.
-      entity: "", // default entity `timing`
-      secret: "your_advance_guard_secret",
-      time_expired: {
-        minutes: 1, // should length [0-60]
-        seconds: 0, // should length [0-60]
-      },
-    },
-  },
-
-  ...
-
-}
-
-```
-
-<b>After configure</b>, You must add some logic in your front-end like this.
-
-Before add logic, We needed [```beech-auth0```](https://github.com/bombkiml/beech-auth0) and [```moment.js```](https://momentjs.com) for apply in Policy.
-
-```sh
-# NPM
-$ npm install --save beech-auth0 moment
-
-# Yarn
-$ yarn add beech-auth0 moment
-```
-Now! you can add some logic like this.
-
- - Import packages
-
-```js
-// CommonJS
-const { Auth0 } = require("beech-auth0");
-const moment = require("moment");
-
-// ES6
-import { Auth0 } from "beech-auth0";
-import moment from "moment";
-```
-
-- Get unix time with momentJS
-
-```js
-// Get UNIX TIME with moment
-let unix_time = moment().unix();
-```
-
-- Get hashing with Beech Auth0
-
-```js
-// Auth0 Policy.
-Auth0(unix_time, 'your_advance_guard_secret', (error, hashing) => {
-
-  // Your XHR request for All Endpoint.
-  POST: "/authentication"
-  headers: { timing: hashing } 👈 // Assign advance guard entity to headers with callback hashing.
-
-});
-
-```
-
-## # Beech User Authentication Managements ###
-You can easy management `users` data with Beech, Only ```Store, Update``` NO ```Delete```, Anything you can make DELETE endpoint by yourself
-
-```js
-const { Store, Update } = require("beech-api");
-```
-
-- ***Store*** users data with ``Store()``
-```js
-// prepare data for store users
-var data = {
-  username: "bombkiml",
-  password: "secret",
-  name: "bombkiml nc.",
-  email: "bomb@bomb.com"
-}
-
-Store(data, (err, stored) => {
-  if (err) throw err;
-  
-  // response affected data
-  console.log(stored.insertId, stored.affectedRows);
-
-});
-```
-
-- ***Update*** users data with ``Update()``
-```js
-// prepare data for update users
-var data = {
-  password: "new_secret",
-  name: "bombkiml NC.",
-  email: "bombkiml@bomb.com"
-}
-
-Update(data, id, (err, updated) => {
-  if (err) throw err;
-
-  // response affected data
-  console.log(updated.updateId, updated.affectedRows);
-
-});
-```
-
-# Beech with Official Strategy
-
-Latest supported with ``Google`` and ``Facebook`` Strategy.
-
-
-## # Google Strategy
-
-
-The Google OAuth 2.0 authentication strategy authenticates users using a Google account and OAuth 2.0 tokens. The strategy requires a verify callback, which accepts these credentials and calls done providing a user, as well as options specifying a client ID, client secret, and callback URL.
-
-Before your application can make use of Sign In With Google, you must register your app with Google. This can be done in the [APIs & Services](https://console.cloud.google.com/apis) page of the [Google Cloud Platform console.](https://console.cloud.google.com/) Once registered, your app will be issued a client ID and secret which will be used in the strategy configuration.
-
-Go to open file ``passport.config.js`` and go to ``google strategy`` then turn allow Google Strategy is ``allow: true`` something like this.
-
-📂 passport.config.js
-```js
-...
-
-strategy: {
-
-  google: {
-
-    // Allow for using google strategy
-    allow: true,
-
-    // Authen profile store fields available: `google_id`, `name`, `email`, `photos`, `locate`
-    local_profile_fields: {
-      google_id: "google_id", // Google ID field, default field name: `google_id`
-      name: "your_name_field",
-      email: "your_email_field",
-      photos: "your_profile_url_field",
-      locate: "" // If you not store set to null or remove it.
-    },
-    // Google development Credentials OAuth 2.0 Client IDs
-    client_id: "GOOGLE_CLIENT_ID",
-    client_secret: "GOOGLE_CLIENT_SECRET",
-    // Callback endpoint default `/google/callback`
-    callbackURL: "",
-    // Failure redirect to your route
-    failureRedirect: "/login"
-  }
-}
-
-...
-```
-
-The above code is a configures and registers the Google Strategy.
-
-- ``allow`` : Turn on/off the Google Strategy config type of ``boolean`` switch by ``true/false``.
-- ``google_id`` : Local Google ID field for store Google ID in my local database default field is ``google_id``.
-- ``local_profile_fields`` : Local Profile fields for store Google user details.
-- ``client_id`` and ``client_secret`` : The options to the Google Strategy constructor must include a ``clientID`` and ``clientSecret``, the values of which are set to the client ID and secret that were obtained when registering your application.
-- ``callbackURL`` : When registering your application. A callbackURL must also be included. Google will redirect users to this location after they have authenticated.
-- ``failureRedirect`` : When registering your application somthing failure it's redirect to that.
-
-Place a button on the application's login page, prompting the user to sign in with Google.
-
-```html
-<a href="/authentication/google" class="button">Sign in with Google</a>
-```
-
-❓ **Note:** The URL "``/authentication``" will be follow by ``auth_endpoint`` when you custom it.
-
-
-## # Facebook Strategy
-
-
-Facebook Login allows users to sign in using their Facebook account. Support for Faceboook Login is provided by the ``passport-facebook`` package.
-
-Before your application can make use of Facebook Login, you must register your app with Facebook. This can be done in the [App dashboard](https://developers.facebook.com/apps) at [Facebook for Developers.](https://developers.facebook.com/) Once registered, your app will be issued an app ID and secret which will be used in the strategy configuration.
-
-Go to open file ``passport.config.js`` and go to ``facebook strategy`` then turn allow Facebook Strategy is ``allow: true`` something like this.
-
-📂 passport.config.js
-```js
-...
-
-strategy: {
-
-  facebook: {
-
-    // Allow for using facebook strategy
-    allow: true,
-
-    // Authen profile store fields available: `facebook_id`, `name`, `email`, `photos`, `locate`
-    local_profile_fields: {
-      facebook_id: "facebook_id", // Facebook ID field, default field name: `facebook_id`
-      name: "your_name_field",
-      email: "your_email_field",
-      photos: "your_profile_url_field",
-      locate: "" // If you not store set to null or remove it.
-    },
-    // Facebook development Credentials OAuth 2.0
-    app_id: "FACEBOOK_APP_ID",
-    app_secret: "FACEBOOK_APP_SECRET",
-
-    // You can allow Permissions facebook profile fields. Learn more (https://developers.facebook.com/docs/graph-api/reference/v13.0/user#readperms)
-    // **Update 2024, Now! Facebook requests permission for show Email. Learn more (https://developers.facebook.com/docs/permissions)
-    profileFieldsAllow: [ 'id', 'displayName', 'name', 'photos', 'email', 'location' ], // Default allowed
-
-    // Callback endpoint default `/facebook/callback`
-    callbackURL: "",
-    // Failure redirect to your route
-    failureRedirect: "/login"
-  }
-}
-
-...
-```
-
-The above code is a configures and registers the Facebook Strategy.
-
-- ``allow`` : Turn on/off the Facebook Strategy config type of ``boolean`` switch by ``true/false``.
-- ``facebook_id`` : Local Facebook ID field for store Facebook ID in my local database default field is ``facebook_id``.
-- ``local_profile_fields`` : Local Profile fields for store Facebook user details.
-- ``app_id`` and ``app_secret`` : The options to the Facebook Strategy must include an app ID and secret. you must register your app with Facebook. This can be done in the [App dashboard](https://developers.facebook.com/apps) at [Facebook for Developers.](https://developers.facebook.com/) Once registered, your app will be issued an ``app ID`` and ``secret`` which will be used in the strategy configuration.
-- ``profileFieldsAllow`` : Permissions with Facebook Login. You must allow Permissions facebook profile fields: see more (https://developers.facebook.com/docs/graph-api/reference/v13.0/user#readperms)
-- ``callbackURL`` : When registering your application. A callbackURL must also be included. Facebook will redirect users to this location after they have authenticated.
-- ``failureRedirect`` : When registering your application somthing failure it's redirect to that.
-
-Place a button on the application's login page, prompting the user to sign in with Facebook.
-
-```html
-<a href="/authentication/facebook" class="button">Log In With Facebook</a>
-```
-
-❓ **Note:** The URL "``/authentication``" will be follow by ``auth_endpoint`` when you custom it.
-
-# CORS Origin & Server Configuration
-The origin array to the callback can be any value allowed for the origin option of the middleware. Certain CORS requests are considered `complex` and require an initial OPTIONS request (called the `pre-flight request`). You can allowed CORS origin inside file `beech.config.js`
-
-📂 beech.config.js
-```js
-module.exports = {
-  defineConfig: {
-    // Base public path when served in development or production.
-    base: process.env.NODE_ENV === "production"
-          ? "/my-api/" // For Production
-          : "/", // For Development
-
-    server: {
-      // Client request allow origin whitelist
-      origin: ["http://example.com", "http://my-webapp:8080", "https://cat.io"],
-      originSensitive: false, // Sensitive with contrasts wording
-
-      // API Request rate limit (Disabled for Remove it.)
-      rateLimit: {
-        windowMs: 15 * 60 * 1000, // 15 minutes
-        limit: 100, // Limit each IP to 100 requests per `window` (here, per 15 minutes).
-        // store: ... , // Redis, Memcached, etc.
-        // See more: https://www.npmjs.com/package/express-rate-limit#Configuration
-      },
-
-      // API Duplicate Request (Disabled for Set expiration to 0 zero.)
-      duplicateRequest: {
-        expiration: 500, // Can't duplicate request for 5 milliseconds each IP requests per `window`
-      },
-
-      payload: {
-        // The limit of request body size, json default "100KB", urlencoded default "100KB". Learn more: https://expressjs.com/en/4x/api.html#express.json
-        json: {
-          limit: "100KB", // default: "100KB"
-        },
-        urlencoded: {
-          limit: "100KB", // default: "100KB"
-          extended: true, // default: true (reccomended: true)
-        },
-        file: {
-          uploadAllowMethod: ["POST", "PATCH", "PUT"], // Only apply file upload limit for POST, PATCH, PUT method.
-          allowedTypes: ["image/jpeg", "image/png", "application/pdf"], // Example: Allow only JPEG, PNG, and PDF files. Learn more: https://www.digipres.org/formats/mime-types/
-          limit: 5 * 1024 * 1024, // 5MB (default: Infinity)
-        },
-      },
-
-    },
-  },
-}
-```
-
-❓ **Note:** When you must to allowed all Origin. You can assign `*` or `[]` null value to `origin` variable.
-
-## # Custom Endpoint Specific Rate Limit
-When you need assign specific request Endpoint with [express-rate-limit](https://www.npmjs.com/package/express-rate-limit), You can managemnet with Beech object ```rateLimit``` for your custom Rate Limit like this.
-
-```js
-const { rateLimit } = require("beech-api").Express;
-
-// Specific of your rate limit
-const specificRateLimit1 = rateLimit({
-  windowMs: 5 * 60 * 1000, // 5 minutes
-  limit: 20,
-  // more...
-});
-
-// Your Endpoints...
-endpoint.get("/banana", specificRateLimit1, (req, res) => {
-  ...
-});
-
-...
-```
-
-## # Custom Endpoint Specific Slow Down
-**DON'T DO IT.** &nbsp; Because it's annoying to users.
-
-When you need assign specific request Endpoint with [express-slow-down](https://www.npmjs.com/package/express-slow-down), You can managemnet with Beech object ```slowDown``` for your custom Slow Down like this.
-
-```js
-const { slowDown } = require("beech-api").Express;
-
-// Specific of your slow down
-const specificSlowDown1 = slowDown({
-  windowMs: 15 * 60 * 1000,      // 15 minutes
-  delayAfter: 5,                 // Allow 5 requests per 15 minutes.
-  delayMs: (hits) => hits * 100, // Add 100 ms of delay to every request after the 5th one.
-  // more...
-  
-  /**
-   * So:
-   *
-   * - requests 1-5 are not delayed.
-   * - request 6 is delayed by 600ms
-   * - request 7 is delayed by 700ms
-   * - request 8 is delayed by 800ms
-   *
-   * and so on. After 15 minutes, the delay is reset to 0.
-   */
-});
-
-// Your Endpoints...
-endpoint.get("/banana", specificSlowDown1, (req, res) => {
-  ...
-});
-
-...
-```
-
-## # Custom Endpoint Specific Duplicate Request
-This middleware to Limit each IP duplicated requests per window.
-
-When you need assign specific request Endpoint with duplicate request use [express-duplicate-request](https://github.com/bombkiml/express-duplicate-request), You can managemnet with Beech object ```duplicateRequest``` for your custom Duplicate Request like this.
-
-```js
-const { duplicateRequest } = require("beech-api").Express;
-
-// Specific of your duplicate request
-const specificDup1 = duplicateRequest({
-  expiration: 500, // Can't duplicate request for 5 milliseconds, Should 0 to disabled
-  // more...
-});
-
-// Your Endpoints...
-endpoint.get("/banana", specificDup1, (req, res) => {
-  ...
-});
-
-...
-```
-
-# Databases managements
-
-## # Migrations & Seeder
-
-Just like you use Git / SVN to manage changes in your source code, you can use migrations to keep track of changes to the database. With migrations you can transfer your existing database into another state and vice versa: Those state transitions are saved in migration files, which describe how to get to the new state and how to revert the changes in order to get back to the old state.
-
-You will need [Sequelize CLI.](https://github.com/sequelize/cli) The CLI ships support for [migrations](https://sequelize.org/v5/manual/migrations.html) and project.
-
-## # Usage
-
-To create an empty project you will need to execute `init` command
-
-```sh
-$ npx sequelize-cli init
-```
-
-This will create following folders inside `databases` folder.
-
-- `config`, contains config file, which tells CLI how to connect with database.
-- `models`, contains all models for your project.
-- `migrations`, contains all migration files.
-- `seeders`, contains all seed files.
-
-## # Configuration
-
-Before continuing further we will need to tell CLI how to connect to database. To do that let's open default config file `databases/config/database.json` It looks something like this:
-
-```json
-{
-  "development": {
-    "username": "root",
-    "password": null,
-    "database": "database_development",
-    "host": "127.0.0.1",
-    "port": 3306, // IF your another port
-    "dialect": "mysql"
-  },
-  "test": {
-    "username": "root",
-    "password": null,
-    "database": "database_test",
-    "host": "127.0.0.1",
-    "dialect": "mysql"
-  },
-  "production": {
-    "username": "root",
-    "password": null,
-    "database": "database_production",
-    "host": "127.0.0.1",
-    "dialect": "mysql"
-  }
-}
-```
-
-❓ **Note:** The database connect default port 3306 if you another port you can add object ``port`` in config.
-
-❓ **Note:** If your database doesn't exists yet, you can just call `npx sequelize-cli db:create` command. With proper access it will create that database for you.
-
-## # Creating first Migrations
-
-Create `model` use `model:generate` command. This command requires two options.
-
-- `--name`, Name of the model
-- `--attributes`, List of model attributes
-
-Let's create a model name example `User`. See more about of [Datatypes](https://sequelize.org/v5/manual/data-types.html)
-
-```sh
-$ npx sequelize-cli model:generate --name User --attributes firstName:string,lastName:string,email:string,birhday:date
-```
-
-## # Migrations Up and Down
-
-Until this step, we haven't inserted anything into the database. We have just created required model and migration files for our first model User.
-
-- **Migrate Up** : you can create that table in database you need to run db:migrate command.
-
-  ```sh
-  $ npx sequelize-cli db:migrate
-  ```
-
-- **Migrate Down** : you can use `db:migrate:undo`, this command will revert most recent migration.
-  ```sh
-  // Step to undo
-  $ npx sequelize-cli db:migrate:undo
-
-  // All to undo
-  $ npx sequelize-cli db:migrate:undo:all
-
-  ```
-
-## # Creating First Seeder
-
-To manage all data migrations you can use seeders. Seed files are some change in data that can be used to populate database table with sample data or test data.
-
-Let's create a seed file which will add a demo user to our User table.
-
-```sh
-$ npx sequelize-cli seed:generate --name user
-```
-
-## # Seeder Up and Down
-
-In last step you have create a seed file. It's still not committed to database. To do that we need to run a simple command.
-
-- **Seed Up** : you can execute that seed file and you will have a user inserted into `User` table.
-
-  ```sh
-  $ npx sequelize-cli db:seed:all
-  ```
-
-- **Seed Down** : seeders can be undone if they are using any storage. There are two commands available for that:
-
-  If you wish to undo most recent seed
-
-  ```sh
-  $ npx sequelize-cli db:seed:undo
-  ```
-
-  If you wish to undo a specific seed
-
-  ```
-  $ npx sequelize-cli db:seed:undo --seed <seederName>
-  ```
-
-  If you wish to undo all seeds
-
-  ```sh
-  $ npx sequelize-cli db:seed:undo:all
-  ```
-
-# Testing
-
-Test using [Jest](https://jestjs.io/en/) for testing the project. Jest is a delightful JavaScript Testing Framework with a focus on simplicity. Learn more [Jest docs](https://jestjs.io/docs/en/getting-started.html)
-
-So, When you make the new endpoints it's automatic create test file end with `.spec.js` in `__test__` folder with constant `baseUrl` variable and `axios` package.
-
-***For Example :***
-
-📂 \_\_test\_\_/unit/endpoints/fruit-endpoints.spec.js
-```js
-const endpoint = baseUrl.concat("/fruit");
-
-describe("Test endpoint : " + endpoint, () => {
-  it("Truthy!", () => {
-    expect("/fruit").toBeTruthy();
-  });
-
-  it("Respond with basic GET status code 200", (done) => {
-    axios.get(endpoint).then((res) => {
-      expect(200).toEqual(res.data.code);
-      done();
-    });
-  });
-});
-```
-
-
-# Implementation
-
-## # Implement with [Docker](https://www.docker.com)
-
-[Docker](https://www.docker.com) is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly.
-
-- ### **Create Dockerfile**
-
-Docker builds images automatically by reading the instructions from a Dockerfile -- a text file that contains all commands, in order, needed to build a given image. A Dockerfile adheres to a specific format and set of instructions which you can find at [Dockerfile reference](https://docs.docker.com/engine/reference/builder/).
-
-📂 Dockerfile
-```js
-FROM node:18-alpine
-ENV NODE_ENV=production
-WORKDIR /usr/src/api
-COPY ["package.json", "package-lock.json*", "./"]
-RUN npm install --production --silent && mv node_modules .
-COPY . .
-EXPOSE 9000
-CMD ["node", "./node_modules/beech-api/packages/cli/beech"]
-```
-
-- ### **Docker build image**
-
-The docker build command builds an image from a Dockerfile and a context. The build’s context is the set of files at a specified location ```PATH``` or ```URL```. The PATH is a directory on your local filesystem. The URL is a Git repository location.
-
-```sh
-$ docker build -t <imageName> .
-```
-
-❓ **Note:** You can specify a repository and tag at which to save the new image : ``` $ docker build -t <imageName>:<tags> . ```
-
-- ### **Run docker**
-
-  After create ``image`` you can run docker engine following :
-
-  - ### **Docker Container (Standalone)**
-  ```sh
-  $ docker run -d -p 9000:9000 --name <containerName> <imageName>
-  ```
-
-  - ### **Create Docker Swarm (Cluster)**
-  ```sh
-  # Initiate swarm
-  $ docker swarm init
-  
-  # Run docker service
-  $ docker service create --replicas <instances> --name <containerName> --publish 9000:9000 <imageName>
-  ```
-
-## # Implement with [PM2](https://pm2.keymetrics.io/)
-[PM2](https://pm2.keymetrics.io/) is a daemon process manager that will help you manage and keep your application online. Getting started with PM2 is straightforward, it is offered as a simple and intuitive CLI, installable via [NPM](https://www.npmjs.com/).
-
-```sh
-# Start service as standalone
-$ pm2 start ./node_modules/beech-api/packages/cli/beech --name <serviceName>
-
-# OR
-
-# Start service as cluster mode
-$ pm2 start ./node_modules/beech-api/packages/cli/beech --name <serviceName> -i <instances>
-```
-
-# Development
-
-Want to contribute or join for great job!, You can contact to me via
-
-- GitHub: [bombkiml/beech-api - issues](https://github.com/bombkiml/beech-api/issues)
-- E-mail: nattapat.jquery@gmail.com
-- Facebook: [https://www.facebook.com/bombkiml](https://www.facebook.com/bombkiml)
-
-# License
-
-The Beech API framework is open-sourced software licensed under the [MIT license.](https://opensource.org/licenses/MIT)
+[![N|Solid](https://i.ibb.co/NKxx9NQ/beech320.jpg)](https://github.com/bombkiml)
+
+# Beech API framework
+#### Auto endpoint v.3.9.0 (LTS)
+
+[![beech-api release](https://img.shields.io/github/v/release/bombkiml/beech-api)](https://github.com/bombkiml/beech-api/releases/)
+[![PyPI license](https://shields.io/pypi/l/ansicolortags.svg)](https://github.com/bombkiml/beech-api/blob/master/README.md)
+
+# What is Beech API ?
+
+The Beech API is API framework, It's help you with very easy to create API project under [Node.js](https://nodejs.org)
+
+## Let's go
+- <b>[Installation](#installation)</b>
+- <b>[Creating a project](#creating-a-project)</b>
+- <b>[Upgrade to latest version](#upgrade-to-latest-version)</b>
+- <b>[Beech CLI tool available](#beech-cli-tool-available)</b>
+- ✨ <b>Automation Endpoints with CRUD</b>
+  - [Database Connection](#database-connection)
+    - [Model](#models)
+  - [Retrieving data with Query String](#retrieving-data-with-query-string)
+    - Conditions
+    - Grouping
+    - Ordering
+    - Timestamps (Add-on in Store and Update)
+  - [Transactions](#-transactions)
+    - [Disorganized transactions](#way-1---disorganized-transactions-)
+    - [Organized transactions](#way-2---organized-transactions-)
+    - [Transactions set Isolation levels](#way-3---transactions-set-isolation-levels-)
+  - [Endpoints](#endpoints)
+  - [Helpers](#helpers)
+- 🔐 <b>System Management of Authentication</b>
+  - [Authentication Manegement](#authentication-passport-jwt)
+    - [Request Token](#request-token)
+    - [Beech Guard](#beech-guard)
+      - Verify Identity Management
+      - Two Factor (2fa, OTP, etc.)
+    - [Beech User Authentication Managements](#-beech-user-authentication-managements)
+      - Create Auth
+      - Update Auth
+- 🛠️ <b>Safe Endpoints Request</b>
+  - [Rate Limit](#-custom-endpoint-specific-rate-limit)
+  - [Slow Down](#-custom-endpoint-specific-slow-down)
+  - [Block Duplicate Request per Window](#-custom-endpoint-specific-duplicate-request)
+  - [JWT Broken Role](#jwt-broken-role)
+  - [Advance Guard (Timimg)](#-beech-advanced-guard-timing)
+- 🙂 <b>Hight Security under passport-jwt, oauth2</b>
+- 🌐 <b>Supported Official Strategy</b>
+  - [Google](#-google-strategy)
+  - [Facebook](#-facebook-strategy)
+- 🖥️ <b>CORS Origin & Server Configuration</b>
+  - [Config Base public path `./`](#cors-origin--server-configuration)
+  - [Allow origin whitelist](#cors-origin--server-configuration)
+- 📚 <b>Databases Managements</b>
+  - [Migrations](#databases-managements)
+  - [Seeder](#-creating-first-seeder)
+- ☕ <b>Testing</b>
+  - [Jest](#testing)
+- 🏃 <b>Implementration</b>
+  - [Building for Production](#building-for-production)
+  - [Docker](#implementation)
+  - [PM2](#-implement-with-pm2)
+
+# Environment
+
+- [`Node.js`](https://nodejs.org) >= 18.18.0+ (recommended)
+
+# Installation
+
+Beech API needed Node.js version 18.18.0 or above. You can management multiple versions on the same machine with [nvm](https://github.com/creationix/nvm) or [nvm-windows](https://github.com/coreybutler/nvm-windows).
+
+<b>So, Let's go to install</b> `beech-api`
+
+```sh
+# NPM
+$ npm install beech-api --global
+
+# Yarn
+$ yarn global add beech-api
+```
+
+Installation demo:
+
+[Demo 1](https://i.ibb.co/TBjNgVrF/1-11.gif)
+![Alt Text](https://i.ibb.co/TBjNgVrF/1-11.gif)
+
+[Demo 2](https://i.ibb.co/wrdgyzDP/ezgif-8539024298ec62a9.gif)
+![Alt Text](https://i.ibb.co/wrdgyzDP/ezgif-8539024298ec62a9.gif)
+
+After installation, you will have access to the `beech-app` binary in your command line.
+You can check you have the right version with this command:
+
+```sh
+$ beech-app --version
+```
+
+# Creating a project
+
+Create a new project run:
+
+```sh
+$ beech-app create hello-world
+```
+Run your project:
+```sh
+$ cd hello-world
+
+$ npm run dev
+# OR
+$ yarn dev
+```
+
+❓ **Note:** The Beech API it's start server at [http://localhost:9000](http://localhost:9000) you can change new a port in `app.config.js` file.
+
+
+# Upgrade to latest version
+The Beech API upgrade to latest version command avariable :
+
+```sh
+// Project upgrade
+$ beech-app update
+
+// Global upgrade
+$ beech-app update -g, --global
+```
+
+# Beech CLI tool available
+After installation, you will have access to the `beech` binary in your command line.
+The `beech` command has a number of options and you can explore them all by running:
+
+```sh
+$ beech --help
+```
+
+The `beech` command line available:
+
+```
+Usage:
+  $ beech [options] [arguments] [special]
+
+Options:
+  ?, -h, --help                       Display this help message.
+  -v, --version                       Display the application version.
+
+The following commands are available:
+
+  $ beech make <endpoint>             Create a new Endpoints and unit test file,
+                                      You might using [special] `-R, --require`
+                                      for choose Model(s) used to endpoint file.
+
+  $ beech make <model> -M, --model    Create a new Models file, You might using
+                                      [special] `--no-comment` for ignore comment
+                                      Table Property in your Schema.
+
+  $ beech update model <model_name>   Update new Table Structure for latest, You
+                                      might using [special] `--no-comment` for 
+                                      ignore comment Table Property in your Schema.
+
+  $ beech make <helper> --helper      Create a new Helpers file.
+  $ beech passport init               Initialize authentication with passport-jwt.
+  $ beech skd init                    Initialize Job Scheduler file.
+  $ beech key:generate, key:gen       Re-Generate application key (Dangerous!).
+  $ beech hash:<text>                 Hash text for Access to Database connection.
+```
+❓ **Note:** Every to create new project will be generated new ``app_key`` in ``app.config.js`` file.
+
+❓ **Note:** If you can re-generate. Can use command ``$ beech key:generate`` or ``$ beech key:gen``
+
+# Database connection
+
+You might connection to Database with `database_config` object in `app.config.js` file. Anything can support to multiple Database connections.
+
+The connection base on `pool_base` in `global.config.js` file.
+
+- `basic` = Support only Raw Query with Only MySQL.
+- `sequelize` = Support PDO, Raw Query with various Database Engine.
+
+In case Access to Database must to Hash the `username` and `password` with Beech CLI like this.
+
+```sh
+// Hash database username
+$ beech hash:root
+Output: m42BVxQ6Q4kLdRX7xS_Hm7WbQiNqShJDvw9SLCgI431oafWBtQJoJDnoCL
+
+// Hash database password
+$ beech hash:password
+Output: FjgcgJPylkV7EeQJjea_EeifPwaHVO9onD3ATk3YYAyvjtMGu3dcDS0ejA
+
+```
+***For Example :***
+
+📂 app.config.js
+```js
+// Database configuration Only Basic & Sequelize (needed Hash)
+
+...
+
+database_config: [
+  {
+    dialect: "mysql",
+    name: "mysql_my_store_db",
+    host: "localhost",
+    username: "m42BVxQ6Q4kLdRX7xS_Hm7WbQiNqShJDvw9SLCgI431oafWBtQJoJDnoCL",
+    password: "FjgcgJPylkV7EeQJjea_EeifPwaHVO9onD3ATk3YYAyvjtMGu3dcDS0ejA",
+    database: "my_store_db",
+    port: "3306",
+
+    // Specify global options, which are used when Define is called.
+    define: {
+      charset: "utf8",
+      freezeTableName: true,
+      ...
+    },
+
+    timezone: "+07:00", // Example: GMT+2
+    // or use a named timezone supported by Intl.Locale
+    // timezone: 'America/Los_Angeles',
+
+    logging: console.log, // SQL trace logs. Learn more: https://sequelize.org/docs/v6/getting-started/#logging
+
+    is_connect: true, // Boolean, Turn ON/OFF to connect
+  },
+
+  ...
+
+],
+
+...
+```
+❓ **Caution! :**  Every re-new generate `app_key`. Must to new Hash your Access and change to ALL Database connections.
+
+❓ **Development** : You can add ```dev: true``` in ```main_config``` for a better experience.
+
+# Models
+
+The `models` keep the files of function(s) data managemnets for Retriving, Creating, Updating and Destroying (CRUD). for understanding you might make model name same your table name inside `src/models` folder.
+
+```sh
+$ beech make modelName --model
+```
+
+## # Model (Basic)
+
+  Basic model only support `MySQL` Raw Query format and freedom of your SQL query
+
+  ❓ **Note:**  The Basic pool engine it's not support auto Endpoints.
+
+
+***For example :***
+
+📂 models/Fruit.js
+```js
+module.exports = {
+
+  // Example basic function get data
+  getData() {
+
+    return {
+      id: 1,
+      name: "John Doe",
+    }
+
+  },
+
+  // Example basic function get data from MySQL table
+  getFruit() {
+
+    // calling Pool connection name by `mysql.default_db`
+    mysql.default_db.query("SELECT * FROM fruit", (err, results) => {
+
+      if (err) { throw err }
+      return results;
+
+    });
+
+  }
+
+};
+```
+
+## # Model (Sequelize)
+
+  Sequelize is a promise-based Node.js ORM tool for Postgres, MySQL, MariaDB, SQLite, Microsoft SQL Server, Oracle Database, Amazon Redshift and Snowflake’s Data Cloud. It features solid transaction support, relations, eager and lazy loading, read replication and more. <br/>You can learn more: [Sequelize docs](https://sequelize.org/docs/v6)
+  
+  You can asign more DataTypes, Learn more : [Sequelize docs](https://sequelize.org/docs/v6/core-concepts/model-basics/#data-types)
+
+  ❓ **Note:** When you generate a model it's create table structure for automatically for you.
+
+***For example :***
+
+📂 models/Fruit.js
+```js
+const { Schema } = require("beech-api");
+
+// Define table Schema with `Schema(sql.default_db)` connection name
+const Fruit = Schema(sql.default_db).define("fruit", {
+  fruit_id: {
+    field: "id", // Rename PK field to fruit_id Ref: `id` field in fruit table
+    type: DataTypes.INTEGER,
+    autoIncrement: true,
+    primaryKey: true
+  },
+  friut_uuid: {
+    field: "uuid",
+    type: DataTypes.STRING(100),
+    allowNull: true,
+    defaultValue: DataTypes.UUIDV4,
+  },
+  fruitName: DataTypes.STRING,
+  fruitQty: DataTypes.INTEGER,
+  fruitPrice: {
+    type: DataTypes.INTEGER,
+    allowNull: false, // Allow null feilds
+  },
+  sort: DataTypes.STRING,
+  createdAt: {
+    type: DataTypes.DATE,
+    allowNull: false,
+    defaultValue: DataTypes.NOW,
+  },
+  updatedAt: {
+    type: DataTypes.DATE,
+    allowNull: true,
+  },
+}, {
+  // Enables timestamps with createdAt and updatedAt
+  timestamps: true,
+  // Custom field names createdAt and updatedAt
+  createdAt: "createdAt",
+  updatedAt: "updatedAt",
+});
+
+Fruit.options = {
+  // Choose one for Allow magic generate default Endpoint (CRUD), It's like magic creating The endpoints for you (CRUD) ✨
+
+  // Option 1: Allow all methods
+  defaultEndpoint: true,
+
+   // Option 2: Allow with specific per methods
+  defaultEndpoint: {
+    GET: true,
+    POST: {
+      allow: true, // allow Auto-Endpoint
+      jwt: {
+        allow: true, // allow JWT
+        broken_role: [
+          { role: [1, 2] },
+        ],
+      },
+      // Rate Limit for POST
+      rate_limit: {
+        windowMs: 15 * 60 * 1000, // 15 minutes
+        limit: 100, // Limit each IP to 100 requests per `window` (here, per 15 minutes).
+        // store: ... , // Redis, Memcached, etc.
+        // See more: https://www.npmjs.com/package/express-rate-limit#Configuration
+      },
+      // Duplicate Request for POST
+      duplicate_request: {
+        expiration: 500, // Can't duplicate request for 5 milliseconds each IP requests per `window` (Disabled for Set expiration to 0 zero.)
+      },
+    },
+    PATCH: false,
+    DELETE: false,
+  },
+
+  limitRows: 100, // Limit rows default 100
+};
+
+// Example Finder by id (ORM), Learn more: https://sequelize.org/docs/v6/core-concepts/model-querying-finders/
+function exampleFindOneFruitById(id) {
+  return Fruit.findOne({ where: { id: id } });
+}
+
+// Example Raw Query with Model Instances. This allows you to easily map a query to a predefined model
+function exampleGetAllFruitWithModelInstance(id) {
+  return Fruit.query("SELECT * FROM fruit", {
+    model: Fruit, // When JOIN table needed register that table [Fruit, ...]
+    mapToModel: true // pass true here if you have any mapped fields
+  });
+}
+
+// Example Raw Query, Learn more: https://sequelize.org/docs/v6/core-concepts/raw-queries/
+function exampleGetAllFruit(id) {
+  return Fruit.query("SELECT * FROM fruit");
+}
+
+...
+
+// Export Schema, Function, ...
+module.exports = {
+  Fruit,
+  exampleFindOneFruitById,
+  exampleGetAllFruitWithModelInstance,
+  exampleGetAllFruit,
+  ...
+};
+```
+
+## Retrieving data with Query String
+
+Now you can add Query String with Conditional, Grouping and Ordering (Now Support Readonly for GET method)
+
+### ✨ That's cool! It's like magic Creating The Endpoints for you (CRUD) ✨
+
+<b style="font-size:12pt">For Example, Now!</b>, You can request to `/fruit` with methods GET, POST, PATCH and DELETE like this.
+
+| Efficacy |  Method  |        Endpoint        |    Body      | Mode    |
+|:---------|:---------|:-----------------------|:-------------|:--------|
+|  Create  |  POST    | /fruit                 |     { }      | Single  |
+|  Create  |  POST    | /fruit                 |     [ ]      | Bulk    |
+|  Read    |  GET     | /fruit                 |     No       | Fetch   |
+|  Read    |  GET     | /fruit/:limit/:offset  |     No       | Fetch   |
+|  Read    |  GET     | /fruit?someField=1     |     No       | Fetch   |
+|  Read    |  GET     | /fruit?orderby=sort    |     No       | Fetch   |
+|  Read    |  GET     | /fruit?groupby=id      |     No       | Fetch   |
+|  Update  |  PATCH   | /fruit/:id             |     { }      | Single  |
+|  Delete  |  DELETE  | /fruit/:id             |     No       | Single  |
+
+Add some Basic Conditions, Grouping and Ordering with `QUERY STRING` under GET methods<br/>
+
+Retrieving `fruit` data with GET : `/fruit?someField=[eq,1]&groupby=[id]&orderby=[id,desc]`
+
+***For Example :***
+
+```java
+// WHERE Conditions
+GET: /fruit?id=1                       // id = 1
+GET: /fruit?isActived=[eq,1]           // isActived = 1
+GET: /fruit?fruitName=[like,Banana%]   // fruitName LIKE 'Banana%' (Not allow with date, time)
+GET: /fruit?cost=[gt,50]&qty=[lt,10]   // cost > 50 AND qty < 10
+GET: /fruit/10/0?qty=[lt,10]           // qty < 10 LIMIT 0,10
+
+// Grouping
+GET: /fruit?groupby=id                 // GROUP BY id
+GET: /fruit?groupby=[id,fruitName]     // GROUP BY id, fruitName
+
+// Ordering
+GET: /fruit?oderby=id                  // ORDER BY id ASC
+GET: /fruit?oderby=[sort,desc]         // ORDER BY sort DESC
+```
+
+For usage avariable:
+
+```java
+// Basics conditions
+=3                                      // = 3
+=[eq,3]                                 // = 3
+=[ne,20]                                // != 20
+=[is,null]                              // IS NULL
+=[not,null]                             // IS NOT NULL
+=[or,[5,6]]                             // (someField = 5) OR (someField = 6) // Not support NULL value
+
+// Number comparisons conditions
+=[gt,6]                                 // > 6
+=[gte,6]                                // >= 6
+=[lt,10]                                // < 10
+=[lte,10]                               // <= 10
+=[between,[6,10]]                       // BETWEEN 6 AND 10
+=[between,["2025-01-01","2025-04-30"]]  // BETWEEN "2025-01-01" AND "2025-04-30"
+                                        // When assign Datetime format will only support field datatype is `Date`, `Datetime`, `Time`
+
+// OR You can assign Datetime like this.
+=[between,["2025-01-01 12:00:00","2025-04-30 15:00:00"]] // BETWEEN "2025-01-01 12:00:00" AND "2025-04-30 15:00:00"
+
+=[notBetween,[11,15]]                   // NOT BETWEEN 11 AND 15
+
+// Other operators conditions
+=[in,[1,2,3]],                          // IN [1, 2, 3]
+=[notIn,[1,2,3]],                       // NOT IN [1, 2, 3]
+=[like,"%Banana"]                       // LIKE '%Banana' (Freestyle LIKE)
+
+=[notLike,"Banana"]                     // NOT LIKE 'Banana'
+=[startsWith,"Banana"]                  // LIKE 'Banana%'
+=[endsWith,"Banana"]                    // LIKE '%Banana'
+=[substring,"Banana"]                   // LIKE '%Banana%'
+
+// Grouping
+groupby=id                              // GROUP BY id
+groupby=[id]                            // ORDER BY id
+groupby=[id,fruitName]                  // ORDER BY id, fruitName
+
+// Ordering
+oderby=id                               // ORDER BY id ASC (Basic usage default Ascending)
+oderby=[id,asc]                         // ORDER BY id ASC
+oderby=[id,desc]                        // ORDER BY id ASC
+oderby=[[id,desc],[sort,asc]]           // ORDER BY id DESC, sort ASC
+```
+
+## # Transactions
+
+Sequelize does not use transactions by default. However, for production-ready usage of Sequelize, you should definitely configure Sequelize to use transactions.
+
+Beech use Sequelize supports three ways of using transactions:
+
+- ### Way 1 - Disorganized transactions :
+```js
+// First, we start a transaction from your connection and save it into a variable
+const t = await Fruit.transaction();
+
+try {
+
+  // Then, we do some calls passing this transaction as an option:
+  const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
+  await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
+
+  // If the execution reaches this line, no errors were thrown.
+  // We commit the transaction.
+  await t.commit();
+
+} catch (error) {
+
+  // If the execution reaches this line, an error was thrown.
+  // We rollback the transaction.
+  await t.rollback();
+
+}
+```
+
+- ### Way 2 - Organized transactions :
+```js
+// First, we start a transaction from your connection and save it into a variable
+Fruit.transaction(async t => {
+  try {
+
+    // Then, we do some calls passing this transaction as an option:
+    const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
+    await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
+
+    // If the execution reaches this line, no errors were thrown.
+    // We commit the transaction.
+    await t.commit();
+
+  } catch (error) {
+
+    // If the execution reaches this line, an error was thrown.
+    // We rollback the transaction.
+    await t.rollback();
+
+  }
+});
+```
+
+- ### Way 3 - Transactions set Isolation levels :
+
+The possible [isolations levels](https://sequelize.org/docs/v6/other-topics/transactions/#isolation-levels) to use when starting a transaction:
+
+```js
+const { Transaction } = require('sequelize');
+
+// First, we start a transaction from your connection and save it into a variable
+Fruit.transaction(
+  {
+    isolationLevel: Transaction.ISOLATION_LEVELS.SERIALIZABLE,
+  },
+  async t => {
+    try {
+
+      // Then, we do some calls passing this transaction as an option:
+      const fruit = await Fruit.create({ fruitName: 'Banana', fruitQty: '5', }, { transaction: t });
+      await fruit.addSibling({ fruitName: 'Litle', fruitQty: '2', }, { transaction: t }); // Error function
+
+      // If the execution reaches this line, no errors were thrown.
+      // We commit the transaction.
+      await t.commit();
+
+    } catch (error) {
+
+      // If the execution reaches this line, an error was thrown.
+      // We rollback the transaction.
+      await t.rollback();
+
+    }
+});
+```
+
+# Endpoints
+
+The `endpoints` keep the endpoints basic request files currently support `GET`, `POST`, `PUT`, `PATCH` and `DELETE`.
+
+So, you might create new endpoints with constant `endpoint` object variable in `src/endpoints/` folder and file neme must be end with `-endpoints.js`
+
+```sh
+$ beech make endpointName
+```
+You might using [special] `-R, --require` for choose Model(s) used for that endpoint.
+
+❓ **Note:** If you generate Endpoint Name same Auto-Endpoint it's Override to main Auto-Endpoint to you, (You always have priority).
+
+***For Example :***
+
+📂 endpoints/fruit-endpoints.js
+```js
+// Require Model schema, Function & Others
+const { Fruit } = require("@/models/Fruit");
+
+exports.init = () => {
+
+  // GET method
+  endpoint.get("/fruit", Credentials, async (req, res) => {
+    // example call Fruit model for get data
+    res.json({
+      code: 200,
+      status: "SUCCESS",
+      results: await Fruit.findAll();
+    });
+  });
+
+
+  // POST method
+  endpoint.post("/fruit", Credentials, (req, res) => {
+    // @response
+    res.json({
+      code: 200,
+      status: "SUCCESS",
+      message: "POST request at /fruit",
+      result: {
+        id: req.body.id,
+        name: req.body.name,
+      },
+    });
+  });
+
+
+  // PUT method
+  endpoint.put("/fruit/:id", Credentials, (req, res) => {
+    // @response
+    res.json({
+      code: 200,
+      status: "SUCCESS",
+      message: "PUT request at /fruit/" + req.params.id,
+    });
+  });
+
+
+  // DELETE method
+  endpoint.delete("/fruit/:id", Credentials, (req, res) => {
+    // @response
+    res.json({
+      code: 200,
+      status: "SUCCESS",
+      message: "DELETE request at /fruit/" + req.params.id,
+    });
+  });
+
+  ...
+
+}
+```
+
+# JWT Broken Role
+
+The **JWT Broken Role** mechanism provides a flexible way to bypass or override role-based authorization rules when using JWT.
+
+#### It can be applied in three different levels, depending on your use case.
+
+| Priority | Level 	                         | Scope                    | Best For                        |
+|:---------|:--------------------------------|:-------------------------|:--------------------------------|
+| 3rd      | Global (``passport.config.js``) | All endpoints            |	Common authorization exceptions |
+| 2nd      | Model-level options             |	Per model & HTTP method |	Structured, reusable rules      |
+| 1st      | Endpoint middleware             |	Single endpoint	        | Custom or special cases         |
+
+This multi-layer approach allows you to design **secure, flexible, and maintainable JWT authorization flows**.
+
+### 1. Global Configuration (passport.config.js) - Priority 3
+
+You can define global JWT Broken Role rules that apply to all endpoints by configuring them in ``passport.config.js``.
+```js
+module.exports = {
+  // Enable JWT authentication
+  jwt_allow: true,
+
+  ...
+
+  // Global JWT broken role configuration
+  jwt_broken_role: [
+    {
+      role: [0, 2, 4],
+      email: "john.doe@company.com",
+    }, // Basic role matching
+
+    {
+      role: { $in: [0, 2, 4] },
+      email: { $regex: /@company\.com$/ },
+    }, // Advanced matching using operators
+  ],
+
+  ...
+};
+```
+
+**Use cases**
+
+- Apply common authorization exceptions across the entire application
+- Support both simple role arrays and advanced operators (``$in``, ``$regex``, etc.)
+
+### 2. Model-Level Configuration (Per HTTP Method) - Priority 2
+
+You can configure JWT and Broken Role rules per model and per HTTP method using model options.
+
+📂 src/models/Fruit.js
+```js
+Fruit.options = {
+  ...
+
+  // Auto-endpoint configuration by HTTP method
+  defaultEndpoint: {
+    GET: true, // Enable auto-generated GET endpoint
+
+    POST: {
+      allow: true,
+      jwt: {
+        allow: true,
+        broken_role: [
+          { role: [5, 6] },
+        ],
+      },
+    },
+
+    PATCH: {
+      allow: true,
+      jwt: {
+        allow: true,
+        broken_role: [
+          { role: [5, 6, 9] },
+          { department: "IT" },
+        ],
+      },
+    },
+
+    DELETE: false, // Disable auto-generated DELETE endpoint
+  },
+
+  ...
+};
+```
+
+**Use cases**
+
+- Fine-grained access control per HTTP method
+- Different role requirements for POST, PATCH, etc.
+- Combine role-based and attribute-based conditions
+
+### 3. Endpoint-Level Configuration (Credentials Middleware) - Priority 1
+
+For maximum flexibility, you can define Broken Role rules directly on a specific endpoint using the Credentials middleware.
+
+📂 endpoints/custom-fruit-endpoints.js
+```js
+const { Fruit } = require("@/models/Fruit");
+
+endpoint.delete(
+  "/destroy-fruit-by-id/:id",
+  Credentials([{ role: [5, 9] }]),
+  async (req, res) => {
+
+    // Only JWT tokens with role level 5 or 9 are allowed
+
+    const deleted = await Fruit.destroy({
+      where: {
+        id: req.params.id,
+      },
+    });
+
+    console.log("result:", deleted);
+
+    // @response
+  }
+);
+```
+
+**Use cases**
+
+- One-off or custom endpoints
+- Highly specific authorization rules
+- Override global or model-level behavior when necessary
+
+## Supported Basic & Operators Usage
+
+The JWT Broken Role system supports both basic value matching and advanced operators for flexible authorization rules.
+
+| Operator | Meaning            | Description                                                   |
+|:---------|:-------------------|:--------------------------------------------------------------|
+| $eq      | equal              | Matches when the value is equal                               |
+| $ne      | not equal          | Matches when the value is not equal                           |
+| $in      | value IN array     | Matches when the value exists in the specified array          |
+| $not     | value NOT IN array | Matches when the value does not exist in the specified array  |
+| $regex   | regex match        | Matches using a regular expression                            |
+| $fn      | custom function    | Matches using a custom evaluation function                    |
+
+## Evaluation Logic (Very Important !)
+```js
+[
+  { rule1 AND rule1 },
+  { rule2 AND rule2 }
+]
+        ⬇
+        OR
+```
+
+## Basic Usage for Examples :
+
+```js
+Credentials([
+  { role: [9] },         // Only role check
+  { email: 'a@b.com' },  // OR email
+])
+
+// Common Matching Patterns
+{ role: [1, 2, 3] }     // IN
+{ role: 1 }             // Equal
+{ email: 'a@b.com' }    // Equal
+{ department: 'IT' }    // Equal
+{ status: ['active'] }  // Dynamic key
+```
+
+## Operators Usage for Examples :
+
+```js
+// Equal with Role
+Credentials([
+  {
+    role: { $eq: [1, 2, 5] }
+  }
+])
+
+// Not Equal with Role
+Credentials([
+  {
+    role: { $ne: [0, 3] }
+  }
+])
+
+// Regex with Email domain
+Credentials([
+  {
+    email: { $regex: /@company\.com$/ }
+  }
+])
+
+// IN with Role
+Credentials([
+  {
+    role: { $in: [1, 2, 4] }
+  }
+])
+
+// NOT IN with Role
+Credentials([
+  {
+    role: { $not: [0, 3] }
+  }
+])
+
+// Multiple OR rules
+Credentials([
+  {
+    role: { $in: [1] },
+    email: 'john.doe@company.com'
+  },
+  // OR
+  {
+    role: { $in: [4] },
+    email: { $regex: /@company\.com$/ }
+  },
+])
+
+// Custom Function
+Credentials([
+  {
+    role: {
+      $fn: (value, user) => value >= 4 && user.department === 'IT'
+    }
+  }
+])
+```
+
+# Helpers
+
+The `helpers` keep the files of functions for process specific something in the project. So, you might create the `helpers` in path `src/helpers` folder.
+
+```sh
+$ beech make helperName --helper
+```
+
+***For Example :***
+
+📂 helpers/TextEditor.js
+```js
+module.exports = {
+
+  textUpperCase(text) {
+    return text.toUpperCase();
+  },
+  
+  textTrim(text) {
+    return text.trim();
+  },
+
+  ...
+
+};
+```
+
+# Authentication (passport-jwt)
+
+Passport is authentication middleware for Node. It is designed to serve a singular purpose: authenticate requests. When writing modules, encapsulation is a virtue, so Passport delegates all other functionality to the application. This separation of concerns keeps code clean and maintainable, and makes Passport extremely easy to integrate into an application.
+
+### Passport-jwt Initialization
+
+```sh
+$ beech passport init
+```
+
+After passport initialized the `passport.config.js` it's appeared
+
+📂 passport.config.js
+```js
+module.exports = {
+  // Allow for using passport-jwt
+  jwt_allow: true,
+
+  // custom authenticaiton endpoint name, default `/authentication`
+  auth_endpoint: "",
+
+  // your jwt secret key
+  secret: "your_jwt_secret",
+
+  // token expiry time (seconds), default 86400 sec. it's expired in 24 hr.
+  token_expired: 86400,
+
+  // Allow for using global jwt broken role
+  jwt_broken_role: [
+    // { role: [1, 2, 9] },
+  ],
+
+  model: {
+    // Main sql connection name. You must make sure connection name like inside `app.config.js` file and choose one connection name.
+    name: "default_db",
+
+    // table name of users store, default table `users`
+    table: "",
+
+    // secret user store field for authenticate, default field `username` and `password`
+    username_field: "",
+    password_field: "",
+
+    // JWT playload data, You can add it. Example: ["name", "email", ...]
+    fields: [],
+
+    // Other fields add for authentication.
+    guard: {
+      // Basic guard field, Example: ["pin", "hint", "2fa"]
+      guard_field: [],
+
+      // Advanced guard jwt request (needed some logical from front-end)
+      advanced_guard: {
+        allow: false,
+        entity: "", // default entity `timing`
+        secret: "top_secret",
+        time_expired: {
+          minutes: 1, // should length [0-60]
+          seconds: 0, // should length [0-60]
+        },
+      },
+    },
+  },
+
+  // Allow for using request with app_key entity (Every request must be using the app_key entity in headers)
+  app_key_allow: false
+
+  ...
+
+};
+```
+### Request Token
+**Authentication structure :** Simple ``users`` table:
+```
+==============================================================
+|  id  |  username | password |     name     |     email     |
+--------------------------------------------------------------
+|  1   |  bombkiml |  secret  | bombkiml NC. | bomb@bomb.com |
+|  2   |  johnson  |  secret  | johnson BA.  | john@bomb.com |
+```
+
+When you config passport with ```users``` table already. You will got Auth endpoint in available.
+```js
+POST:  "/authentication"               // Request token
+POST:  "/authentication/refresh"       // Request refresh token
+POST:  "/authentication/create"        // Create new Auth data
+PATCH: "/authentication/update/:id"    // Update old Auth data (needed user id)
+```
+
+***XHR Example :***
+
+```js
+// Request with body for gether Token
+POST: "/authentication"
+payload: {
+  username: "bombkiml",
+  password: "secret"
+}
+
+// Request with header for refresh token
+POST: "/authentication/refresh"
+headers: Authorization: Bearer <your_token>
+
+// Request with body for Create Auth data
+POST: "/authentication/create"
+payload: {
+  username: "add_new_username",
+  password: "add_new_secret",
+  name: "add_new_my_name",
+  email: "add_new_email"
+}
+
+// Request with body for Update Auth data
+PATCH: "/authentication/update/1"
+headers: Authorization: Bearer <your_token>
+payload: {
+  username: "update_bombkiml",
+  password: "update_secret",
+  name: "update_my_name",
+  email: "my_update_email@bomb.com"
+}
+```
+
+# Beech Guard
+You can easy using 2 Factor authenticate with ```guard_field``` inside ```passport.config.js``` file and add your Guard field ex: ```2fa``` field for Authenticate Conditions.
+
+## # Guard (2FA, Other)
+
+📂 passport.config.js
+```js
+module.exports = {
+  ...
+
+  guard: {
+    // Other fields add for authenticate, exmaple ["pin", "hint", "2fa"]
+    guard_field: ["2fa"], 👈 // your feild guard. (Disabled to remove it.)
+
+    ...
+  },
+
+  ...
+
+}
+```
+
+## # Beech Advanced Guard (Timing)
+Advance Guard for Protection your Endpoint with Timing. You can allow in object ```advance_guard``` inside ```passport.config.js``` file. So let's go add your Advance Guard Configuration.
+
+📂 passport.config.js
+```js
+module.exports = {
+  ...
+
+  guard: {
+    ...
+
+    // Advanced guard to Request (Needed some logical from front-end)
+    advanced_guard: {
+      allow: false, 👈 // advanced guard allow for All Endpoint.
+      entity: "", // default entity `timing`
+      secret: "your_advance_guard_secret",
+      time_expired: {
+        minutes: 1, // should length [0-60]
+        seconds: 0, // should length [0-60]
+      },
+    },
+  },
+
+  ...
+
+}
+
+```
+
+<b>After configure</b>, You must add some logic in your front-end like this.
+
+Before add logic, We needed [```beech-auth0```](https://github.com/bombkiml/beech-auth0) and [```moment.js```](https://momentjs.com) for apply in Policy.
+
+```sh
+# NPM
+$ npm install --save beech-auth0 moment
+
+# Yarn
+$ yarn add beech-auth0 moment
+```
+Now! you can add some logic like this.
+
+ - Import packages
+
+```js
+// CommonJS
+const { Auth0 } = require("beech-auth0");
+const moment = require("moment");
+
+// ES6
+import { Auth0 } from "beech-auth0";
+import moment from "moment";
+```
+
+- Get unix time with momentJS
+
+```js
+// Get UNIX TIME with moment
+let unix_time = moment().unix();
+```
+
+- Get hashing with Beech Auth0
+
+```js
+// Auth0 Policy.
+Auth0(unix_time, 'your_advance_guard_secret', (error, hashing) => {
+
+  // Your XHR request for All Endpoint.
+  POST: "/authentication"
+  headers: { timing: hashing } 👈 // Assign advance guard entity to headers with callback hashing.
+
+});
+
+```
+
+## # Beech User Authentication Managements ###
+You can easy management `users` data with Beech, Only ```Store, Update``` NO ```Delete```, Anything you can make DELETE endpoint by yourself
+
+```js
+const { Store, Update } = require("beech-api");
+```
+
+- ***Store*** users data with ``Store()``
+```js
+// prepare data for store users
+var data = {
+  username: "bombkiml",
+  password: "secret",
+  name: "bombkiml nc.",
+  email: "bomb@bomb.com"
+}
+
+Store(data, (err, stored) => {
+  if (err) throw err;
+  
+  // response affected data
+  console.log(stored.insertId, stored.affectedRows);
+
+});
+```
+
+- ***Update*** users data with ``Update()``
+```js
+// prepare data for update users
+var data = {
+  password: "new_secret",
+  name: "bombkiml NC.",
+  email: "bombkiml@bomb.com"
+}
+
+Update(data, id, (err, updated) => {
+  if (err) throw err;
+
+  // response affected data
+  console.log(updated.updateId, updated.affectedRows);
+
+});
+```
+
+# Beech with Official Strategy
+
+Latest supported with ``Google`` and ``Facebook`` Strategy.
+
+
+## # Google Strategy
+
+
+The Google OAuth 2.0 authentication strategy authenticates users using a Google account and OAuth 2.0 tokens. The strategy requires a verify callback, which accepts these credentials and calls done providing a user, as well as options specifying a client ID, client secret, and callback URL.
+
+Before your application can make use of Sign In With Google, you must register your app with Google. This can be done in the [APIs & Services](https://console.cloud.google.com/apis) page of the [Google Cloud Platform console.](https://console.cloud.google.com/) Once registered, your app will be issued a client ID and secret which will be used in the strategy configuration.
+
+Go to open file ``passport.config.js`` and go to ``google strategy`` then turn allow Google Strategy is ``allow: true`` something like this.
+
+📂 passport.config.js
+```js
+...
+
+strategy: {
+
+  google: {
+
+    // Allow for using google strategy
+    allow: true,
+
+    // Authen profile store fields available: `google_id`, `name`, `email`, `photos`, `locate`
+    local_profile_fields: {
+      google_id: "google_id", // Google ID field, default field name: `google_id`
+      name: "your_name_field",
+      email: "your_email_field",
+      photos: "your_profile_url_field",
+      locate: "" // If you not store set to null or remove it.
+    },
+    // Google development Credentials OAuth 2.0 Client IDs
+    client_id: "GOOGLE_CLIENT_ID",
+    client_secret: "GOOGLE_CLIENT_SECRET",
+    // Callback endpoint default `/google/callback`
+    callbackURL: "",
+    // Failure redirect to your route
+    failureRedirect: "/login"
+  }
+}
+
+...
+```
+
+The above code is a configures and registers the Google Strategy.
+
+- ``allow`` : Turn on/off the Google Strategy config type of ``boolean`` switch by ``true/false``.
+- ``google_id`` : Local Google ID field for store Google ID in my local database default field is ``google_id``.
+- ``local_profile_fields`` : Local Profile fields for store Google user details.
+- ``client_id`` and ``client_secret`` : The options to the Google Strategy constructor must include a ``clientID`` and ``clientSecret``, the values of which are set to the client ID and secret that were obtained when registering your application.
+- ``callbackURL`` : When registering your application. A callbackURL must also be included. Google will redirect users to this location after they have authenticated.
+- ``failureRedirect`` : When registering your application somthing failure it's redirect to that.
+
+Place a button on the application's login page, prompting the user to sign in with Google.
+
+```html
+<a href="/authentication/google" class="button">Sign in with Google</a>
+```
+
+❓ **Note:** The URL "``/authentication``" will be follow by ``auth_endpoint`` when you custom it.
+
+
+## # Facebook Strategy
+
+
+Facebook Login allows users to sign in using their Facebook account. Support for Faceboook Login is provided by the ``passport-facebook`` package.
+
+Before your application can make use of Facebook Login, you must register your app with Facebook. This can be done in the [App dashboard](https://developers.facebook.com/apps) at [Facebook for Developers.](https://developers.facebook.com/) Once registered, your app will be issued an app ID and secret which will be used in the strategy configuration.
+
+Go to open file ``passport.config.js`` and go to ``facebook strategy`` then turn allow Facebook Strategy is ``allow: true`` something like this.
+
+📂 passport.config.js
+```js
+...
+
+strategy: {
+
+  facebook: {
+
+    // Allow for using facebook strategy
+    allow: true,
+
+    // Authen profile store fields available: `facebook_id`, `name`, `email`, `photos`, `locate`
+    local_profile_fields: {
+      facebook_id: "facebook_id", // Facebook ID field, default field name: `facebook_id`
+      name: "your_name_field",
+      email: "your_email_field",
+      photos: "your_profile_url_field",
+      locate: "" // If you not store set to null or remove it.
+    },
+    // Facebook development Credentials OAuth 2.0
+    app_id: "FACEBOOK_APP_ID",
+    app_secret: "FACEBOOK_APP_SECRET",
+
+    // You can allow Permissions facebook profile fields. Learn more (https://developers.facebook.com/docs/graph-api/reference/v13.0/user#readperms)
+    // **Update 2024, Now! Facebook requests permission for show Email. Learn more (https://developers.facebook.com/docs/permissions)
+    profileFieldsAllow: [ 'id', 'displayName', 'name', 'photos', 'email', 'location' ], // Default allowed
+
+    // Callback endpoint default `/facebook/callback`
+    callbackURL: "",
+    // Failure redirect to your route
+    failureRedirect: "/login"
+  }
+}
+
+...
+```
+
+The above code is a configures and registers the Facebook Strategy.
+
+- ``allow`` : Turn on/off the Facebook Strategy config type of ``boolean`` switch by ``true/false``.
+- ``facebook_id`` : Local Facebook ID field for store Facebook ID in my local database default field is ``facebook_id``.
+- ``local_profile_fields`` : Local Profile fields for store Facebook user details.
+- ``app_id`` and ``app_secret`` : The options to the Facebook Strategy must include an app ID and secret. you must register your app with Facebook. This can be done in the [App dashboard](https://developers.facebook.com/apps) at [Facebook for Developers.](https://developers.facebook.com/) Once registered, your app will be issued an ``app ID`` and ``secret`` which will be used in the strategy configuration.
+- ``profileFieldsAllow`` : Permissions with Facebook Login. You must allow Permissions facebook profile fields: see more (https://developers.facebook.com/docs/graph-api/reference/v13.0/user#readperms)
+- ``callbackURL`` : When registering your application. A callbackURL must also be included. Facebook will redirect users to this location after they have authenticated.
+- ``failureRedirect`` : When registering your application somthing failure it's redirect to that.
+
+Place a button on the application's login page, prompting the user to sign in with Facebook.
+
+```html
+<a href="/authentication/facebook" class="button">Log In With Facebook</a>
+```
+
+❓ **Note:** The URL "``/authentication``" will be follow by ``auth_endpoint`` when you custom it.
+
+# CORS Origin & Server Configuration
+The origin array to the callback can be any value allowed for the origin option of the middleware. Certain CORS requests are considered `complex` and require an initial OPTIONS request (called the `pre-flight request`). You can allowed CORS origin inside file `beech.config.js`
+
+📂 beech.config.js
+```js
+module.exports = {
+  defineConfig: {
+    // Base public path when served in development or production.
+    base: process.env.NODE_ENV === "production"
+          ? "/my-api/" // For Production
+          : "/", // For Development
+
+    server: {
+      // Client request allow origin whitelist
+      origin: ["http://example.com", "http://my-webapp:8080", "https://cat.io"],
+      originSensitive: false, // Sensitive with contrasts wording
+
+      // API Request rate limit (Disabled for Remove it.)
+      rateLimit: {
+        windowMs: 15 * 60 * 1000, // 15 minutes
+        limit: 100, // Limit each IP to 100 requests per `window` (here, per 15 minutes).
+        // store: ... , // Redis, Memcached, etc.
+        // See more: https://www.npmjs.com/package/express-rate-limit#Configuration
+      },
+
+      // API Duplicate Request (Disabled for Set expiration to 0 zero.)
+      duplicateRequest: {
+        expiration: 500, // Can't duplicate request for 5 milliseconds each IP requests per `window`
+      },
+
+      payload: {
+        // The limit of request body size, json default "100KB", urlencoded default "100KB". Learn more: https://expressjs.com/en/4x/api.html#express.json
+        json: {
+          limit: "100KB", // default: "100KB"
+        },
+        urlencoded: {
+          limit: "100KB", // default: "100KB"
+          extended: true, // default: true (reccomended: true)
+        },
+        file: {
+          uploadAllowMethod: ["POST", "PATCH", "PUT"], // Only apply file upload limit for POST, PATCH, PUT method.
+          allowedTypes: ["image/jpeg", "image/png", "application/pdf"], // Example: Allow only JPEG, PNG, and PDF files. Learn more: https://www.digipres.org/formats/mime-types/
+          limit: 5 * 1024 * 1024, // 5MB (default: Infinity)
+        },
+      },
+
+    },
+  },
+}
+```
+
+❓ **Note:** When you must to allowed all Origin. You can assign `*` or `[]` null value to `origin` variable.
+
+## # Custom Endpoint Specific Rate Limit
+When you need assign specific request Endpoint with [express-rate-limit](https://www.npmjs.com/package/express-rate-limit), You can managemnet with Beech object ```rateLimit``` for your custom Rate Limit like this.
+
+```js
+const { rateLimit } = require("beech-api").Express;
+
+// Specific of your rate limit
+const specificRateLimit1 = rateLimit({
+  windowMs: 5 * 60 * 1000, // 5 minutes
+  limit: 20,
+  // more...
+});
+
+// Your Endpoints...
+endpoint.get("/banana", specificRateLimit1, (req, res) => {
+  ...
+});
+
+...
+```
+
+## # Custom Endpoint Specific Slow Down
+**DON'T DO IT.** &nbsp; Because it's annoying to users.
+
+When you need assign specific request Endpoint with [express-slow-down](https://www.npmjs.com/package/express-slow-down), You can managemnet with Beech object ```slowDown``` for your custom Slow Down like this.
+
+```js
+const { slowDown } = require("beech-api").Express;
+
+// Specific of your slow down
+const specificSlowDown1 = slowDown({
+  windowMs: 15 * 60 * 1000,      // 15 minutes
+  delayAfter: 5,                 // Allow 5 requests per 15 minutes.
+  delayMs: (hits) => hits * 100, // Add 100 ms of delay to every request after the 5th one.
+  // more...
+  
+  /**
+   * So:
+   *
+   * - requests 1-5 are not delayed.
+   * - request 6 is delayed by 600ms
+   * - request 7 is delayed by 700ms
+   * - request 8 is delayed by 800ms
+   *
+   * and so on. After 15 minutes, the delay is reset to 0.
+   */
+});
+
+// Your Endpoints...
+endpoint.get("/banana", specificSlowDown1, (req, res) => {
+  ...
+});
+
+...
+```
+
+## # Custom Endpoint Specific Duplicate Request
+This middleware to Limit each IP duplicated requests per window.
+
+When you need assign specific request Endpoint with duplicate request use [express-duplicate-request](https://github.com/bombkiml/express-duplicate-request), You can managemnet with Beech object ```duplicateRequest``` for your custom Duplicate Request like this.
+
+```js
+const { duplicateRequest } = require("beech-api").Express;
+
+// Specific of your duplicate request
+const specificDup1 = duplicateRequest({
+  expiration: 500, // Can't duplicate request for 5 milliseconds, Should 0 to disabled
+  // more...
+});
+
+// Your Endpoints...
+endpoint.get("/banana", specificDup1, (req, res) => {
+  ...
+});
+
+...
+```
+
+# Databases managements
+
+## # Migrations & Seeder
+
+Just like you use Git / SVN to manage changes in your source code, you can use migrations to keep track of changes to the database. With migrations you can transfer your existing database into another state and vice versa: Those state transitions are saved in migration files, which describe how to get to the new state and how to revert the changes in order to get back to the old state.
+
+You will need [Sequelize CLI.](https://github.com/sequelize/cli) The CLI ships support for [migrations](https://sequelize.org/v5/manual/migrations.html) and project.
+
+## # Usage
+
+To create an empty project you will need to execute `init` command
+
+```sh
+$ npx sequelize-cli init
+```
+
+This will create following folders inside `databases` folder.
+
+- `config`, contains config file, which tells CLI how to connect with database.
+- `models`, contains all models for your project.
+- `migrations`, contains all migration files.
+- `seeders`, contains all seed files.
+
+## # Configuration
+
+Before continuing further we will need to tell CLI how to connect to database. To do that let's open default config file `databases/config/database.json` It looks something like this:
+
+```json
+{
+  "development": {
+    "username": "root",
+    "password": null,
+    "database": "database_development",
+    "host": "127.0.0.1",
+    "port": 3306, // IF your another port
+    "dialect": "mysql"
+  },
+  "test": {
+    "username": "root",
+    "password": null,
+    "database": "database_test",
+    "host": "127.0.0.1",
+    "dialect": "mysql"
+  },
+  "production": {
+    "username": "root",
+    "password": null,
+    "database": "database_production",
+    "host": "127.0.0.1",
+    "dialect": "mysql"
+  }
+}
+```
+
+❓ **Note:** The database connect default port 3306 if you another port you can add object ``port`` in config.
+
+❓ **Note:** If your database doesn't exists yet, you can just call `npx sequelize-cli db:create` command. With proper access it will create that database for you.
+
+## # Creating first Migrations
+
+Create `model` use `model:generate` command. This command requires two options.
+
+- `--name`, Name of the model
+- `--attributes`, List of model attributes
+
+Let's create a model name example `User`. See more about of [Datatypes](https://sequelize.org/v5/manual/data-types.html)
+
+```sh
+$ npx sequelize-cli model:generate --name User --attributes firstName:string,lastName:string,email:string,birhday:date
+```
+
+## # Migrations Up and Down
+
+Until this step, we haven't inserted anything into the database. We have just created required model and migration files for our first model User.
+
+- **Migrate Up** : you can create that table in database you need to run db:migrate command.
+
+  ```sh
+  $ npx sequelize-cli db:migrate
+  ```
+
+- **Migrate Down** : you can use `db:migrate:undo`, this command will revert most recent migration.
+  ```sh
+  // Step to undo
+  $ npx sequelize-cli db:migrate:undo
+
+  // All to undo
+  $ npx sequelize-cli db:migrate:undo:all
+
+  ```
+
+## # Creating First Seeder
+
+To manage all data migrations you can use seeders. Seed files are some change in data that can be used to populate database table with sample data or test data.
+
+Let's create a seed file which will add a demo user to our User table.
+
+```sh
+$ npx sequelize-cli seed:generate --name user
+```
+
+## # Seeder Up and Down
+
+In last step you have create a seed file. It's still not committed to database. To do that we need to run a simple command.
+
+- **Seed Up** : you can execute that seed file and you will have a user inserted into `User` table.
+
+  ```sh
+  $ npx sequelize-cli db:seed:all
+  ```
+
+- **Seed Down** : seeders can be undone if they are using any storage. There are two commands available for that:
+
+  If you wish to undo most recent seed
+
+  ```sh
+  $ npx sequelize-cli db:seed:undo
+  ```
+
+  If you wish to undo a specific seed
+
+  ```
+  $ npx sequelize-cli db:seed:undo --seed <seederName>
+  ```
+
+  If you wish to undo all seeds
+
+  ```sh
+  $ npx sequelize-cli db:seed:undo:all
+  ```
+
+# Testing
+
+Test using [Jest](https://jestjs.io/en/) for testing the project. Jest is a delightful JavaScript Testing Framework with a focus on simplicity. Learn more [Jest docs](https://jestjs.io/docs/en/getting-started.html)
+
+So, When you make the new endpoints it's automatic create test file end with `.spec.js` in `__test__` folder with constant `baseUrl` variable and `axios` package.
+
+***For Example :***
+
+📂 \_\_test\_\_/unit/endpoints/fruit-endpoints.spec.js
+```js
+const endpoint = baseUrl.concat("/fruit");
+
+describe("Test endpoint : " + endpoint, () => {
+  it("Truthy!", () => {
+    expect("/fruit").toBeTruthy();
+  });
+
+  it("Respond with basic GET status code 200", (done) => {
+    axios.get(endpoint).then((res) => {
+      expect(200).toEqual(res.data.code);
+      done();
+    });
+  });
+});
+```
+
+# Building for Production
+
+The Beech API build system is designed to secure your source code without sacrificing performance.
+
+To start the build process, run the following command from your project root
+
+```sh
+$ npm run build
+# OR
+$ yarn build
+```
+
+❓ **Note:** This command triggers ```beech-service build``` as defined in your package.json.
+
+### # What happens during Build ?
+The build engine performs the following automated steps:
+
+- **Scanning**: It scans for all .js files in src/ (endpoints, models, helpers) and configuration files.
+
+- **Entry Point Generation**: It retrieves the core engine template (beech.txt) and converts it into a secured server.js in the output folder.
+
+- **Compilation**: Files are minified to reduce size.
+
+- **Obfuscation**:
+
+  - Variables and function names are renamed.
+  - Strings are Base64 encoded.
+  - Performance remains 100% because control-flow logic is preserved.
+
+- **Distribution**: All protected files are placed in the ```./dist``` directory.
+
+### # Deployment Structure ?
+After the build is complete, your ./dist folder will look like this:
+
+```sh
+dist/
+├── src/
+│   ├── endpoints/    (Obfuscated)
+│   ├── models/       (Obfuscated)
+│   ├── helpers/      (Obfuscated)
+│   └── etc/          (Obfuscated)
+├── server.js         (Main entry point)
+├── app.config.js     (Obfuscated)
+├── beech.config.js   (Obfuscated)
+├── global.config.js  (Obfuscated)
+└── package.json      (Copied for dependency management)
+```
+
+## # Starting the Production Server ?
+To run your application in production:
+
+- Upload the contents of the dist folder to your server.
+
+- Install only production dependencies:
+  ```sh
+  npm install --production
+  ```
+
+# Implementation
+
+## # Implement with [Docker](https://www.docker.com)
+
+[Docker](https://www.docker.com) is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly.
+
+- ### **Create Dockerfile**
+
+Docker builds images automatically by reading the instructions from a Dockerfile -- a text file that contains all commands, in order, needed to build a given image. A Dockerfile adheres to a specific format and set of instructions which you can find at [Dockerfile reference](https://docs.docker.com/engine/reference/builder/).
+
+📂 Dockerfile
+```js
+FROM node:18-alpine
+ENV NODE_ENV=production
+WORKDIR /usr/src/api
+COPY ["package.json", "package-lock.json*", "./"]
+RUN npm install --production --silent && mv node_modules .
+COPY . .
+EXPOSE 9000
+CMD ["node", "server.js"]
+```
+
+- ### **Docker build image**
+
+The docker build command builds an image from a Dockerfile and a context. The build’s context is the set of files at a specified location ```PATH``` or ```URL```. The PATH is a directory on your local filesystem. The URL is a Git repository location.
+
+```sh
+$ docker build -t <imageName> .
+```
+
+❓ **Note:** You can specify a repository and tag at which to save the new image : ``` $ docker build -t <imageName>:<tags> . ```
+
+- ### **Run docker**
+
+  After create ``image`` you can run docker engine following :
+
+  - ### **Docker Container (Standalone)**
+  ```sh
+  $ docker run -d -p 9000:9000 --name <containerName> <imageName>
+  ```
+
+  - ### **Create Docker Swarm (Cluster)**
+  ```sh
+  # Initiate swarm
+  $ docker swarm init
+  
+  # Run docker service
+  $ docker service create --replicas <instances> --name <containerName> --publish 9000:9000 <imageName>
+  ```
+
+## # Implement with [PM2](https://pm2.keymetrics.io/)
+[PM2](https://pm2.keymetrics.io/) is a daemon process manager that will help you manage and keep your application online. Getting started with PM2 is straightforward, it is offered as a simple and intuitive CLI, installable via [NPM](https://www.npmjs.com/).
+
+```sh
+# Start service as standalone
+$ pm2 start server.js --name <serviceName>
+
+# OR
+
+# Start service as cluster mode
+$ pm2 start server.js --name <serviceName> -i <instances>
+```
+
+# Development
+
+Want to contribute or join for great job!, You can contact to me via
+
+- GitHub: [bombkiml/beech-api - issues](https://github.com/bombkiml/beech-api/issues)
+- E-mail: nattapat.jquery@gmail.com
+- Facebook: [https://www.facebook.com/bombkiml](https://www.facebook.com/bombkiml)
+
+# License
+
+The Beech API framework is open-sourced software licensed under the [MIT license.](https://opensource.org/licenses/MIT)