[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-auditing-package":8,"blog-posts-latest:24":30,"blog-comments:d1020b7b-b410-414f-9ceb-eb0501bc905e":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":24,"published_at":25,"view_count":26,"deleted_at":27,"deleted_reason":17,"created_at":28,"updated_at":29},"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.","\u003Ch2>Quick Answer\u003C\u002Fh2>\n\u003Cp>The Laravel auditing package (owen-it\u002Flaravel-auditing) stores a history of Eloquent model changes: old values, new values, event type, user, IP, and timestamp. You add the Auditable trait, run a migration, and create\u002Fupdate\u002Fdelete events write rows to an \u003Ccode>audits\u003C\u002Fcode> table. Use it for compliance trails and “who changed this?” — not as a generic application event bus.\u003C\u002Fp>\n\n\u003Ch2>Quick Facts\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Topic:\u003C\u002Fstrong> Laravel Auditing Package\u003Cbr>\n\u003Cstrong>Category:\u003C\u002Fstrong> Backend \u002F Laravel Packages\u003C\u002Fp>\n\n\u003Ch2>Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>What Is Laravel Auditing Package?\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 Auditing Package?\u003C\u002Fh2>\n\u003Cp>When people say “Laravel audit package,” they usually mean \u003Ccode>owen-it\u002Flaravel-auditing\u003C\u002Fcode>. It watches Eloquent models and writes an audit row whenever a record is created, updated, deleted, or restored.\u003C\u002Fp>\n\u003Cp>Each audit is a morph to the model (\u003Ccode>auditable_type\u003C\u002Fcode> + \u003Ccode>auditable_id\u003C\u002Fcode>) plus a morph to the user who did it (\u003Ccode>user_type\u003C\u002Fcode> + \u003Ccode>user_id\u003C\u002Fcode>). Old and new attributes live in JSON columns. You can later list history on a document, CAPA, or user profile without a custom \u003Ccode>*_histories\u003C\u002Fcode> table per module.\u003C\u002Fp>\n\u003Cp>It is not the same as Spatie’s activity log. Activity log is a general “something happened” feed. Auditing is focused on attribute-level diffs on models. In regulated Laravel apps (the kind of Document Control \u002F CAPA work on \u003Ca href=\"\u002F\">this stack\u003C\u002Fa>), you often want the diff, not just a sentence in a log.\u003C\u002Fp>\n\n\u003Ch2>Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Who changed what\u003C\u002Fstrong> — support and QA can answer that without reading MySQL binlogs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Compliance-friendly trail\u003C\u002Fstrong> — create\u002Fupdate\u002Fdelete with actor and timestamp is the minimum many quality systems expect.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Less custom history code\u003C\u002Fstrong> — one \u003Ccode>audits\u003C\u002Fcode> table instead of copy-pasted observers in every module.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Debugging data bugs\u003C\u002Fstrong> — a bad mass-assignment or import shows up as a sudden old→new jump you can replay.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>How It Works\u003C\u002Fh2>\n\u003Cp>Auditing hooks Eloquent events. After the model saves, the package builds an audit from the dirty attributes (or the full snapshot, depending on config) and inserts it.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Model is auditable\u003C\u002Fstrong> — it uses \u003Ccode>OwenIt\\Auditing\\Auditable\u003C\u002Fcode> and implements \u003Ccode>Auditable\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Event fires\u003C\u002Fstrong> — \u003Ccode>created\u003C\u002Fcode>, \u003Ccode>updated\u003C\u002Fcode>, \u003Ccode>deleted\u003C\u002Fcode>, \u003Ccode>restored\u003C\u002Fcode> (you choose which in config or per model).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Resolver data\u003C\u002Fstrong> — user id, IP, user agent, URL come from resolvers. In HTTP that’s the logged-in user. In queues\u002Fartisan you must set a resolver or accept \u003Ccode>user_id = null\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit row\u003C\u002Fstrong> — \u003Ccode>old_values\u003C\u002Fcode> \u002F \u003Ccode>new_values\u003C\u002Fcode> JSON, \u003Ccode>event\u003C\u002Fcode>, morph keys, optional tags.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Read path\u003C\u002Fstrong> — \u003Ccode>$model-&gt;audits\u003C\u002Fcode> or a query on the \u003Ccode>Audit\u003C\u002Fcode> model for reports.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Global scopes and \u003Ccode>saveQuietly()\u003C\u002Fcode> matter. Quiet saves skip Eloquent events, so they skip audits. That’s a feature when you sync a denormalized counter; it’s a hole if you “fix data” in tinker with \u003Ccode>saveQuietly()\u003C\u002Fcode> on a controlled document.\u003C\u002Fp>\n\n\u003Ch2>Step-by-Step Guide\u003C\u002Fh2>\n\u003Cp>Package APIs shift across major versions. Match the install to your Laravel version, then keep the same idea: trait + migration + exclude secrets.\u003C\u002Fp>\n\n\u003Ch3>Step 1: Install and migrate\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>composer require owen-it\u002Flaravel-auditing\nphp artisan vendor:publish --provider \"OwenIt\\Auditing\\AuditingServiceProvider\" --tag=\"config\"\nphp artisan vendor:publish --provider \"OwenIt\\Auditing\\AuditingServiceProvider\" --tag=\"migrations\"\nphp artisan migrate\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Confirm an \u003Ccode>audits\u003C\u002Fcode> table exists. Don’t hand-edit that schema unless you know you need extra columns (tenant id, plant id, etc.).\u003C\u002Fp>\n\n\u003Ch3>Step 2: Make a model auditable\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>use OwenIt\\Auditing\\Contracts\\Auditable;\nuse OwenIt\\Auditing\\Auditable as AuditableTrait;\n\nclass Document extends Model implements Auditable\n{\n    use AuditableTrait;\n\n    protected $fillable = ['title', 'status', 'owner_id', 'content'];\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Repeat only on models that need a trail. Auditing every \u003Ccode>sessions\u003C\u002Fcode>-style or cache table is noise and disk.\u003C\u002Fp>\n\n\u003Ch3>Step 3: Exclude secrets and useless columns\u003C\u002Fh3>\n\u003Cp>In the model or in \u003Ccode>config\u002Faudit.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F on the model\nprotected $auditExclude = [\n    'remember_token',\n    'password',\n    'updated_at', \u002F\u002F optional; some teams keep it\n];\n\npublic function transformAudit(array $data): array\n{\n    unset($data['new_values']['password'], $data['old_values']['password']);\n    return $data;\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Never audit password hashes, API tokens, or 2FA secrets. If a column is huge (long HTML), either exclude it or store a hash\u002Fsummary — JSON blobs will bloat \u003Ccode>audits\u003C\u002Fcode> fast.\u003C\u002Fp>\n\n\u003Ch3>Step 4: Control which events you keep\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>\u002F\u002F config\u002Faudit.php (concept)\n'events' =&gt; [\n    'created',\n    'updated',\n    'deleted',\n    'restored',\n],\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Per-model override if a lookup table only needs \u003Ccode>updated\u003C\u002Fcode>. Skip \u003Ccode>retrieved\u003C\u002Fcode> unless you have a real “who viewed this” requirement — that’s volume, not an audit of changes.\u003C\u002Fp>\n\n\u003Ch3>Step 5: Show history in the UI\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>$document = Document::with('audits.user')-&gt;findOrFail($id);\n\nforeach ($document-&gt;audits as $audit) {\n    \u002F\u002F $audit-&gt;event, $audit-&gt;user, $audit-&gt;old_values, $audit-&gt;new_values, $audit-&gt;created_at\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Render a simple timeline: actor, event, changed keys. Don’t dump raw JSON to end users in a pharma\u002FQMS screen — map keys to labels (\u003Ccode>status\u003C\u002Fcode> → Status).\u003C\u002Fp>\n\n\u003Ch3>Step 6: Handle console, jobs, and impersonation\u003C\u002Fh3>\n\u003Cp>HTTP requests get \u003Ccode>auth()-&gt;user()\u003C\u002Fcode> for free. Seeders, imports, and queue jobs do not. Set the auditor explicitly or accept system rows:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F concept — use the API your installed version documents\nDocument::disableAuditing();\n\u002F\u002F bulk import\nDocument::enableAuditing();\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If admins impersonate users, make sure the resolver stores the real actor (or both actor and impersonator). Otherwise the trail lies.\u003C\u002Fp>\n\n\u003Ch3>Step 7: Prune or archive\u003C\u002Fh3>\n\u003Cp>Audits grow forever. Add a scheduled prune for noisy models, or archive old rows to cold storage. Keep longer retention on regulated entities (documents, CAPA) than on \u003Ccode>Last seen at\u003C\u002Fcode> style fields.\u003C\u002Fp>\n\n\u003Ch2>Real-World Example\u003C\u002Fh2>\n\u003Cp>A Document Control module had a custom \u003Ccode>document_revisions\u003C\u002Fcode> table that only stored “new file uploaded.” Status flips, owner changes, and “who un-obsolete’d this?” were missing. QA failed a trail question in an audit meeting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>After the auditing package:\u003C\u002Fstrong> \u003Ccode>Document\u003C\u002Fcode> and \u003Ccode>DocumentVersion\u003C\u002Fcode> used the Auditable trait. Status, owner, and effective dates showed old→new. The file upload still wrote a revision row (binary files don’t belong in \u003Ccode>audits\u003C\u002Fcode> JSON). Reviewers opened a History tab: user, timestamp, fields.\u003C\u002Fp>\n\u003Cp>The remaining gap was an artisan backfill that used \u003Ccode>saveQuietly()\u003C\u002Fcode> to set \u003Ccode>legacy_id\u003C\u002Fcode>. Those updates left no audit. The fix was a tagged audit or a one-off “system migration” note — not more observers. Same lesson as the \u003Ca href=\"\u002Fblog\u002Flaravel-lifecycle\">Laravel lifecycle\u003C\u002Fa>: if Eloquent never fires \u003Ccode>updated\u003C\u002Fcode>, no package can see it.\u003C\u002Fp>\n\n\u003Ch2>Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Attribute-level old\u002Fnew values on Eloquent models\u003C\u002Fli>\n\u003Cli>One morph table instead of per-module history schemas\u003C\u002Fli>\n\u003Cli>User, IP, and URL resolvers included\u003C\u002Fli>\n\u003Cli>Works with restore on SoftDeletes if you enable that event\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>JSON history is awkward to query (“all documents whose status became Obsolete last month” needs JSON functions or extra indexes)\u003C\u002Fli>\n\u003Cli>High-churn models will grow the table quickly\u003C\u002Fli>\n\u003Cli>Does not replace a full event-sourced domain or file version storage\u003C\u002Fli>\n\u003Cli>Queue\u002Fconsole actors are easy to get wrong (\u003Ccode>user_id\u003C\u002Fcode> null)\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Audit business entities\u003C\u002Fstrong>, not every Eloquent model.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Exclude passwords, tokens, and giant HTML\u003C\u002Fstrong> from \u003Ccode>old_values\u003C\u002Fcode> \u002F \u003Ccode>new_values\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Index\u003C\u002Fstrong> \u003Ccode>auditable_type\u003C\u002Fcode>, \u003Ccode>auditable_id\u003C\u002Fcode>, \u003Ccode>user_id\u003C\u002Fcode>, \u003Ccode>created_at\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Don’t use \u003Ccode>saveQuietly()\u003C\u002Fcode>\u003C\u002Fstrong> on records you legally need to trail.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Keep file binaries in your own revision table\u003C\u002Fstrong>; audit metadata only.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Decide retention\u003C\u002Fstrong> per model type before production data explodes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Pair with policies\u003C\u002Fstrong> — auditing records what happened; it does not block unauthorized writes. Auth still belongs in gates\u002Fpolicies and \u003Ca href=\"\u002Fblog\u002Flaravel-sanctum-api-authentication\">API auth\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Auditing the User password field\u003C\u002Fstrong> → Fix: exclude it; never put hashes in JSON logs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Expecting audits from \u003Ccode>Model::query()-&gt;update()\u003C\u002Fcode>\u003C\u002Fstrong> → Fix: mass updates skip model events. Loop models or write an explicit audit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logging retrieved\u002Fview events like changes\u003C\u002Fstrong> → Fix: use a separate view log; don’t drown \u003Ccode>audits\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No user on queued jobs\u003C\u002Fstrong> → Fix: pass actor id into the job and set it in a resolver, or mark event as \u003Ccode>system\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Showing raw JSON to auditors\u003C\u002Fstrong> → Fix: human labels and only changed keys.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>One giant unindexed \u003Ccode>audits\u003C\u002Fcode> table\u003C\u002Fstrong> → Fix: indexes + prune\u002Farchive.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3>What is the Laravel auditing package?\u003C\u002Fh3>\n\u003Cp>It is an Eloquent auditing library (commonly owen-it\u002Flaravel-auditing) that stores who changed a model, which attributes changed, and when. History lives in an \u003Ccode>audits\u003C\u002Fcode> table related by morphs.\u003C\u002Fp>\n\n\u003Ch3>How do I set up Laravel auditing?\u003C\u002Fh3>\n\u003Cp>Composer require the package, publish config and migrations, migrate, then implement \u003Ccode>Auditable\u003C\u002Fcode> and use the trait on each model you care about. Exclude secrets, then read \u003Ccode>$model-&gt;audits\u003C\u002Fcode> in the UI.\u003C\u002Fp>\n\n\u003Ch3>Laravel auditing vs Spatie activity log?\u003C\u002Fh3>\n\u003Cp>Auditing stores old\u002Fnew attribute diffs on a model. Spatie activity log stores a description of an activity, optionally with properties. Use auditing for field-level trails; use activity log for “User X approved CAPA Y” style events. Many apps use both.\u003C\u002Fp>\n\n\u003Ch3>Is the Laravel auditing package worth it?\u003C\u002Fh3>\n\u003Cp>Yes if you keep answering “who changed this row?” or you need a basic compliance trail on Eloquent data. Skip it for throwaway CRUD with no accountability, or if you already have a mature event-sourcing store.\u003C\u002Fp>\n\n\u003Ch3>Does Laravel auditing work with SoftDeletes?\u003C\u002Fh3>\n\u003Cp>Yes if you enable \u003Ccode>deleted\u003C\u002Fcode> and \u003Ccode>restored\u003C\u002Fcode> events. A force delete may still need an extra policy so you don’t wipe the only copy of history by cascading the audits table without a backup.\u003C\u002Fp>\n\n\u003Ch2>Summary\u003C\u002Fh2>\n\u003Cp>The Laravel auditing package gives you a single, morph-based history of Eloquent changes: old values, new values, actor, and event. Install it, trait the models that matter, and keep secrets out of JSON.\u003C\u002Fp>\n\u003Cp>It will not see mass \u003Ccode>update()\u003C\u002Fcode> queries or \u003Ccode>saveQuietly()\u003C\u002Fcode>. Plan resolvers for jobs, indexes for the \u003Ccode>audits\u003C\u002Fcode> table, and retention before the table outgrows the feature.\u003C\u002Fp>\n\u003Cp>Next: pick one critical model (Document, Order, User role assignment), enable audits, and ship a History tab. For Laravel + Nuxt product work, \u003Ca href=\"\u002Fabout\">get in touch\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Ch2>Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Audit package = Eloquent field diffs in an \u003Ccode>audits\u003C\u002Fcode> table, not a generic logger.\u003C\u002Fli>\n\u003Cli>Trait only business models; exclude passwords and huge columns.\u003C\u002Fli>\n\u003Cli>Mass updates and quiet saves skip audits because they skip model events.\u003C\u002Fli>\n\u003Cli>Index morph columns and prune high-churn data.\u003C\u002Fli>\n\u003Cli>Use Spatie activity log for human events; use auditing for attribute history — they solve different jobs.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786778101029-mwb9sf.webp","Laravel Auditing Package: Track Model Changes","Use the Laravel auditing package to log who changed what, restore history, and avoid homemade audit tables. Setup, morphs, and common mistakes.","",[19,20,21,22,23],"Laravel","Auditing","PHP","Security","Activity Log","published","2026-08-15T21:24:32.135+00:00",14,null,"2026-08-15T07:15:10.656409+00:00","2026-08-15T21:24:32.194447+00:00",[31,46,63,79,93,107,119,131,144,156,167,178,180,193,207,218,229,238,249,263,275,284,295,308],{"id":32,"title":33,"slug":34,"excerpt":35,"cover_image":36,"tags":37,"published_at":43,"updated_at":44,"view_count":45},"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",[38,39,40,41,42,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":47,"title":48,"slug":49,"excerpt":50,"cover_image":51,"tags":52,"published_at":60,"updated_at":61,"view_count":62},"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",[53,54,55,39,6,56,57,58,59],"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":64,"title":65,"slug":66,"excerpt":67,"cover_image":68,"tags":69,"published_at":76,"updated_at":77,"view_count":78},"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,70,71,72,73,74,75],"Sanctum","CSRF","419","SPA","Nuxt","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":80,"title":81,"slug":82,"excerpt":83,"cover_image":84,"tags":85,"published_at":90,"updated_at":91,"view_count":92},"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",[74,86,87,88,89],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":94,"title":95,"slug":96,"excerpt":97,"cover_image":98,"tags":99,"published_at":105,"updated_at":106,"view_count":62},"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",[100,101,102,103,104],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":108,"title":109,"slug":110,"excerpt":111,"cover_image":112,"tags":113,"published_at":116,"updated_at":117,"view_count":118},"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",[100,114,101,104,103,115],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":120,"title":121,"slug":122,"excerpt":123,"cover_image":124,"tags":125,"published_at":128,"updated_at":129,"view_count":130},"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",[126,101,114,103,127,115],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":132,"title":133,"slug":134,"excerpt":135,"cover_image":136,"tags":137,"published_at":141,"updated_at":142,"view_count":143},"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,138,139,21,140],"Queues","Jobs","backend","2026-08-21T04:36:56.222+00:00","2026-08-21T04:36:56.606735+00:00",20,{"id":145,"title":146,"slug":147,"excerpt":148,"cover_image":149,"tags":150,"published_at":154,"updated_at":155,"view_count":26},"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,151,152,153,21],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",{"id":157,"title":158,"slug":159,"excerpt":160,"cover_image":161,"tags":162,"published_at":164,"updated_at":165,"view_count":166},"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,151,21,163,140],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":168,"title":169,"slug":170,"excerpt":171,"cover_image":172,"tags":173,"published_at":176,"updated_at":177,"view_count":62},"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,174,151,21,175],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":179,"published_at":25,"updated_at":29,"view_count":26},[19,20,21,22,23],{"id":181,"title":182,"slug":183,"excerpt":184,"cover_image":185,"tags":186,"published_at":190,"updated_at":191,"view_count":192},"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,21,187,188,189],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":194,"title":195,"slug":196,"excerpt":197,"cover_image":198,"tags":199,"published_at":205,"updated_at":206,"view_count":26},"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",[200,201,202,203,204],"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":208,"title":209,"slug":210,"excerpt":211,"cover_image":212,"tags":213,"published_at":216,"updated_at":217,"view_count":166},"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",[74,188,214,215,87],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":219,"title":220,"slug":221,"excerpt":222,"cover_image":223,"tags":224,"published_at":227,"updated_at":228,"view_count":130},"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",[74,87,214,225,226],"Lifecycle","JavaScript","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":230,"title":231,"slug":232,"excerpt":233,"cover_image":234,"tags":235,"published_at":236,"updated_at":237,"view_count":92},"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.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785833713437-wcqb6c.webp",[19,70,75,21,73,22],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":239,"title":240,"slug":241,"excerpt":242,"cover_image":243,"tags":244,"published_at":247,"updated_at":248,"view_count":166},"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,70,245,75,21,246,73],"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,189,257,258,21,88,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":130},"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",[88,226,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":26},"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",[226,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":166},"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,70,291,292,73],"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,21,302,303,189,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":143},"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,21,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,88,402,226],"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,21,400,399,226,88,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,88],"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,88],"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,88,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"]