<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jayprakash Jangir on Medium]]></title>
        <description><![CDATA[Stories by Jayprakash Jangir on Medium]]></description>
        <link>https://medium.com/@jayprakashj?source=rss-8fce4d999f0d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XRBL8pQyhNX8-oKz0SH21g.jpeg</url>
            <title>Stories by Jayprakash Jangir on Medium</title>
            <link>https://medium.com/@jayprakashj?source=rss-8fce4d999f0d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:56:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jayprakashj/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Effortlessly Import Large MySQL Dumps into Docker: A Step-by-Step Guide]]></title>
            <link>https://medium.com/@jayprakashj/effortlessly-import-large-mysql-dumps-into-docker-a-step-by-step-guide-61f90482d04d?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/61f90482d04d</guid>
            <category><![CDATA[phpmyadmin]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 09:25:04 GMT</pubDate>
            <atom:updated>2025-10-15T09:25:04.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j9CTjszsbvQBNCfjIHKO8Q.png" /></figure><h3>Introduction</h3><p>If you’re managing web applications in Docker — especially Laravel, WordPress, or PHP projects — you’ll often need to import production data into your local environment for debugging or testing.</p><p>But what happens when your SQL dump is hundreds of megabytes and phpMyAdmin just gives up?</p><p>In this guide, we’ll walk through how to <strong>import a large MySQL dump (</strong><strong>.sql.gz) into a Dockerized MySQL container</strong>, even if you already have a database and just want to refresh one table.</p><h3>1. Understanding the Setup</h3><p>Here’s a typical local Docker setup:</p><pre>php83        → PHP 8.3 container<br>mysql57      → MySQL 5.7 container<br>phpmyadmin   → phpMyAdmin (port 5050)<br>nginx        → Web server (port 80/443)</pre><p>And we have a large production dump file:</p><pre>~/Downloads/your_table.sql.gz</pre><p>Our goal: <strong>Replace the data of the </strong><strong>your_table table</strong> in an existing database.</p><h3>2. Copy the Dump File into the MySQL Container</h3><p>We’ll start by copying the file from macOS into the MySQL container:</p><pre>docker cp ~/Downloads/your_table.sql.gz mysql57:/tmp/</pre><p>This puts the file in the container’s /tmp folder, ready for import.</p><h3>3. Access the MySQL Container</h3><pre>docker exec -it mysql57 /bin/bash</pre><p>Once inside, verify:</p><pre>ls /tmp</pre><p>You should see:</p><pre>your_table.sql.gz</pre><h3>4. (Optional) Truncate the Existing Table</h3><p>If you already have a database and just want to refresh one table:</p><pre>mysql -u root -p</pre><p>Then inside the MySQL shell:</p><pre>USE your_database_name;<br>TRUNCATE TABLE your_table;<br>EXIT;</pre><h3>5. Decompress and Import the Dump</h3><p>Still inside the container:</p><pre>cd /tmp<br>gunzip your_table.sql.gz<br>mysql -u root -p your_database_name &lt; /tmp/your_table.sql</pre><p>This unzips and imports the data directly into your existing table.</p><h3>6. Verify in phpMyAdmin</h3><p>Visit:</p><pre>http://localhost:5050</pre><p>Login using:</p><pre>Server: mysql57<br>Username: root<br>Password: &lt;your password&gt;</pre><p>Open your database → check your_table → you’ll see the fresh data loaded successfully!</p><h3>7. (Bonus) One-Line Automation</h3><p>You can even automate this with a single command:</p><pre>docker cp ~/Downloads/your_table.sql.gz mysql57:/tmp/ &amp;&amp; \<br>docker exec -it mysql57 bash -c &quot;cd /tmp &amp;&amp; gunzip -f your_table.sql.gz &amp;&amp; mysql -u root -pYOURPASSWORD your_database_name &lt; /tmp/your_table.sql&quot;</pre><p>(Replace YOURPASSWORD and your_database_name and your_tableaccordingly.)</p><h3>Conclusion</h3><p>Importing large SQL dumps into Docker doesn’t have to be painful.<br> With a few CLI commands, you can easily refresh your local MySQL database — no need to fight phpMyAdmin upload limits again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61f90482d04d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding SGI in Python: WSGI vs ASGI Explained]]></title>
            <link>https://medium.com/@jayprakashj/understanding-sgi-in-python-wsgi-vs-asgi-explained-9658382e783a?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9658382e783a</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[fastapi]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 17:32:57 GMT</pubDate>
            <atom:updated>2025-08-25T17:32:57.774Z</atom:updated>
            <content:encoded><![CDATA[<p>When building modern Python web applications, one crucial layer often goes unnoticed: <strong>SGI (Server Gateway Interface)</strong>. It acts as the <strong>bridge between your Python code and the web server</strong>, ensuring HTTP requests and responses flow smoothly.</p><p>Over time, two main standards have emerged:</p><ul><li><strong>WSGI</strong> (Web Server Gateway Interface)</li><li><strong>ASGI</strong> (Asynchronous Server Gateway Interface)</li></ul><p>This blog will break down <strong>what they are, how they differ, and why ASGI is shaping the future</strong> of Python web frameworks.</p><h3>What is SGI?</h3><p>SGI defines a <strong>common interface</strong> between:</p><ul><li>A <strong>Python application</strong> (Django, FastAPI, Flask, etc.)</li><li>A <strong>web server</strong> (Gunicorn, Uvicorn, Daphne, etc.)</li></ul><p>Without it, every framework would need custom server integrations — making deployment chaotic. SGI is like the <strong>universal adapter</strong> that ensures Python apps can run anywhere.</p><h3>WSGI: The Synchronous Workhorse</h3><p><strong>WSGI (Web Server Gateway Interface)</strong> was introduced in <strong>PEP 333 (2003)</strong> and has powered Python web for two decades.</p><h3>Characteristics:</h3><ul><li><strong>Synchronous only</strong>: Works in a request-response cycle.</li><li>Great for <strong>CPU-bound tasks</strong> (business logic, rendering templates).</li><li>Well-supported by servers like <strong>Gunicorn, uWSGI, mod_wsgi</strong>.</li></ul><h3>Example: A Minimal WSGI App</h3><pre>def app(environ, start_response):<br>    response_body = b&quot;Hello, WSGI World!&quot;<br>    status = &quot;200 OK&quot;<br>    headers = [(&quot;Content-Type&quot;, &quot;text/plain&quot;)]<br>    start_response(status, headers)<br>    return [response_body]</pre><p>Frameworks like <strong>Flask</strong> and <strong>Django (pre-3.0)</strong> rely heavily on WSGI.</p><h3>Limitation:</h3><ul><li>Cannot handle <strong>concurrent connections</strong> efficiently.</li><li>Blocking operations (like waiting for an API call) freeze the server thread.</li></ul><h3>ASGI: The Async-Ready Successor</h3><p><strong>ASGI (Asynchronous Server Gateway Interface)</strong> was introduced in <strong>2016</strong> as the spiritual successor to WSGI.</p><h3>Characteristics:</h3><ul><li>Supports <strong>both sync and async</strong>.</li><li>Handles <strong>long-lived connections</strong> (WebSockets, HTTP/2, GraphQL subscriptions).</li><li>Powered by servers like <strong>Uvicorn, Daphne, Hypercorn</strong>.</li></ul><h3>Example: A Minimal ASGI App</h3><pre>async def app(scope, receive, send):<br>    assert scope[&quot;type&quot;] == &quot;http&quot;<br>    await send({<br>        &quot;type&quot;: &quot;http.response.start&quot;,<br>        &quot;status&quot;: 200,<br>        &quot;headers&quot;: [(b&quot;content-type&quot;, b&quot;text/plain&quot;)],<br>    })<br>    await send({<br>        &quot;type&quot;: &quot;http.response.body&quot;,<br>        &quot;body&quot;: b&quot;Hello, ASGI World!&quot;,<br>    })</pre><p>Frameworks like <strong>FastAPI</strong>, <strong>Starlette</strong>, and <strong>Django 3.0+</strong> (with channels) support ASGI.</p><h3>WSGI vs ASGI: Key Differences</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q2XnJP1kqHyDrpw7CJZybQ.png" /></figure><h3>Real-World Implications</h3><p><strong>1) Traditional Sites (Blogs, Admin Panels)</strong></p><ul><li>WSGI is sufficient.</li><li>Flask + Gunicorn works great.</li></ul><p><strong>2) Modern APIs / Real-time Apps</strong></p><ul><li>ASGI is essential.</li><li>FastAPI + Uvicorn scales to thousands of connections.</li><li>WebSockets for chat, IoT, streaming are <strong>not possible with WSGI.</strong></li></ul><h3>Migration &amp; Coexistence</h3><ul><li><strong>Django</strong> is a great example:</li><li>Traditional requests → via WSGI</li><li>WebSockets / async views → via ASGI (with Channels)</li></ul><p>This means you don’t have to abandon WSGI apps — ASGI can run both.</p><h3>Conclusion</h3><ul><li><strong>WSGI</strong>: Reliable, battle-tested, still relevant for synchronous apps.</li><li><strong>ASGI</strong>: Future-proof, async-native, built for modern real-time applications.</li></ul><p>If you’re starting a new <strong>API-first or real-time project</strong>, <strong>ASGI is the way forward</strong>.</p><p><em>Rule of Thumb:</em><br> If your app needs <strong>WebSockets, HTTP/2, or high concurrency</strong> → Use <strong>ASGI</strong>.<br> If you’re running a <strong>classic synchronous web app</strong> → WSGI is fine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9658382e783a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Laravel Relationships: A Complete Guide with Examples]]></title>
            <link>https://medium.com/@jayprakashj/mastering-laravel-relationships-a-complete-guide-with-examples-c688c00cd18e?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c688c00cd18e</guid>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 14:14:14 GMT</pubDate>
            <atom:updated>2025-08-20T14:14:14.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5EuhIF7CpFr8l_Ev1Q7Jg.png" /></figure><p>Laravel makes working with databases elegant and efficient. One of its most powerful features is <strong>Eloquent Relationships</strong>, which allow you to define how your database tables interact with each other.</p><p>In this article, we’ll explore all types of relationships in Laravel, from <strong>one-to-one</strong> to <strong>many-to-many polymorphic</strong>. Each relationship is explained with examples so you can directly apply them to your projects.</p><h3>1. One-to-One Relationship</h3><p>A <strong>one-to-one</strong> relationship is when one record is associated with exactly one other record.</p><p><strong>Example:</strong> A User has one Profile.</p><h3>Database Structure:</h3><ul><li>users table</li><li>profiles table with user_id</li></ul><h3>Models</h3><p><strong>User.php</strong></p><pre>public function profile()<br>{<br>    return $this-&gt;hasOne(Profile::class);<br>}</pre><p><strong>Profile.php</strong></p><pre>public function user()<br>{<br>    return $this-&gt;belongsTo(User::class);<br>}</pre><h3>2. One-to-Many Relationship</h3><p>A <strong>one-to-many</strong> relationship means one record can have multiple related records.</p><p><strong>Example:</strong> A User can write many Posts.</p><h3>Database Structure:</h3><ul><li>users table</li><li>posts table with user_id</li></ul><h3>Models</h3><p><strong>User.php</strong></p><pre>public function posts()<br>{<br>    return $this-&gt;hasMany(Post::class);<br>}</pre><p><strong>Post.php</strong></p><pre>public function user()<br>{<br>    return $this-&gt;belongsTo(User::class);<br>}</pre><h3>3. Many-to-Many Relationship</h3><p>A <strong>many-to-many</strong> relationship allows records to be linked to multiple other records.</p><p><strong>Example:</strong> Users can have many Roles, and Roles can belong to many Users.</p><h3>Database Structure:</h3><ul><li>users</li><li>roles</li><li>role_user (pivot table)</li></ul><h3>Models</h3><p><strong>User.php</strong></p><pre>public function roles()<br>{<br>    return $this-&gt;belongsToMany(Role::class, &#39;role_user&#39;, &#39;user_id&#39;, &#39;role_id&#39;);<br>}</pre><p><strong>Role.php</strong></p><pre>public function users()<br>{<br>    return $this-&gt;belongsToMany(User::class, &#39;role_user&#39;, &#39;role_id&#39;, &#39;user_id&#39;);<br>}</pre><h3>4. Has One Through</h3><p>The <strong>has-one-through</strong> relationship allows accessing a related model through an intermediate model.</p><p><strong>Example:</strong> A User has one Address through Profile.</p><h3>Models</h3><p><strong>User.php</strong></p><pre>public function address()<br>{<br>    return $this-&gt;hasOneThrough(Address::class, Profile::class, &#39;user_id&#39;, &#39;profile_id&#39;, &#39;id&#39;, &#39;id&#39;);<br>}</pre><p><strong>Profile.php</strong></p><pre>public function address()<br>{<br>    return $this-&gt;hasOne(Address::class);<br>}</pre><p><strong>Address.php</strong></p><pre>public function profile()<br>{<br>    return $this-&gt;belongsTo(Profile::class);<br>}</pre><h3>5. Has Many Through</h3><p>The <strong>has-many-through</strong> relationship is useful for accessing distant relations.</p><p><strong>Example:</strong> A Website has many Posts through Users.</p><h3>Models</h3><p><strong>Website.php</strong></p><pre>public function posts()<br>{<br>    return $this-&gt;hasManyThrough(Post::class, User::class, &#39;website_id&#39;, &#39;user_id&#39;, &#39;id&#39;, &#39;id&#39;);<br>}<br><br>public function users()<br>{<br>    return $this-&gt;hasMany(User::class);<br>}</pre><p><strong>User.php</strong></p><pre>public function posts()<br>{<br>    return $this-&gt;hasMany(Post::class);<br>}</pre><p><strong>Post.php</strong></p><pre>public function website()<br>{<br>    return $this-&gt;belongsTo(Website::class);<br>}<br>public function user()<br>{<br>    return $this-&gt;belongsTo(User::class);<br>}</pre><h3>6. One-to-One (Polymorphic)</h3><p>Polymorphic relationships allow a model to belong to multiple other models.</p><p><strong>Example:</strong> A User or Post can have one featured Image.</p><h3>Database Structure:</h3><ul><li>images table with imageable_id &amp; imageable_type</li></ul><h3>Models</h3><p><strong>User.php</strong></p><pre>public function featuredImage()<br>{<br>    return $this-&gt;morphOne(Image::class, &#39;imageable&#39;);<br>}</pre><p><strong>Post.php</strong></p><pre>public function featuredImage()<br>{<br>    return $this-&gt;morphOne(Image::class, &#39;imageable&#39;);<br>}</pre><p><strong>Image.php</strong></p><pre>public function imageable()<br>{<br>    return $this-&gt;morphTo();<br>}</pre><h3>7. One-to-Many (Polymorphic)</h3><p><strong>Example:</strong> Both Posts and Videos can have multiple Comments.</p><h3>Database Structure:</h3><ul><li>comments table with commentable_id &amp; commentable_type</li></ul><h3>Models</h3><p><strong>Post.php</strong></p><pre>public function comments()<br>{<br>    return $this-&gt;morphMany(Comment::class, &#39;commentable&#39;);<br>}</pre><p><strong>Video.php</strong></p><pre>public function comments()<br>{<br>    return $this-&gt;morphMany(Comment::class, &#39;commentable&#39;);<br>}</pre><p><strong>Comment.php</strong></p><pre>public function commentable()<br>{<br>    return $this-&gt;morphTo();<br>}</pre><h3>8. Many-to-Many (Polymorphic)</h3><p><strong>Example:</strong> Posts and Videos can have multiple Tags.</p><h3>Database Structure:</h3><ul><li>taggables table with tag_id, taggable_id, and taggable_type</li></ul><h3>Models</h3><p><strong>Post.php</strong></p><pre>public function tags()<br>{<br>    return $this-&gt;morphToMany(Tag::class, &#39;taggable&#39;);<br>}</pre><p><strong>Video.php</strong></p><pre>public function tags()<br>{<br>    return $this-&gt;morphToMany(Tag::class, &#39;taggable&#39;);<br>}</pre><p><strong>Tag.php</strong></p><pre>public function posts()<br>{<br>    return $this-&gt;morphedByMany(Post::class, &#39;taggable&#39;);<br>}<br><br>public function videos()<br>{<br>    return $this-&gt;morphedByMany(Video::class, &#39;taggable&#39;);<br>}</pre><h3>Final Thoughts</h3><p>Laravel relationships make database interactions simple and intuitive. By defining relationships in your models, you can query related data with minimal effort and keep your code clean.</p><p>Here’s a quick recap of what we covered:</p><ul><li>One-to-One</li><li>One-to-Many</li><li>Many-to-Many</li><li>HasOneThrough &amp; HasManyThrough</li><li>Polymorphic Relationships</li></ul><p>Mastering these will help you design more efficient and scalable applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c688c00cd18e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Version Control with Git: A Complete Guide for Developers]]></title>
            <link>https://medium.com/@jayprakashj/mastering-version-control-with-git-a-complete-guide-for-developers-37dc29fdb9af?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/37dc29fdb9af</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Tue, 12 Aug 2025 07:15:53 GMT</pubDate>
            <atom:updated>2025-08-12T07:15:53.817Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CjaOdgntGE9yu3zzJr2oRg.png" /></figure><h3>1. What is Version Control?</h3><p>Version control is a system that helps you track changes to files over time. It allows you to:</p><ul><li>Maintain a history of code changes.</li><li>Restore previous versions when needed.</li><li>Collaborate with other developers without overwriting each other’s work.</li></ul><p>Without version control, tracking project history and coordinating changes would be a nightmare — especially for team projects.</p><h3>2. Types of Version Control</h3><h4>Centralized Version Control (CVCS)</h4><p>In a CVCS, there’s a single central server that stores all versions of a project. Developers commit changes directly to this server.</p><ul><li><strong>Examples:</strong> Subversion (SVN), Perforce.</li><li><strong>Pros:</strong> Easy to understand, central authority.</li><li><strong>Cons:</strong> Single point of failure, requires constant internet access.</li></ul><h4>Distributed Version Control (DVCS)</h4><p>In a DVCS, each developer has a full copy of the repository, including its history. Changes can be committed locally and later pushed to a shared remote repository.</p><ul><li><strong>Examples:</strong> Git, Mercurial.</li><li><strong>Pros:</strong> Works offline, faster operations, no single point of failure.</li><li><strong>Cons:</strong> Slightly higher learning curve.</li></ul><h3>3. Introduction to Git</h3><p>Git is a <strong>distributed version control system</strong> created by Linus Torvalds in 2005 for Linux kernel development. It’s now the most widely used VCS worldwide.</p><p><strong>Key advantages:</strong></p><ul><li>Lightweight and fast.</li><li>Full local history of the project.</li><li>Powerful branching and merging.</li></ul><h3>4. Git Lifecycle</h3><p>The Git workflow revolves around three main states:</p><ol><li><strong>Working Directory</strong> — where you make changes to files.</li><li><strong>Staging Area (Index)</strong> — where you prepare changes for commit.</li><li><strong>Repository (Local)</strong> — where committed changes are stored.</li></ol><p>[Workflow Diagram — Working Directory → Staging Area → Repository]</p><h3>5. How Does Git Work?</h3><ul><li>Files move from the working directory to the staging area with git add.</li><li>You save changes to the repository with git commit.</li><li>You synchronize with a remote server using git push and git pull.</li><li>Git uses <strong>snapshots</strong> (not file differences), making it very fast.</li></ul><h3>6. Common Git Commands</h3><p>Command Description</p><p>git init Initialize a new repository</p><p>git status show the current status of files</p><p>git branch List, create, or delete branches</p><p>git checkout Switch to a branch</p><p>git log View commit history</p><p>git stash Temporarily save changes without committing</p><p>git revertUndo a specific commit</p><h3>7. Merging Branches</h3><h4>Merge (git merge)</h4><p>Combines changes from one branch into another, preserving both histories.</p><h4>Rebase (git rebase)</h4><p>Moves commits from one branch on top of another to create a linear history.</p><h3>Conclusion</h3><p>Git is more than just a tool — it’s the backbone of modern software collaboration. Whether you’re working alone or in a team, mastering Git will make your workflow smoother, your code safer, and your productivity higher.</p><p>💬 <em>Which Git command do you use the most?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37dc29fdb9af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Waterfall to DevOps: The Evolution of Software Delivery]]></title>
            <link>https://medium.com/@jayprakashj/from-waterfall-to-devops-the-evolution-of-software-delivery-852f853bbb6f?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/852f853bbb6f</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Mon, 11 Aug 2025 06:51:25 GMT</pubDate>
            <atom:updated>2025-08-11T06:51:25.338Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pnUuY0lswQmEli3A-VX4EA.png" /></figure><h3>The Evolution of Software Development: From Waterfall to DevOps</h3><p>Software development has undergone significant transformations to meet the demands of faster delivery, enhanced collaboration, and increased automation. This evolution has taken us from traditional models to the now prevalent DevOps approach.</p><h3>A Brief History of Development Models</h3><p>The Waterfall Model, a linear and sequential approach, was one of the earliest methodologies. Its simplicity and well-documented processes were advantageous for projects with fixed requirements. However, its inflexibility to changes and late-stage testing proved problematic for dynamic projects.</p><p>The Agile Model emerged as a response, offering an iterative and incremental approach that prioritized flexibility, collaboration, and customer feedback. While Agile improved adaptability and customer satisfaction, it required continuous customer involvement and experienced teams to effectively manage sprints.</p><h3>The Rise of DevOps</h3><p>Agile addressed many issues, but challenges persisted in deployment, operations, and collaboration between development and operations teams. DevOps arose to bridge this gap, emphasizing automation, collaboration, and continuous delivery.</p><p>DevOps is a cultural and technical practice uniting software development (Dev) and IT operations (Ops) to accelerate the development lifecycle and ensure continuous delivery of high-quality software. Its core principles include collaboration, automation, continuous improvement, and measurement, aiming to deliver features faster, enhance reliability, and rapidly respond to feedback.</p><h3>How DevOps Works: A Continuous Cycle</h3><p>DevOps operates through continuous practices:</p><ul><li>Continuous Development: Code is continuously developed and version-controlled (e.g., using GitHub, GitLab).</li><li>Continuous Integration (CI): Developers frequently integrate code into a shared repository where it’s automatically tested (e.g., using Jenkins, CircleCI).</li><li>Continuous Deployment (CD): Code changes are automatically deployed to production after passing tests (e.g., using Docker, Kubernetes).</li><li>Continuous Testing: Automated tests run alongside development to catch bugs early (e.g., using Selenium, JUnit).</li><li>Continuous Monitoring: Application performance and infrastructure health are constantly tracked (e.g., using Nagios, Grafana).</li></ul><h3>Benefits of DevOps</h3><p>Adopting DevOps yields numerous benefits, including faster feature delivery, better team collaboration, reduced deployment failures, and improved scalability and reliability.</p><h3>Conclusion</h3><p>The journey from Waterfall to Agile and finally to DevOps reflects the industry’s continuous pursuit of efficiency and quality. DevOps is more than just a set of tools; it represents a mindset and a culture. Organizations should embrace DevOps gradually, focusing on automation and collaboration to achieve its full potential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=852f853bbb6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SSR & Hybrid Rendering with Laravel + React (Inertia.js & Next.js)]]></title>
            <link>https://medium.com/@jayprakashj/ssr-hybrid-rendering-with-laravel-react-inertia-js-next-js-93a6c16c214b?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/93a6c16c214b</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Thu, 08 May 2025 01:58:23 GMT</pubDate>
            <atom:updated>2025-05-08T01:58:23.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4g-ER_NZASEpaU3HHGWNCA.png" /></figure><p>In today’s SEO- and performance-conscious web world, <strong>Server-Side Rendering (SSR)</strong> or <strong>Hybrid Rendering</strong> has become essential — especially for dynamic applications. Using <strong>Laravel + React</strong>, developers can now enjoy the best of both worlds: <strong>robust backend APIs</strong> and <strong>SEO-friendly frontends</strong> using tools like <strong>Inertia.js</strong> or <strong>Next.js</strong>.</p><p>This guide explores:</p><ul><li>When to use SSR or hybrid rendering</li><li>Laravel + React via <strong>Inertia.js</strong> (SPA-feel with SSR support)</li><li>Laravel + Next.js (true SSR/hybrid apps)</li><li>Managing <strong>authentication and middleware logic</strong> across client &amp; server</li></ul><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a><br><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>1. 🧠 SSR vs Hybrid Rendering: What’s the Difference?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G8XdROXjTV6BhMe-lzf49A.png" /></figure><h3>2. ⚛️ Laravel + React + Inertia.js (Hybrid Rendering)</h3><p><strong>Inertia.js</strong> bridges the gap between full SPAs and traditional SSR pages.</p><h4>a. Installation</h4><p>Install Inertia + React adapter:</p><pre>npm install @inertiajs/inertia @inertiajs/inertia-react</pre><p>Server-side Inertia setup (Laravel):</p><pre>composer require inertiajs/inertia-laravel</pre><p>Basic route example:</p><pre>Route::get(&#39;/dashboard&#39;, function () {<br>    return Inertia::render(&#39;Dashboard&#39;, [&#39;user&#39; =&gt; Auth::user()]);<br>});</pre><p>React component:</p><pre>const Dashboard = ({ user }) =&gt; (<br>  &lt;div&gt;Welcome, {user.name}&lt;/div&gt;<br>);</pre><h4>b. SEO with Inertia + Laravel SSR</h4><p>Inertia supports SSR using <strong>Laravel + Node SSR bridge</strong> (experimental). You can also pre-render public pages using Inertia server render packages or fallback to traditional Blade.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a><br><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>3. 🌍 Laravel + Next.js (True SSR + API-Driven)</h3><p><strong>Next.js</strong> is a mature React framework that supports SSR, SSG, and hybrid rendering out-of-the-box.</p><h4>a. API-Driven Setup</h4><ul><li>Laravel exposes a RESTful or GraphQL API</li><li>Next.js fetches data from Laravel</li><li>SSR occurs using getServerSideProps or getStaticProps</li></ul><p>Example in Next.js:</p><pre>export async function getServerSideProps(context) {<br>  const res = await fetch(&#39;https://your-laravel-site.com/api/posts&#39;);<br>  const posts = await res.json();<br>  return { props: { posts } };<br>}</pre><h4>b. Handling Laravel Auth in Next.js</h4><p>For session-based auth (e.g., Sanctum), use:</p><pre>npm install axios</pre><p>In axios.js:</p><pre>axios.defaults.withCredentials = true;<br>axios.get(&#39;/sanctum/csrf-cookie&#39;).then(() =&gt; {<br>  axios.post(&#39;/login&#39;, { email, password });<br>});</pre><p>Ensure these settings in .env:</p><pre>SANCTUM_STATEFUL_DOMAINS=localhost:3000<br>SESSION_DOMAIN=localhost</pre><h3>4. 🔐 Shared Auth and Middleware Logic</h3><h4>a. Laravel Middleware Example</h4><p>Protect routes with Laravel:</p><pre>Route::middleware([&#39;auth&#39;])-&gt;group(function () {<br>    Route::get(&#39;/dashboard&#39;, [DashboardController::class, &#39;index&#39;]);<br>});</pre><h4>b. Inertia Middleware</h4><p>Create custom middleware to pass shared props:</p><pre>Inertia::share([<br>    &#39;auth.user&#39; =&gt; fn () =&gt; Auth::user(),<br>]);</pre><h4>c. Next.js Middleware</h4><p>Use middleware to protect SSR routes:</p><pre>import { NextResponse } from &#39;next/server&#39;;<br>export function middleware(req) {<br>  const token = req.cookies.get(&#39;token&#39;);<br>  if (!token) return NextResponse.redirect(&#39;/login&#39;);<br>  return NextResponse.next();<br>}</pre><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a><br><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Conclusion</h3><p>Choosing between Inertia.js and Next.js depends on your app’s complexity, SEO needs, and team preference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFb2QSbBt02pX6nrcpmLpQ.png" /></figure><p>In both cases, you can ensure robust authentication, API interaction, and SEO-friendly rendering, unlocking the power of <strong>modern web development with Laravel + React</strong>.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a><br><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93a6c16c214b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API-Driven Development with Laravel + React]]></title>
            <link>https://medium.com/@jayprakashj/api-driven-development-with-laravel-react-535ad6994ba8?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/535ad6994ba8</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Wed, 07 May 2025 02:06:41 GMT</pubDate>
            <atom:updated>2025-05-07T02:08:32.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="API-Driven Development with Laravel + React" src="https://cdn-images-1.medium.com/max/1024/1*Me710pp4-Z2gS6B-LzrPDQ.png" /></figure><p>In modern web development, API-driven architecture is the foundation of scalable, maintainable applications. Whether you’re building a single-page app (SPA) or a mobile backend, decoupling the frontend from the backend through APIs gives you greater flexibility, reusability, and control.</p><p>In this article, we’ll explore API-Driven Development using <strong>Laravel (backend)</strong> and <strong>React (frontend)</strong>. We’ll cover:</p><ul><li>Token-based authentication using <strong>JWT</strong> or <strong>Laravel Sanctum</strong></li><li><strong>API rate limiting</strong> and <strong>versioning</strong></li><li>Structuring responses using <strong>Resource Transformers</strong> and <strong>Fractal-style output</strong></li><li>Managing traffic through <strong>Request Throttling</strong> and <strong>Global API Middleware</strong></li></ul><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>1. 🔐 Token-Based Authentication (JWT / Laravel Sanctum)</h3><p>Laravel provides two main methods for stateless API authentication:</p><h4>a. Laravel Sanctum</h4><p>Lightweight and perfect for SPAs using cookies with CSRF protection.</p><p><strong>Installation:</strong></p><pre>composer require laravel/sanctum<br>php artisan vendor:publish --provider=&quot;Laravel\Sanctum\SanctumServiceProvider&quot;<br>php artisan migrate</pre><p><strong>Usage in </strong><strong>api.php:</strong></p><pre>Route::middleware(&#39;auth:sanctum&#39;)-&gt;get(&#39;/user&#39;, fn (Request $request) =&gt; $request-&gt;user());</pre><h4>b. JWT (JSON Web Token)</h4><p>Best for mobile APIs or external client integrations.</p><p><strong>Popular Package:</strong> tymon/jwt-auth</p><pre>composer require tymon/jwt-auth<br>php artisan vendor:publish --provider=&quot;Tymon\JWTAuth\Providers\LaravelServiceProvider&quot;<br>php artisan jwt:secret</pre><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>2. 🚦 API Rate Limiting and Versioning</h3><h4>a. Rate Limiting</h4><p>Prevent abuse and DoS attacks using Laravel’s built-in throttle middleware.</p><pre>Route::middleware(&#39;throttle:60,1&#39;)-&gt;group(function () {<br>    Route::get(&#39;/posts&#39;, [PostController::class, &#39;index&#39;]);<br>});</pre><p>This allows <strong>60 requests per minute per IP</strong>.</p><h4>b. API Versioning</h4><p>Create multiple versions of your API to prevent breaking changes.</p><p><strong>Directory Structure:</strong></p><pre>app/Http/Controllers/API/V1/PostController.php<br>app/Http/Controllers/API/V2/PostController.php</pre><p><strong>Routes:</strong></p><pre>Route::prefix(&#39;v1&#39;)-&gt;group(function () {<br>    Route::get(&#39;posts&#39;, [V1\PostController::class, &#39;index&#39;]);<br>});</pre><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>3. 🧱 Resource Transformers &amp; Fractal-Style API Responses</h3><p>API responses should be <strong>consistent</strong>, <strong>structured</strong>, and <strong>minimal</strong>.</p><h4>a. Laravel API Resources</h4><pre>class PostResource extends JsonResource<br>{<br>    public function toArray($request)<br>    {<br>        return [<br>            &#39;id&#39;    =&gt; $this-&gt;id,<br>            &#39;title&#39; =&gt; $this-&gt;title,<br>            &#39;body&#39;  =&gt; $this-&gt;body,<br>        ];<br>    }<br>}</pre><p><strong>Usage:</strong></p><pre>return PostResource::collection(Post::all());</pre><h4>b. Fractal-Style Output (Optional)</h4><p>Fractal provides powerful includes, meta info, and pagination.</p><p><strong>Package:</strong> spatie/laravel-fractal</p><pre>composer require spatie/laravel-fractal</pre><pre><br>fractal(Post::paginate())-&gt;transformWith(new PostTransformer())-&gt;toArray();</pre><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>4. 🧰 Request Throttling &amp; Global API Middleware</h3><p>To handle all API-related behavior, create a <strong>global middleware group</strong> in app/Http/Kernel.php.</p><pre>&#39;api&#39; =&gt; [<br>    \App\Http\Middleware\EnsureFrontendRequestsAreStateful::class,<br>    &#39;throttle:api&#39;,<br>    \Illuminate\Routing\Middleware\SubstituteBindings::class,<br>],</pre><p>You can also define <strong>custom throttling logic</strong> in RouteServiceProvider:</p><pre>RateLimiter::for(&#39;api&#39;, function (Request $request) {<br>    return Limit::perMinute(100)-&gt;by($request-&gt;user()?-&gt;id ?: $request-&gt;ip());<br>});</pre><h3>5. ⚛️ React as Frontend Consumer</h3><p>With Laravel API in place, React can now consume it using axios:</p><pre>axios.get(&#39;/api/v1/posts&#39;, {<br>  headers: {<br>    Authorization: `Bearer ${yourToken}`<br>  }<br>});</pre><p>For Sanctum, make sure your frontend and backend share the same domain or configure SANCTUM_STATEFUL_DOMAINS.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Final Thoughts</h3><p>API-driven development helps you build robust, scalable applications that serve both SPAs and mobile clients. By combining Laravel’s elegant backend features with React’s dynamic frontend capabilities, you gain the best of both worlds.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=535ad6994ba8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Laravel 12: A Comprehensive Guide to the Latest Features, Enhancements, and Installation]]></title>
            <link>https://medium.com/@jayprakashj/laravel-12-a-comprehensive-guide-to-the-latest-features-enhancements-and-installation-ee7ac73819ff?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee7ac73819ff</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[stammptech]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Fri, 21 Feb 2025 02:35:36 GMT</pubDate>
            <atom:updated>2025-02-21T02:35:36.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WqALoN-_cMncnkl-L_kyHA.jpeg" /></figure><p>Laravel 12, scheduled for release on February 24, 2025, marks a significant milestone in the evolution of this popular PHP framework. This version focuses on enhancing developer productivity, streamlining application structure, and introducing new features to facilitate modern web development.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Key Features and Enhancements</h3><h3>1. New Starter Kits</h3><p>Laravel 12 introduces versatile starter kits tailored to different frontend technologies:</p><ul><li><strong>Vue.js</strong>: A comprehensive setup integrating Vue.js seamlessly with Laravel, providing a robust foundation for building dynamic user interfaces.</li><li><strong>React</strong>: A React-based starter kit that simplifies the process of creating reactive and component-driven applications within the Laravel ecosystem.</li><li><strong>Livewire</strong>: For developers preferring server-driven UI updates, the Livewire starter kit offers an efficient way to build dynamic interfaces without extensive JavaScript.</li></ul><p>These starter kits incorporate components from the shadcn/ui library, ensuring a cohesive and modern design language across applications. Each kit is pulled directly from dedicated GitHub repositories, granting developers full control over the codebase and facilitating easier customisation.</p><h3>2. Enhanced Application Structure</h3><p>Building upon the structural refinements introduced in previous versions, Laravel 12 offers a more streamlined and minimalistic application setup:</p><ul><li><strong>Simplified Directory Layout</strong>: The framework now features a cleaner directory structure, reducing complexity and making navigation more intuitive.</li><li><strong>Optimized Configuration Files</strong>: Configuration files have been reorganized for better clarity, allowing developers to locate and manage settings with ease.</li></ul><p>This enhanced structure not only reduces the initial setup complexity but also aids in maintaining a clean codebase as the application scales.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>3. Performance Improvements</h3><p>Laravel 12 brings several performance optimizations to ensure faster and more efficient applications:</p><ul><li><strong>Asynchronous Caching</strong>: The framework now supports asynchronous caching operations, enabling non-blocking cache retrievals and updates, which is particularly beneficial for high-traffic applications.</li><li><strong>Optimised Query Execution</strong>: Enhancements in the Query Builder allow for more efficient database interactions, reducing latency and improving overall application responsiveness.</li><li><strong>Leveraging PHP 8 Features</strong>: By embracing modern PHP 8 capabilities, such as Just-In-Time (JIT) compilation, Laravel 12 achieves significant improvements in code execution speed.</li></ul><h3>4. Security Enhancements</h3><p>Security remains a top priority in Laravel 12, with several updates aimed at fortifying application defenses:</p><ul><li><strong>Improved Authentication and Authorisation</strong>: The framework offers enhanced mechanisms for user authentication and authorisation, simplifying the implementation of secure access controls.</li><li><strong>Advanced Encryption Protocols</strong>: Laravel 12 adopts stronger encryption standards, ensuring that sensitive data is protected using the latest security practices.</li><li><strong>Enhanced CSRF Protection</strong>: Cross-Site Request Forgery protections have been bolstered to provide an additional layer of security against malicious attacks.</li></ul><h3>5. Modernized Frontend Tooling</h3><p>Keeping pace with the evolving frontend ecosystem, Laravel 12 integrates seamlessly with contemporary tools:</p><ul><li><strong>Tailwind CSS 4.0</strong>: The framework includes out-of-the-box support for Tailwind CSS 4.0, enabling developers to craft modern, responsive designs with ease.</li><li><strong>Vite 6.0</strong>: Laravel 12 adopts Vite 6.0 as its default asset bundler, offering faster build times and an improved development experience.</li></ul><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Installation and Getting Started</h3><p>Upon its official release, developers can create a new Laravel 12 project using Composer:</p><pre>composer create-project --prefer-dist laravel/laravel project-name &quot;12.*&quot;</pre><p>Ensure that your development environment meets the minimum PHP version requirement of 8.2 to fully leverage Laravel 12’s features.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Conclusion</h3><p>Laravel 12 continues the framework’s tradition of combining elegance and functionality, empowering developers to build robust web applications efficiently. With its focus on performance, security, and modern development practices, Laravel 12 is poised to be a valuable asset for the developer community.</p><p><strong><em>Note: As Laravel 12 is in active development, some features and details may be subject to change upon official release.</em></strong></p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee7ac73819ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering php.ini Configuration for Laravel: Essential Settings & Best Practices ]]></title>
            <link>https://medium.com/@jayprakashj/mastering-php-ini-configuration-for-laravel-essential-settings-best-practices-3cd374877ce0?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cd374877ce0</guid>
            <category><![CDATA[configuration-file]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Wed, 12 Feb 2025 02:52:20 GMT</pubDate>
            <atom:updated>2025-02-12T02:52:20.367Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AhsQTN4Pg5dWHj_-kgqdPQ.jpeg" /></figure><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Introduction</h3><p>Laravel is a powerful PHP framework that requires proper configuration to function optimally. One crucial part of Laravel’s setup is <strong>PHP’s </strong><strong>php.ini file</strong>, which controls settings like memory limits, execution times, error handling, and file uploads.</p><p>Misconfigured php.ini settings can lead to performance issues, security vulnerabilities, and unexpected errors. In this guide, we’ll cover <strong>essential </strong><strong>php.ini configurations for Laravel</strong>, explain their impact, and provide best practices for optimizing your Laravel environment.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>What is php.ini?</h3><p>The php.ini file is PHP’s main configuration file that defines how PHP behaves on your server. Laravel, being a PHP framework, relies on these settings for smooth execution.</p><h3>Locating php.ini on Your System</h3><p>To find the php.ini file used by your server, run:</p><pre>php --ini</pre><p>or</p><pre>php -i | grep &quot;Loaded Configuration File&quot;</pre><p>This will display the path to the active php.ini file.</p><p>If using <strong>Laravel with PHP-FPM</strong> (e.g., Nginx), locate the php.ini file for FPM:</p><pre>php-fpm -i | grep &quot;Loaded Configuration File&quot;</pre><h3>Essential php.ini Configurations for Laravel</h3><p>Here are the most important php.ini settings that impact Laravel performance and functionality:</p><h3>1️⃣ Memory Limit — Prevents Out-of-Memory Errors</h3><p>By default, PHP has a low memory limit that may cause Laravel applications to crash when processing large data. Increase it to ensure smooth operation.</p><pre>memory_limit = 512M  ; Adjust according to application needs</pre><p>✔ <strong>Best Practice:</strong> Use at least 256M for small applications, 512M+ for larger ones.</p><h3>2️⃣ Maximum Execution Time — Avoid Timeouts in Long Operations</h3><p>Laravel jobs, migrations, and complex queries can take time to execute. If the script execution time is too short, it may terminate before completing.</p><pre>max_execution_time = 300  ; 300 seconds (5 minutes)</pre><p>✔ <strong>Best Practice:</strong> Set max_execution_time to 300 seconds for complex applications.</p><h3>3️⃣ Maximum Input Variables — Prevent Data Loss in Large Forms</h3><p>If you work with large forms (e.g., <strong>multi-step forms, dynamic forms</strong>), PHP may not process all submitted variables.</p><pre>max_input_vars = 3000  ; Increase for large forms</pre><p>✔ <strong>Best Practice:</strong> Use 3000+ for applications handling large form submissions.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>4️⃣ File Upload Limits — Adjusting Upload Size in Laravel</h3><p>If you handle file uploads (images, PDFs, videos), PHP’s default upload limits may be too restrictive. Increase the limits as needed.</p><pre>upload_max_filesize = 100M   ; Max file size for uploads<br>post_max_size = 110M         ; Slightly larger to handle form submissions</pre><p>✔ <strong>Best Practice:</strong> Set upload_max_filesize slightly lower than post_max_size to avoid errors.</p><h3>5️⃣ Error Reporting &amp; Logging — Improve Debugging</h3><p>For Laravel development, enable <strong>detailed error reporting</strong>:</p><pre>display_errors = On<br>log_errors = On<br>error_reporting = E_ALL</pre><p>✔ <strong>Best Practice:</strong></p><ul><li>Set display_errors = Off in <strong>production</strong> to avoid leaking sensitive info.</li><li>Keep log_errors = On in <strong>both development and production</strong>.</li></ul><h3>6️⃣ Session Handling — Optimize User Sessions</h3><p>Laravel sessions depend on PHP’s session settings. Configure them properly for better performance.</p><pre>session.gc_maxlifetime = 1440  ; Default is 24 minutes (adjust as needed)<br>session.save_path = &quot;/var/lib/php/sessions&quot;  ; Ensure the path exists</pre><p>✔ <strong>Best Practice:</strong> If using <strong>Redis or Database</strong> for sessions, Laravel overrides php.ini settings.</p><h3>7️⃣ Opcache Settings — Boost Laravel Performance 🚀</h3><p>Opcache caches PHP scripts in memory, significantly improving Laravel’s speed.<br>Enable and configure it in php.ini:</p><pre>opcache.enable=1<br>opcache.memory_consumption=256<br>opcache.max_accelerated_files=10000<br>opcache.validate_timestamps=0</pre><p>✔ <strong>Best Practice:</strong></p><ul><li><strong>Set </strong><strong>opcache.validate_timestamps = 0</strong> in production for better performance.</li><li>If developing, use 1 to reload code changes automatically.</li></ul><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Applying Changes &amp; Restarting PHP</h3><p>After modifying php.ini, restart your web server for changes to take effect:</p><p>For Apache:</p><pre>sudo systemctl restart apache2</pre><p>For Nginx with PHP-FPM:</p><pre>sudo systemctl restart php-fpm</pre><h3>Verifying Changes in Laravel</h3><p>To confirm the new settings, create a route in web.php:</p><pre>Route::get(&#39;/php-info&#39;, function() {<br>    return phpinfo();<br>});</pre><p>Visit http://your-domain.com/php-info to see the updated configuration.</p><h3>Best Practices for Managing php.ini in Laravel</h3><p>✅ <strong>Separate Development &amp; Production Configurations</strong> — Avoid using the same php.ini settings in both environments.<br>✅ <strong>Use </strong><strong>.user.ini for Shared Hosting</strong> – If you don’t have access to php.ini, create a .user.ini file in Laravel’s public folder with custom settings.<br>✅ <strong>Automate Configuration with Ansible or Docker</strong> – If deploying Laravel via <strong>Docker or Ansible</strong>, manage php.ini dynamically.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Conclusion</h3><p>Configuring php.ini properly is <strong>essential for Laravel performance and stability</strong>. By tuning memory limits, execution times, session handling, and caching settings, you can <strong>optimize Laravel applications for both development and production</strong>.</p><p>🚀 <strong>Want Laravel to run faster? Adjust your </strong><strong>php.ini settings today!</strong> 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cd374877ce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering GitHub & GitHub Copilot for PHP Development ]]></title>
            <link>https://medium.com/@jayprakashj/mastering-github-github-copilot-for-php-development-ebe10ce68255?source=rss-8fce4d999f0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebe10ce68255</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Jayprakash Jangir]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 05:41:14 GMT</pubDate>
            <atom:updated>2025-01-29T05:41:14.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UgOrvIw49sP4VAe77brXjg.jpeg" /><figcaption>Mastering GitHub &amp; GitHub Copilot for PHP Development</figcaption></figure><h3>Introduction</h3><p>As a PHP developer, managing your projects efficiently and writing clean, optimized code are crucial skills. <strong>GitHub</strong> simplifies collaboration and version control, while <strong>GitHub Copilot</strong>, powered by AI, speeds up coding with intelligent suggestions.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><p>In this guide, we’ll cover:</p><p>✅ <strong>GitHub Basics &amp; Best Practices</strong><br>✅ <strong>Using GitHub for PHP Projects</strong><br>✅ <strong>GitHub Copilot for PHP: Real-World Examples</strong><br>✅ <strong>Best Practices for PHP Developers</strong></p><h3>Part 1: GitHub for PHP Development</h3><h3>What is GitHub?</h3><p>GitHub is a <strong>Git-based platform</strong> for managing, collaborating on, and deploying code. It enables version control, branch management, and automated deployments.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Essential GitHub Features for PHP Developers</h3><ol><li><strong>Version Control:</strong> Track code changes and roll back if needed.</li><li><strong>Pull Requests &amp; Code Reviews:</strong> Collaborate with your team on changes before merging.</li><li><strong>GitHub Actions:</strong> Automate PHP testing and deployment (e.g., running PHPUnit).</li><li><strong>GitHub Pages:</strong> Host PHP documentation or static websites.</li><li><strong>Security Features:</strong> Identify and fix vulnerabilities in dependencies (e.g., Composer packages).</li></ol><h3>Setting Up GitHub for a PHP Project</h3><h4>Step 1: Install Git and Configure It</h4><pre>sudo apt install git  # Linux<br>brew install git      # macOS</pre><pre>git config --global user.name &quot;Your Name&quot;<br>git config --global user.email &quot;[email protected]&quot;</pre><h4>Step 2: Create a Repository on GitHub</h4><ol><li>Visit <a href="https://github.com/"><strong>GitHub</strong></a> and create a new repository.</li><li>Clone it locally:</li></ol><pre>git clone https://github.com/yourusername/repo-name.git cd repo-name</pre><h4>Step 3: Add PHP Code and Push</h4><pre>git add .<br>git commit -m &quot;Initial commit&quot;<br>git push origin main</pre><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Part 2: GitHub Copilot for PHP</h3><h3>What is GitHub Copilot?</h3><p>GitHub Copilot is an <strong>AI-powered assistant</strong> that generates PHP code <strong>based on comments and context</strong>.</p><h3>How to Install GitHub Copilot in VS Code</h3><ol><li><strong>Enable Copilot</strong> via <a href="https://github.com/features/copilot">GitHub Copilot</a>.</li><li><strong>Install Copilot Extension</strong> in VS Code:</li></ol><pre>code --install-extension GitHub.copilot</pre><p><strong>3. Activate Copilot</strong> in the settings.</p><h3>Part 3: GitHub Copilot in Action (PHP Examples)</h3><h3>1. Writing a PHP Function Automatically</h3><p>🚀 <strong>Example: Checking if an Email is Valid</strong> Write a comment in PHP:</p><pre>// Validate an email address</pre><p>GitHub Copilot suggests:</p><pre>function validateEmail($email) {<br>    return filter_var($email, FILTER_VALIDATE_EMAIL) !== false;<br>}</pre><p>🎯 <strong>Saves time</strong> by auto-generating common utility functions.</p><h3>2. Building a Laravel Controller with Copilot</h3><p>🚀 <strong>Example: Generating a Laravel API Controller</strong> Type:</p><pre>// Create a Laravel controller for managing users</pre><p>Copilot suggests:</p><pre>namespace App\Http\Controllers;<br>use Illuminate\Http\Request;<br>use App\Models\User;<br>class UserController extends Controller<br>{<br>    public function index()<br>    {<br>        return User::all();<br>    }<br>    public function store(Request $request)<br>    {<br>        $validated = $request-&gt;validate([<br>            &#39;name&#39; =&gt; &#39;required|string|max:255&#39;,<br>            &#39;email&#39; =&gt; &#39;required|email|unique:users&#39;,<br>            &#39;password&#39; =&gt; &#39;required|min:6&#39;,<br>        ]);<br>        return User::create($validated);<br>    }<br>}</pre><p>🎯 <strong>Automates Laravel CRUD development</strong> with <strong>clean, optimized</strong> code.</p><h3>3. Writing PHPUnit Tests Automatically</h3><p>🚀 <strong>Example: PHPUnit Test for a Laravel Model</strong> Write:</p><pre>// Test the User model creation</pre><p>Copilot suggests:</p><pre>use Tests\TestCase;<br>use App\Models\User;<br><br>class UserTest extends TestCase<br>{<br>    public function test_user_creation()<br>    {<br>        $user = User::factory()-&gt;create();<br>        $this-&gt;assertDatabaseHas(&#39;users&#39;, [&#39;email&#39; =&gt; $user-&gt;email]);<br>    }<br>}</pre><p>🎯 <strong>Reduces time spent writing tests</strong> while ensuring coverage.</p><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Part 4: Best Practices for PHP Developers Using GitHub &amp; Copilot</h3><h3>✅ Best GitHub Practices</h3><p><strong>Follow Git Commit Message Conventions</strong></p><ul><li>✅ feat: Added user authentication</li><li>✅ fix: Fixed database connection issue</li></ul><p><strong>Use Feature Branches</strong></p><ul><li>main → Production</li><li>dev → Development</li><li>feature-* → Feature-specific branches</li></ul><p><strong>Enable GitHub Actions for PHP</strong></p><ul><li>Run <strong>automated tests</strong> on every push.</li></ul><h3>✅ Best GitHub Copilot Practices</h3><p><strong>Provide Clear Comments:</strong></p><ul><li>Writing // Function to send an email in Laravel improves Copilot’s accuracy.</li></ul><p><strong>Use Copilot for Repetitive Code:</strong></p><ul><li>Let Copilot handle <strong>boilerplate</strong>, while you focus on logic.</li></ul><p><strong>Review AI-Suggested Code Before Using It!</strong></p><ul><li><strong>Security &amp; performance</strong> checks are crucial.</li></ul><p>🌐 <a href="http://www.stammp.com/">www.stammp.com</a></p><p><a href="https://www.stammp.com/">Stammp Technologies Pvt Ltd</a> (<a href="https://stammp.com/">https://stammp.com/</a>)<br><a href="https://www.linkedin.com/company/stammp">https://www.linkedin.com/company/stammp</a><br><a href="https://www.linkedin.com/in/jayprakashjangir/">https://www.linkedin.com/in/jayprakashjangir/</a></p><h3>Conclusion</h3><p>GitHub and GitHub Copilot are <strong>game-changers for PHP development</strong>. Whether you’re managing a Laravel project or writing complex business logic, these tools can <strong>boost productivity and reduce development time</strong>.</p><p>🚀 <strong>Start using GitHub &amp; GitHub Copilot today to level up your PHP development!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebe10ce68255" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>