Migrations in Laravel

Uthman Ehsan — Sat, 28 Sep 2024 12:17:11 +0000

Migrations are like version control for your database, allowing your team to define and share the application's database schema definition.

If you have ever had to tell a teammate to manually add a column to their local database schema after pulling in your changes from source control, you've faced the problem that database migrations solve.

*Making Migrations
*
One can generate migrations using below artisan commands

 php artisan make:migration create_multisignin_table

Laravel is smart enough to generate up and down functions under migrations folder with date and migration name under

 database/migrations/2023_09_28_create_multisign_table.php (File)

with auto code generated for up and down methods.

** Running Migrations
**
To run all of your outstanding migrations, execute the migrate Artisan command:

 php artisan migrate

If you created more migrations and they are not migrated yet, to run only a specific migration use this:

php artisan migrate --path=/database/migrations/2023_09_28_create_multisign_table.php

** Above migrations will only run if there is no entry before in the migrations table.**

*_ Check migrations table , if there is an entry for 2023_09_28_create_multisign_table than this particular migration
wont run at all even running either of above commands. *

In order to run the migration , one has to delete the entry from database manually and execute

 php artisan migrate:refresh

Happy Coding !

405 Error Laravel Sanctum

Uthman Ehsan — Sat, 28 Sep 2024 11:31:38 +0000

Laravel Sanctum provides a featherweight authentication system for SPAs (single page applications), mobile applications, and simple, token based APIs.

Sanctum allows each user of your application to generate multiple API tokens for their account.

However it differs from JWT tokens where the user information is encoded in a string and passed onto server every time request is sent back to server.

Whereas sanctum is more like a stateful session with limited or life time expiration. One can set the expiration under

config/sanctum.php  
'expiration' => null

One can guard or protect the the respective methods under guard configure that would need to send authentication token.

// Request the resource to get token 

Route::post('/users_new', [UserController::class, 'store']);

public users_new(){

   $user = User::create( $request->user_data );

   $token = $user->createToken('api-token')->plainTextToken;

   return response()->json([
               'token' => $token,
                'data' => $user,
            ], 200);
}

In order to update the user data , it will have to pass the token along with request.

Route::middleware('auth:sanctum')->group(function () {
  // all the requests coming inside this middleware will have to pass the token.

//User
Route::post('/updateUser', [UserController::class, 'upgradeUser']);

});

If above is executed , it might throw an 405 Authorization error because at this moment our webserver doesnot accepts
any header tokens . To achieve this we need to add below .**htaccess **file.

RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

(right after the RewriteBase) so our htaccess code
becomes

<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . index.php [L]
</IfModule>

If we need to test above in PostMan , one must add the BearerToken as HeaderAuthorization as depicted in below diagram.

Happy Coding !

Forem: Uthman Ehsan

Migrations in Laravel

405 Error Laravel Sanctum