[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-api-authentication":8,"blog-posts-latest:24":31,"blog-comments:23c9cf92-232b-460f-9825-a9c53e350600":323,"site-content":324},{"id":4,"accent_theme":5,"font_theme":6,"updated_at":7},1,"midnight","saas","2026-10-28T07:05:59.308034+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"content":13,"cover_image":14,"meta_title":15,"meta_description":16,"og_image":17,"tags":18,"status":25,"published_at":26,"view_count":27,"deleted_at":28,"deleted_reason":17,"created_at":29,"updated_at":30},"23c9cf92-232b-460f-9825-a9c53e350600","How to Use Laravel Sanctum for API Authentication — SPA Cookies & Tokens","laravel-api-authentication","Laravel Sanctum authenticates first-party SPAs with secure cookies and issues API tokens for mobile or third-party clients—without the complexity of full OAuth.","\u003Ch2>Quick Answer\u003C\u002Fh2>\n\u003Cp>Laravel Sanctum is the auth package most of us reach for when the API is Laravel and the client is our own SPA or a mobile app. Browsers get session cookies with CSRF protection. Apps and scripts get personal access tokens. You do not need Passport’s full OAuth stack unless third parties must “sign in with your API” in a formal OAuth way.\u003C\u002Fp>\n\n\u003Ch2>Quick Facts\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Topic:\u003C\u002Fstrong> Laravel Sanctum API Authentication\u003Cbr>\n\u003Cstrong>Category:\u003C\u002Fstrong> Backend \u002F Laravel Security\u003C\u002Fp>\n\n\u003Ch2>Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>What Is Laravel Sanctum?\u003C\u002Fli>\n\u003Cli>Why It Matters\u003C\u002Fli>\n\u003Cli>How It Works\u003C\u002Fli>\n\u003Cli>Step-by-Step Guide\u003C\u002Fli>\n\u003Cli>Real Example\u003C\u002Fli>\n\u003Cli>Pros &amp; Cons\u003C\u002Fli>\n\u003Cli>Best Practices\u003C\u002Fli>\n\u003Cli>Common Mistakes\u003C\u002Fli>\n\u003Cli>FAQs\u003C\u002Fli>\n\u003Cli>Key Takeaways\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>What Is Laravel Sanctum?\u003C\u002Fh2>\n\u003Cp>Sanctum sits between “roll your own token table” and “install Passport.” Official package, maintained with Laravel, and aimed at the boring-but-real cases: a Vue\u002FNuxt\u002FReact frontend talking to your API, or a mobile client that only needs a bearer token.\u003C\u002Fp>\n\u003Cp>I treat it as the default on first-party stacks. Passport still wins when you are building a proper OAuth provider for other companies’ apps. For everything else — dashboard + API, Flutter client, small partner token — Sanctum is usually enough, and you spend your time on product bugs instead of grant types.\u003C\u002Fp>\n\u003Cp>On a Laravel + Nuxt setup like the one behind \u003Ca href=\"\u002F\">this portfolio stack\u003C\u002Fa>, Sanctum is the boring, correct choice more often than JWT-in-localStorage hacks.\u003C\u002Fp>\n\n\u003Ch2>Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>You match the client.\u003C\u002Fstrong> Same-site (or configured) SPA → cookies. Phone \u002F CLI \u002F Postman → token. One package, two doors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cookie SPA auth plays nicer with CSRF.\u003C\u002Fstrong> Sticking long-lived JWTs in \u003Ccode>localStorage\u003C\u002Fcode> is still a common leak path when XSS shows up. Sessions + CSRF are closer to how Laravel already thinks.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tokens are revocable.\u003C\u002Fstrong> Lost phone? Delete that row. You do not have to rotate a global secret and kick every web user at once.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Middleware stays simple.\u003C\u002Fstrong> \u003Ccode>auth:sanctum\u003C\u002Fcode> on the route. Sanctum figures out session vs bearer. Your controllers stay readable.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>How It Works\u003C\u002Fh2>\n\u003Cp>Two modes. Mix them in one app if you have a web dashboard \u003Cem>and\u003C\u002Fem> a mobile app.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>SPA \u002F cookie mode.\u003C\u002Fstrong> Frontend hits \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>, then logs in through a normal session login. Laravel sets session cookies. Later \u003Ccode>\u002Fapi\u002F*\u003C\u002Fcode> calls send those cookies. Sanctum checks the session and that the Origin\u002FReferer looks like a domain you listed as stateful.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Personal access tokens.\u003C\u002Fstrong> After a successful login (or from an admin “create token” UI), you call \u003Ccode>createToken()\u003C\u002Fcode>. Sanctum stores a hash in \u003Ccode>personal_access_tokens\u003C\u002Fcode> and shows the plain token once. Client sends \u003Ccode>Authorization: Bearer …\u003C\u002Fcode> forever after (until you revoke it).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shared guard.\u003C\u002Fstrong> Routes use \u003Ccode>auth:sanctum\u003C\u002Fcode>. For a “stateful” request Sanctum prefers the session; otherwise it tries the bearer token. That is why one middleware covers both clients.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If the browser is yours and domains are lined up, use cookies. If the client cannot do cookies sanely, use tokens. Fighting that rule is where most Sanctum pain starts.\u003C\u002Fp>\n\n\u003Ch2>Step-by-Step Guide\u003C\u002Fh2>\n\u003Cp>Steps match Laravel 10\u002F11-style apps. Copy carefully if you are on an older Kernel-based project vs \u003Ccode>bootstrap\u002Fapp.php\u003C\u002Fcode>.\u003C\u002Fp>\n\n\u003Ch3>Step 1: Install and publish\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>composer require laravel\u002Fsanctum\nphp artisan vendor:publish --provider=\"Laravel\\Sanctum\\SanctumServiceProvider\"\nphp artisan migrate\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You should see \u003Ccode>config\u002Fsanctum.php\u003C\u002Fcode> and a migration for personal access tokens. If migrate looks “empty,” check you are not on a scaffold that already shipped Sanctum.\u003C\u002Fp>\n\n\u003Ch3>Step 2: User model\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>use Laravel\\Sanctum\\HasApiTokens;\n\nclass User extends Authenticatable\n{\n    use HasApiTokens, HasFactory, Notifiable;\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Without \u003Ccode>HasApiTokens\u003C\u002Fcode>, \u003Ccode>createToken()\u003C\u002Fcode> simply is not there. Easy to forget on a custom User model.\u003C\u002Fp>\n\n\u003Ch3>Step 3: Stateful domains for the SPA\u003C\u002Fh3>\n\u003Cp>Cookie mode only works if Sanctum recognizes the frontend host. Local Nuxt on port 3000 counts.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'stateful' =&gt; explode(',', env('SANCTUM_STATEFUL_DOMAINS', sprintf(\n    '%s%s',\n    'localhost,localhost:3000,127.0.0.1,127.0.0.1:8000,::1',\n    Sanctum::currentApplicationUrlWithPort(),\n))),\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Production \u003Ccode>.env\u003C\u002Fcode> sketch:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>SANCTUM_STATEFUL_DOMAINS=app.example.com,www.example.com\nSESSION_DOMAIN=.example.com\nSESSION_DRIVER=cookie\nSESSION_SECURE_COOKIE=true\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Ccode>SESSION_DOMAIN\u003C\u002Fcode> with a leading dot is often what makes \u003Ccode>api.\u003C\u002Fcode> and \u003Ccode>app.\u003C\u002Fcode> share the session cookie. Get this wrong and you get “login works, then every API call is guest” — the classic Saturday-night Sanctum bug.\u003C\u002Fp>\n\n\u003Ch3>Step 4: CORS + credentials\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>\u002F\u002F config\u002Fcors.php (typical shape)\n'paths' =&gt; ['api\u002F*', 'sanctum\u002Fcsrf-cookie', 'login', 'logout', 'register'],\n'supports_credentials' =&gt; true,\n'allowed_origins' =&gt; [env('FRONTEND_URL', 'http:\u002F\u002Flocalhost:3000')],\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Frontend must send cookies:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>axios.defaults.withCredentials = true;\naxios.defaults.withXSRFToken = true; \u002F\u002F Axios 1.x\n\nfetch('\u002Fapi\u002Fuser', { credentials: 'include' });\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If CORS allows \u003Ccode>*\u003C\u002Fcode> with credentials, browsers will refuse. Explicit origin only.\u003C\u002Fp>\n\n\u003Ch3>Step 5: Middleware\u003C\u002Fh3>\n\u003Cp>Laravel 11’s default API stack often already includes Sanctum’s stateful middleware. On older apps, put this in the \u003Ccode>api\u003C\u002Fcode> group:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\\Laravel\\Sanctum\\Http\\Middleware\\EnsureFrontendRequestsAreStateful::class,\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then lock routes down:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Route::middleware('auth:sanctum')-&gt;get('\u002Fapi\u002Fuser', function (Request $request) {\n    return $request-&gt;user();\n});\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Ch3>Step 6: SPA login sequence\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Ccode>GET \u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Flogin\u003C\u002Fcode> with email\u002Fpassword (web\u002Fsession guard)\u003C\u002Fli>\n\u003Cli>Call \u003Ccode>\u002Fapi\u002F...\u003C\u002Fcode> as usual\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cpre>\u003Ccode>await api.get('\u002Fsanctum\u002Fcsrf-cookie');\nawait api.post('\u002Flogin', { email, password });\nconst { data: user } = await api.get('\u002Fapi\u002Fuser');\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Skip step 1 and Laravel answers with \u003Cstrong>419\u003C\u002Fstrong>. That is CSRF doing its job, not “Sanctum being broken.”\u003C\u002Fp>\n\u003Cp>Logout should hit a route that runs the web guard logout and invalidates the session — not only clear Vue state.\u003C\u002Fp>\n\n\u003Ch3>Step 7: Token login for mobile \u002F scripts\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>Route::post('\u002Flogin', [AuthController::class, 'login']);\nRoute::middleware('auth:sanctum')-&gt;group(function () {\n    Route::get('\u002Fuser', fn (Request $r) =&gt; $r-&gt;user());\n    Route::post('\u002Flogout', [AuthController::class, 'logout']);\n});\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cpre>\u003Ccode>public function login(Request $request)\n{\n    $credentials = $request-&gt;validate([\n        'email' =&gt; ['required', 'email'],\n        'password' =&gt; ['required'],\n    ]);\n\n    if (! Auth::attempt($credentials)) {\n        throw ValidationException::withMessages([\n            'email' =&gt; ['Invalid credentials.'],\n        ]);\n    }\n\n    $user = $request-&gt;user();\n    $token = $user-&gt;createToken(\n        'mobile-app',\n        ['orders:read', 'orders:write']\n    )-&gt;plainTextToken;\n\n    return [\n        'token' =&gt; $token,\n        'user' =&gt; $user,\n    ];\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Send it as:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Authorization: Bearer 1|…plainText…\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>On logout for that device:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$request-&gt;user()-&gt;currentAccessToken()-&gt;delete();\n\u002F\u002F or wipe everything: $request-&gt;user()-&gt;tokens()-&gt;delete();\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Ch3>Step 8: Abilities when a token should not do everything\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>$user-&gt;createToken('ci-bot', ['deployments:trigger']);\n\nif (! $request-&gt;user()-&gt;tokenCan('deployments:trigger')) {\n    abort(403);\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Cookie sessions usually lean on policies\u002Fgates for “can this user edit this order?” Abilities shine on machine tokens and narrow integrations.\u003C\u002Fp>\n\n\u003Ch3>Step 9: Smoke-test both doors\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Browser:\u003C\u002Fstrong> cookies present after login; logged-out calls get 401; missing CSRF → 419.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Postman:\u003C\u002Fstrong> Bearer works; garbage token → 401; after delete, old token dies immediately.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Real-World Example\u003C\u002Fh2>\n\u003Cp>Team has Nuxt on \u003Ccode>app.example.com\u003C\u002Fcode> and Flutter hitting \u003Ccode>api.example.com\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Earlier they jammed JWTs into web localStorage “because mobile needed tokens too.” CORS was fiddly, revoke meant “change APP_KEY and apologize,” and a leaked admin token in a screenshot lived forever in chat history.\u003C\u002Fp>\n\u003Cp>With Sanctum split properly:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Nuxt stays on cookie + CSRF.\u003C\u002Fli>\n\u003Cli>Flutter keeps a token in secure storage.\u003C\u002Fli>\n\u003Cli>Settings UI lists tokens and a “log out this device” button.\u003C\u002Fli>\n\u003Cli>A CI bot gets \u003Ccode>reports:read\u003C\u002Fcode> only — not a god token.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Nothing glamorous. Fewer 2 a.m. auth regressions though, which is the point.\u003C\u002Fp>\n\n\u003Ch2>Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Faster path than Passport when you own the clients\u003C\u002Fli>\n\u003Cli>Cookie SPA flow matches Laravel’s session\u002FCSRF habits\u003C\u002Fli>\n\u003Cli>Token create \u002F list \u002F revoke without extra packages\u003C\u002Fli>\n\u003Cli>One middleware name for web SPA and mobile\u003C\u002Fli>\n\u003Cli>Fine with Nuxt, Vue, React, Inertia, Flutter, etc.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Not OAuth2 — no polished “third-party developer platform” story\u003C\u002Fli>\n\u003Cli>SPA mode fails loudly if domain\u002FCORS\u002Fcookie config is half-done\u003C\u002Fli>\n\u003Cli>Plain token is shown once; if you log it to Slack, you own that incident\u003C\u002Fli>\n\u003Cli>Huge public API marketplaces may still want Passport or a real IdP\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Cookies for your SPA; tokens for everything that is not a first-party browser you control.\u003C\u002Fli>\n\u003Cli>Do not “just use Bearer in Nuxt” out of habit if cookie mode is available.\u003C\u002Fli>\n\u003Cli>Production: HTTPS, \u003Ccode>SESSION_SECURE_COOKIE=true\u003C\u002Fcode>, sensible \u003Ccode>SESSION_DOMAIN\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Give tokens names and abilities you can reason about six months later.\u003C\u002Fli>\n\u003Cli>Rate-limit login and token minting.\u003C\u002Fli>\n\u003Cli>Sanctum says who the user is. Policies still decide what they can touch.\u003C\u002Fli>\n\u003Cli>Keep login\u002Flogout on the web guard for SPA; use token delete for mobile logout.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>No CSRF cookie call\u003C\u002Fstrong> → 419 on login. Call \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode> first.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>CORS credentials off or origin \u003Ccode>*\u003C\u002Fcode>\u003C\u002Fstrong> → browser drops cookies. Fix origin list + \u003Ccode>supports_credentials\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Stateful domain ≠ actual frontend host\u003C\u002Fstrong> → session never sticks. Check port in local dev.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tokens for the browser “to keep one code path”\u003C\u002Fstrong> → you traded UX and XSS posture for convenience. Prefer cookies for first-party web.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logout only clears Pinia\u002FVuex\u003C\u002Fstrong> → token or session still valid. Revoke server-side.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Printing plainTextToken in logs\u003C\u002Fstrong> → treat it like a password. DB already has the hash; that is enough.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\n\u003Ch3>What is Laravel Sanctum?\u003C\u002Fh3>\n\u003Cp>Official Laravel auth for first-party SPAs (cookies) and for API clients (personal access tokens). Lighter than Passport; usually enough when you are not selling OAuth to third-party developers.\u003C\u002Fp>\n\n\u003Ch3>How do I authenticate a SPA with Laravel Sanctum?\u003C\u002Fh3>\n\u003Cp>Install Sanctum, set stateful domains and credentialed CORS, call \u003Ccode>\u002Fsanctum\u002Fcsrf-cookie\u003C\u002Fcode>, log in on a session route, then hit \u003Ccode>auth:sanctum\u003C\u002Fcode> APIs with credentials included on every request.\u003C\u002Fp>\n\n\u003Ch3>Laravel Sanctum vs Passport — which should I use?\u003C\u002Fh3>\n\u003Cp>Sanctum for your own web\u002Fmobile clients and simple tokens. Passport (or Auth0\u002FKeycloak\u002Fetc.) when you need full OAuth2 for external apps. If you are unsure, you probably want Sanctum.\u003C\u002Fp>\n\n\u003Ch3>Is Laravel Sanctum worth it for API authentication?\u003C\u002Fh3>\n\u003Cp>For most Laravel products, yes. You get a maintained path for sessions and revocable tokens without maintaining a custom auth homegrown mess. Skip it only if your org already standardized on another IdP and Sanctum would duplicate that.\u003C\u002Fp>\n\n\u003Ch3>How do personal access tokens work in Sanctum?\u003C\u002Fh3>\n\u003Cp>\u003Ccode>createToken()\u003C\u002Fcode> returns the plain token once and stores a hash. Clients send Bearer. You can attach abilities and delete one token or all of them. Compromise response is “delete the row,” not “invalidate the universe.”\u003C\u002Fp>\n\n\u003Ch3>Can I use Sanctum with Nuxt.js?\u003C\u002Fh3>\n\u003Cp>Yes. Point the Nuxt API client at Laravel, turn credentials on, put the Nuxt origin in Sanctum stateful domains and CORS, then CSRF → login → API. Same pattern as Vue or plain Axios.\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>Sanctum covers the two auth shapes Laravel apps actually ship: browser sessions for your SPA, bearer tokens for mobile and scripts. Install it, add \u003Ccode>HasApiTokens\u003C\u002Fcode>, protect routes with \u003Ccode>auth:sanctum\u003C\u002Fcode>, then finish the boring config — domains, CORS, CSRF — because that is where projects stall.\u003C\u002Fp>\n\u003Cp>Pick cookie mode when you own the frontend. Mint scoped tokens when the client cannot hold a Laravel session. Revoke on logout. Keep authorization in policies.\u003C\u002Fp>\n\u003Cp>If you are wiring Laravel + Nuxt and want a second pair of eyes on the cookie\u002FCORS path, \u003Ca href=\"\u002Fabout\">say hello\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2>Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Sanctum = SPA cookies + API tokens, not full OAuth.\u003C\u002Fli>\n\u003Cli>\u003Ccode>auth:sanctum\u003C\u002Fcode> handles session or Bearer; you choose the mode per client.\u003C\u002Fli>\n\u003Cli>Most SPA bugs are CSRF, CORS, or domain mismatch — not “Sanctum itself.”\u003C\u002Fli>\n\u003Cli>Name tokens, scope them, delete them on logout.\u003C\u002Fli>\n\u003Cli>Reach for Passport\u002FOAuth only when third-party delegated login is a real product need.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785833713437-wcqb6c.webp","Laravel Sanctum API Authentication Guide","Learn Laravel Sanctum for API auth: SPA cookie sessions and personal access tokens, with setup steps, examples, and security best practices.","",[19,20,21,22,23,24],"Laravel","Sanctum","API Authentication","PHP","SPA","Security","published","2026-08-04T08:56:17.304+00:00",23,null,"2026-08-04T08:55:57.847255+00:00","2026-08-06T04:07:09.059636+00:00",[32,47,64,77,90,104,116,128,141,154,165,176,187,200,214,225,236,238,249,263,275,284,295,308],{"id":33,"title":34,"slug":35,"excerpt":36,"cover_image":37,"tags":38,"published_at":44,"updated_at":45,"view_count":46},"1fac09f2-990e-4ebf-99b1-0cc532e7cb08","Soft Delete Inventory Bug — Phantom Serial Stock After Purchase Delete","soft-delete-inventory-bug-phantom-serial-stock-after-purchase-delete","Soft-deleting a purchase looked fine until serial-tracked products stayed sellable. The movement ran, quantity didn’t move, and serials were never detached.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1793165769172-Phantom-Inventory_-Deleted-Warehouse-Order_Z0BIZdhyJ.webp",[39,40,41,42,43,6],"laravel","inventory","soft-delete","serial-numbers","stock-movements","2026-10-28T05:36:31.148+00:00","2026-10-28T05:36:32.188948+00:00",21,{"id":48,"title":49,"slug":50,"excerpt":51,"cover_image":52,"tags":53,"published_at":61,"updated_at":62,"view_count":63},"b2a6b718-c6e5-42fa-9358-22e84035aaf2","Multi-Tenant Inventory Manager with Nuxt 3 and Supabase","multi-tenant-inventory-manager-nuxt-supabase","A shop-billing SaaS on Nuxt 3 and Supabase: stock, invoices, UPI links, AI bill scan, and per-shop storefronts — with RLS so shop_id is never trusted from the client.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Flibrary\u002F1792583563566-Modern-Retail-POS-Dashboard-Network_-BFGj_TT0.webp?updatedAt=1792583565092",[54,55,56,40,6,57,58,59,60],"nuxt","supabase","multi-tenancy","vue","pinia","vuetify","ai","2026-10-21T12:07:58.857+00:00","2026-10-21T12:07:59.070373+00:00",16,{"id":65,"title":66,"slug":67,"excerpt":68,"cover_image":69,"tags":70,"published_at":74,"updated_at":75,"view_count":76},"58f0adc6-f4e9-4501-bc0e-ab83cc2cc073","Laravel Sanctum 419 Fix — Why XSRF-TOKEN Must Stay Encrypted","laravel-sanctum-419-xsrf-token-encryption","Sanctum SPA login kept returning 419 CSRF token mismatch. The bug wasn’t domains or cookies “not sticking” — it was excluding XSRF-TOKEN from EncryptCookies while Laravel decrypts the X-XSRF-TOKEN header.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792229994752-From-CSRF-Error-to-Secure-Fix_FIVIW5po2.webp",[19,20,71,72,23,73,21],"CSRF","419","Nuxt","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":78,"title":79,"slug":80,"excerpt":81,"cover_image":82,"tags":83,"published_at":88,"updated_at":89,"view_count":27},"7b4bee90-b35b-4ced-ae8c-0a71e7d968fb","ImageKit Nuxt Upload — Keep Private Keys Off the Client","imagekit-nuxt-upload-secure","ImageKit Nuxt upload means the browser never sees your private key. Sign or upload on the server, return a CDN URL, and store that URL in your CMS or database.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792216420019-Secure-Upload-Architecture-Flow_MGyvtL5tR.webp",[73,84,85,86,87],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",{"id":91,"title":92,"slug":93,"excerpt":94,"cover_image":95,"tags":96,"published_at":102,"updated_at":103,"view_count":63},"bd55b3c6-8bd3-447d-99ad-d46a97490d7b","Apache 2 Installation on Ubuntu: Step-by-Step","apache-2-installation-ubuntu","Install Apache 2 on Ubuntu with apt, start the service, open the firewall, and verify the default page. Part 2 of the Apache 2 series — clean setup before virtual hosts.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788925690969-7zm2c2.webp",[97,98,99,100,101],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":105,"title":106,"slug":107,"excerpt":108,"cover_image":109,"tags":110,"published_at":113,"updated_at":114,"view_count":115},"8c75a723-b1a7-4fab-9bb9-71a111c9d4f8","Apache vs Nginx: What They Are and When to Use Each","apache-vs-nginx","Apache and Nginx are web servers. They take HTTP requests and return files or pass work to PHP, Node, or another app. Apache fits shared hosting and .htaccess; Nginx is the usual reverse proxy on an Ubuntu VPS.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788524039845-wrez6s.webp",[97,111,98,101,100,112],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":117,"title":118,"slug":119,"excerpt":120,"cover_image":121,"tags":122,"published_at":125,"updated_at":126,"view_count":127},"40dd3304-99d2-4948-b8c1-44625f1f4306","What Is a Virtual Host? Host Multiple Sites on One Ubuntu VPS","virtual-host-linux-multiple-websites","A virtual host maps each domain to its own folder on one server. Developers use this on Ubuntu VPSes so portfolio, API, and staging share one bill. Same idea on any Linux — Ubuntu is just what most tutorials and clouds default to.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788523755345-javhet.webp",[123,98,111,100,124,112],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":129,"title":130,"slug":131,"excerpt":132,"cover_image":133,"tags":134,"published_at":138,"updated_at":139,"view_count":140},"6e45f39b-1ade-47f0-a0b0-b4cd386a10dc","Laravel Queues & Jobs: How Background Processing Works","laravel-queues-and-jobs","Laravel queues move slow work off the HTTP request. You push a Job onto a queue, a worker runs it later, and the user gets a fast response. Use them for mail, webhooks, image work, and anything that can fail and retry.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787286979145-0i7ewp.webp",[19,135,136,22,137],"Queues","Jobs","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":142,"title":143,"slug":144,"excerpt":145,"cover_image":146,"tags":147,"published_at":151,"updated_at":152,"view_count":153},"938c7bd9-2cf3-4a81-8dae-cf88c09e64ca","Laravel N+1 Query Problem: How to Detect and Fix It","laravel-n-plus-1-query-problem","The Laravel N+1 query problem is when one listing query is followed by one extra query per row. You spot it in Telescope or the query log, then fix it with with(), withCount(), and nested eager loads.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787199419649-niq9k8.webp",[19,148,149,150,22],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":155,"title":156,"slug":157,"excerpt":158,"cover_image":159,"tags":160,"published_at":162,"updated_at":163,"view_count":164},"76717847-4080-4ae6-a2d8-b35badc46be3","Laravel Eloquent Relationships","laravel-eloquent-relationships","Laravel Eloquent relationships map how models connect — hasMany, belongsTo, belongsToMany, and more. Define them once, then load related rows with with() instead of stuffing joins into every query.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787122982331-16979e.webp",[19,148,22,161,137],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":166,"title":167,"slug":168,"excerpt":169,"cover_image":170,"tags":171,"published_at":174,"updated_at":175,"view_count":63},"6bbe0ad8-0c6d-4172-b279-ded8e2ca9416","Laravel Database Transactions: When and Why to Use DB::transaction()","laravel-database-transactions","DB::transaction() runs a closure inside a SQL transaction: Laravel commits if it finishes, and rolls back if it throws. Use it when one action writes more than one row and a half-finished write would leave bad data.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787114417893-hp3hmc.webp",[19,172,148,22,173],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":177,"title":178,"slug":179,"excerpt":180,"cover_image":181,"tags":182,"published_at":185,"updated_at":186,"view_count":153},"d1020b7b-b410-414f-9ceb-eb0501bc905e","Laravel Auditing Package — Track Model Changes the Right Way","laravel-auditing-package","The Laravel auditing package records old and new model values, the user who changed them, and when it happened—without you inventing a second history table for every feature.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786778101029-mwb9sf.webp",[19,183,22,24,184],"Auditing","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":188,"title":189,"slug":190,"excerpt":191,"cover_image":192,"tags":193,"published_at":197,"updated_at":198,"view_count":199},"3d5eb867-6288-48c4-af04-8b7ece8b874e","Laravel Lifecycle — How a Request Becomes a Response","laravel-lifecycle","The Laravel lifecycle is the path from HTTP request to response: bootstrap, service providers, middleware, routing, then the controller. Know that path and most “random” bugs stop being random.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786777544862-khxf92.webp",[19,22,194,195,196],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":201,"title":202,"slug":203,"excerpt":204,"cover_image":205,"tags":206,"published_at":212,"updated_at":213,"view_count":153},"2ab5e08a-7117-43c5-87eb-0789a2fd3af4","Claude Code Best Practices for Large Codebases — Scope Before You Ship","claude-code-best-practices-large-codebases","On a big repo, Claude Code only helps if you lock rules in CLAUDE.md, scope every ticket, plan multi-file edits, and review the diff like a PR.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786178453897-dulbmv.webp",[207,208,209,210,211],"claude-code","ai-coding","large-codebases","monorepo","developer-tools","2026-08-08T08:41:03.571+00:00","2026-08-08T08:41:03.839922+00:00",{"id":215,"title":216,"slug":217,"excerpt":218,"cover_image":219,"tags":220,"published_at":223,"updated_at":224,"view_count":164},"ddd55ce1-48fd-40b4-ae91-48a6bec20a2a","Nuxt Middleware Explained — Auth, Redirects & Route Guards Deep Dive","nuxt-middleware-explained","Nuxt middleware runs before a page loads so you can check auth, redirect users, or block a route — on the server for the first hit and in the browser on later navigations.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785902953511-osy6pt.webp",[73,195,221,222,85],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":226,"title":227,"slug":228,"excerpt":229,"cover_image":230,"tags":231,"published_at":234,"updated_at":235,"view_count":127},"e0d9941b-467d-45cc-bf12-45390cf9aeaa","Nuxt Lifecycle Explained — Server, Client & Hooks Made Simple","nuxt-lifecycle-explained","Nuxt lifecycle is the order your app boots, fetches data, renders HTML on the server, hydrates in the browser, then runs page navigation — so you know where to put code safely.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785901639981-9tgcl5.webp",[73,85,221,232,233],"Lifecycle","JavaScript","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":237,"published_at":26,"updated_at":30,"view_count":27},[19,20,21,22,23,24],{"id":239,"title":240,"slug":241,"excerpt":242,"cover_image":243,"tags":244,"published_at":247,"updated_at":248,"view_count":164},"f50b774a-c745-41aa-a3b0-72ac1f5b7117","Laravel Sanctum vs Passport — Which API Auth Should You Use?","laravel-sanctum-vs-passport","Laravel Sanctum is the lighter choice for SPAs and simple API tokens; Passport is full OAuth2 for third-party apps. Pick Sanctum for most apps, Passport when you need real OAuth2.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785817155174-054d6s.webp",[19,20,245,21,22,246,23],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":250,"title":251,"slug":252,"excerpt":253,"cover_image":254,"tags":255,"published_at":260,"updated_at":261,"view_count":262},"ef36ca16-73ab-4f9a-9584-ff70a60da5f5","Laravel vs NestJS in 2026: Which Backend Should US Startups Choose?","laravel-vs-nestjs-2026-us-startups","Laravel vs NestJS for US startups in 2026: compare speed, TypeScript, hiring, SaaS MVPs, and real-time apps — and pick the backend that matches your team.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785609396341-ungcby.jpg",[19,256,196,257,258,22,86,259],"NestJS","SaaS","Startups","Web Development","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":264,"title":265,"slug":266,"excerpt":267,"cover_image":268,"tags":269,"published_at":273,"updated_at":274,"view_count":127},"c4e41758-834c-476e-8830-f776c963a784","What Is TypeScript? A Beginner’s Guide to Safer JavaScript","what-is-typescript","TypeScript is JavaScript with types. Learn what it is, how it works, and how to write your first typed script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785574204088-8bc8es.jpg",[86,233,259,270,271,272],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":276,"title":277,"slug":278,"excerpt":279,"cover_image":280,"tags":281,"published_at":282,"updated_at":283,"view_count":153},"37ee32f1-7b8d-4c4d-92b4-37bb37ff64c5","What Is JavaScript? A Beginner’s Guide to Modern Web Development","what-is-javascript","JavaScript is the programming language that makes websites interactive. Learn what it is, how it works, and how to write your first script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785561346515-utrr91.jpg",[233,259,270,271,272],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":285,"title":286,"slug":287,"excerpt":288,"cover_image":289,"tags":290,"published_at":293,"updated_at":294,"view_count":164},"f238da13-8416-41e6-8281-a6185efd4bd4","Laravel Sanctum Explained: Simple API Authentication for Modern Apps","laravel-sanctum-api-authentication","Laravel Sanctum makes API authentication simple — whether you need token-based APIs for mobile apps or cookie-based auth for SPAs. Here’s how it works, without the jargon.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785470074981-vejfi4.jpg",[19,20,291,292,23],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":296,"title":297,"slug":298,"excerpt":299,"cover_image":300,"tags":301,"published_at":305,"updated_at":306,"view_count":307},"d8c77913-46f4-4012-ade6-bd5a81676001","Laravel Module Structure Explained: Keep Large Apps Clean","laravel-module-structure-explained","A practical guide to Laravel module architecture — folder layout, providers, routes, and boundaries that keep features independent as your app grows.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785385385865-8oyk12.png",[19,22,302,303,196,304],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":309,"title":310,"slug":311,"excerpt":312,"cover_image":313,"tags":314,"published_at":321,"updated_at":322,"view_count":140},"26ccd19c-a8bb-419d-be11-efd1d221b415","Cursor vs Claude vs ChatGPT: Which AI Actually Helps with Laravel & Nuxt?","cursor-ai-vs-claude-code-vs-chatgpt-for-laravel-nuxt-development-2026","Tired of constantly copying and pasting code between your Vue frontend and PHP backend? I tested Cursor, Claude Code, and ChatGPT to see which one actually speeds up a real-world Laravel and Nuxt workflow. Here is my breakdown.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785300697566-pn766r.png",[19,315,316,317,318,319,320],"Nuxt 3","AI for Developers","Cursor","Claude Code","ChatGPT","Full Stack","2026-07-29T04:46:50.88+00:00","2026-08-01T08:50:11.809909+00:00",[],{"variant":325,"profile":330,"heroStats":343,"aboutParagraphs":347,"aboutPillars":354,"aboutFacts":367,"skillCategories":380,"experiences":419,"education":446,"projects":465,"languages":535,"interests":538},{"id":326,"slug":327,"label":328,"is_active":329,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":331,"title":332,"tagline":332,"photo_url":333,"summary":334,"email":335,"phone":17,"location":336,"linkedin":337,"github":338,"instagram":339,"hero_headline":340,"hero_headline_accent":341,"hero_subheadline":342},"Mohd Anish","Full Stack Developer ","\u002Fprofile.png","Full Stack Developer with 3.5+ years of experience specializing in Laravel, Vue.js, Nuxt.js, MySQL, and modern web technologies. Experienced in designing, developing, and maintaining scalable web applications with a strong focus on performance, security, and code quality.","anhali736@gmail.com","Rajasthan, India","linkedin.com\u002Fin\u002Fmohd-anish-23096635a","https:\u002F\u002Fgithub.com\u002Fmrmolani76","https:\u002F\u002Fwww.instagram.com\u002Fmohdanish.me\u002F","Building Scalable Web Apps","using Modern Technologies","Building secure, scalable, and high-performance web applications using Laravel, Vue.js, Nuxt.js, and MySQL.",[344],{"value":345,"label":346},"3.5+","Yrs Development",[348,350,352],{"html":349},"I'm a \u003Cspan class=\"text-gold font-medium\">Full Stack Developer\u003C\u002Fspan> passionate about building secure, scalable, and high-performance web applications. I enjoy solving complex problems and creating modern digital experiences with clean, maintainable code.",{"html":351},"I specialize in \u003Cspan class=\"text-gold font-medium\">Laravel\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Vue.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Nuxt.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">MySQL\u003C\u002Fspan>, and \u003Cspan class=\"text-foreground\">REST APIs\u003C\u002Fspan>, building responsive and scalable applications with a strong focus on performance, security, and code quality.",{"html":353},"With \u003Cspan class=\"text-foreground\">3.5+ years of experience\u003C\u002Fspan>, I've contributed to enterprise-grade applications, including compliance-critical modules for the \u003Cspan class=\"text-foreground\">Complere eQMS\u003C\u002Fspan> platform. I'm committed to continuous learning and building software that is reliable, maintainable, and ready for real-world use.",[355,359,363],{"icon":356,"label":357,"description":358},"lucide:code-2","Build","Scalable, clean web apps",{"icon":360,"label":361,"description":362},"lucide:trending-up","Grow","Marketing-driven results",{"icon":364,"label":365,"description":366},"lucide:shield-check","Ship","Reliable, compliant systems",[368,372,376],{"icon":369,"label":370,"value":371},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":373,"label":374,"value":375},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":377,"label":378,"value":379},"lucide:map-pin","Availability","Open to opportunities",[381,394,403,414],{"title":382,"icon":383,"color":384,"show_on_home":329,"show_on_resume":329,"skills":385},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[19,22,386,387,388,389,390,391,392,393],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":395,"icon":396,"color":384,"show_on_home":329,"show_on_resume":397,"skills":398},"Frontend Development","lucide:code",false,[399,400,401,86,402,233],"Nuxt.js","Vue.js","React","Tailwind CSS",{"title":404,"icon":405,"color":384,"show_on_home":329,"show_on_resume":397,"skills":406},"AI & Automation","lucide:zap",[407,408,409,410,411,412,413],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":415,"icon":416,"color":384,"show_on_home":329,"show_on_resume":329,"skills":417},"Development","lucide:wrench",[19,22,400,399,233,86,402,388,387,418],"Git & GitHub",[420],{"role":328,"company":421,"note":422,"period":423,"description":424,"stack":425,"color":384,"icon":426,"points":427},"Complibued","Complere eQMS — Pharmaceutical SaaS","2023 – Present","Building Complere eQMS, a cloud-based Quality Management System for regulated life sciences using Laravel and Nuxt.js. Developed compliance-critical modules — Document Control, LMS, Events, CAPA, Change Control, Audit, and Risk Assessment.","Laravel · Vue\u002FNuxt · MySQL · Tailwind CSS","lucide:folder-git-2",[428,431,433,435,437,440,442,444],{"text":429,"surface":430},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":432,"surface":430},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":434,"surface":430},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":436,"surface":430},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":438,"surface":439},"Built Document Control & LMS (training) modules","home",{"text":441,"surface":439},"Implemented CAPA and Event management workflows",{"text":443,"surface":439},"Developed Change Control (CR) with impact-assessed approvals",{"text":445,"surface":439},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[447,452,456,461],{"degree":448,"school":449,"period":450,"score":451},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":453,"school":449,"period":454,"score":455},"BCA","2020 – 2023","71%",{"degree":457,"school":458,"period":459,"score":460},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":462,"school":458,"period":463,"score":464},"Secondary (10th)","2016 – 2017","48.75%",[466,483,500],{"title":467,"slug":468,"description":469,"why":470,"category":471,"image":472,"emoji":473,"link":474,"is_active":329,"stack":475,"features":477,"metrics":482},"Inventory Manager","inventory-manager","Professional inventory management system for tracking stock, orders, and enterprise operations. Powered by Supabase auth and a relational MySQL backend.","Stock and order tracking needed a reliable source of truth for enterprise operations. This system was built so teams can monitor inventory, manage orders, and report status from one authenticated app.","Enterprise","bg-gradient-to-br from-gold-soft\u002F15 via-gold\u002F5 to-transparent","📦","https:\u002F\u002Fruby-enterprise.vercel.app\u002F",[400,476,387,402,86],"Supabase",[478,479,480,481],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":484,"slug":485,"description":486,"why":487,"category":488,"image":489,"emoji":490,"link":491,"is_active":329,"stack":492,"features":494,"metrics":499},"Random Video Chat","random-video-chat","Omegle-style platform for spontaneous 1-on-1 video conversations with strangers. Uses WebRTC for peer-to-peer video and Supabase Realtime for matchmaking and signaling.","I wanted to explore real-time peer connections without a heavy media server. The app was built to practice WebRTC + realtime matchmaking and deliver instant 1-on-1 video chat with no account friction.","Real-time","bg-gradient-to-br from-gold\u002F15 via-gold\u002F5 to-transparent","🎥","https:\u002F\u002Fomegle-seven-xi.vercel.app\u002F",[400,493,476,402,86],"WebRTC",[495,496,497,498],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":501,"slug":502,"description":503,"why":504,"category":505,"image":489,"emoji":506,"link":507,"is_active":329,"stack":508,"features":516,"metrics":525},"Nexro","nexro","Multi-tenant retail web app for GST billing and inventory — products, purchases, sales, POS, quotations, supplier ledgers, and reports. Landing page: nexro.me.","Retail shops were juggling billing, stock, purchases, and supplier dues across sheets and separate tools. Nexro was built as a multi-tenant SaaS so each shop gets its own data on a shared Laravel + Nuxt stack, with GST invoices, live stock, and day-to-day ops from one login.","Web App \u002F SaaS","🏪","https:\u002F\u002Fnexro.me",[509,510,511,512,402,86,387,513,514,515,390],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[517,518,519,520,521,522,523,524],"Multi-tenant shop isolation","GST billing & POS","Inventory with SKU \u002F barcode \u002F serial","Purchases & supplier ledger","Quotations → invoice","Sales, stock & dues reports","Thermal & A4 print","Region-aware landing (nexro.me)",[526,529,532],{"value":527,"label":528},"1","Product platform",{"value":530,"label":531},"7+","Core modules",{"value":533,"label":534},"MT","Multi-tenant",[536,537],"Hindi","English",[259,539,540],"Video Content","New Tools & Tech"]