<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Santosh Khanal</title><description>Full-stack Laravel. Shipped to production.</description><link>https://khanal.dev/</link><language>en</language><item><title>Laravel and ecosystem</title><link>https://khanal.dev/posts/laravel-and-all/</link><guid isPermaLink="true">https://khanal.dev/posts/laravel-and-all/</guid><description>A first note on why this blog exists and what I&apos;ll be writing about.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;This is the first time I am writing a blog.&lt;/p&gt;
&lt;p&gt;After 8+ years building on Laravel — full apps, from scratch to production — I keep accumulating small lessons that never seem to fit anywhere: a testing trick with Pest, a deployment gotcha on Vapor or a VPS, the reason some Laravel internal behaves the way it does. This is where I&apos;ll write them down.&lt;/p&gt;
&lt;p&gt;Expect posts aimed at fellow Laravel and PHP developers:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Framework internals&lt;/strong&gt; — how things actually work under the hood&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tips &amp;amp; Tricks&lt;/strong&gt; — All about Laravel ecosystem&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Testing&lt;/strong&gt; — Pest and PHPUnit in real projects&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Frontend&lt;/strong&gt; — Vuejs / Inertiajs alongside Laravel&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shipping&lt;/strong&gt; — deploying and running apps without surprises&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More soon.&lt;/p&gt;
</content:encoded></item></channel></rss>