<?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 Nicolas Maitre on Medium]]></title>
        <description><![CDATA[Stories by Nicolas Maitre on Medium]]></description>
        <link>https://medium.com/@maitrenicolas?source=rss-4211439e6d90------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZK138EdMTTND1wCW_DDCbQ.jpeg</url>
            <title>Stories by Nicolas Maitre on Medium</title>
            <link>https://medium.com/@maitrenicolas?source=rss-4211439e6d90------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:07:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maitrenicolas/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[Deploy Your Angular SSR App on Dokploy with Railpack (No Dockerfile Needed)]]></title>
            <link>https://medium.com/@maitrenicolas/deploy-your-angular-ssr-app-on-dokploy-with-railpack-no-dockerfile-needed-696cbf187fb9?source=rss-4211439e6d90------2</link>
            <guid isPermaLink="false">https://medium.com/p/696cbf187fb9</guid>
            <category><![CDATA[dokploy]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[self-hosting]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Nicolas Maitre]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 21:45:51 GMT</pubDate>
            <atom:updated>2025-12-22T21:45:51.328Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve ever tried deploying an Angular SSR application, you know it can be a bit tricky. Unlike classic SPAs that just need a static file server, SSR apps require a Node.js server running your application.</p><p>In this guide, I’ll show you how to deploy an Angular SSR app on <strong>Dokploy</strong> using <strong>Railpack, </strong>no Dockerfile required.</p><h3>What is Dokploy?</h3><p>Dokploy is a self-hosted Platform-as-a-Service (PaaS) alternative to Vercel, Netlify, or Railway. It lets you deploy applications on your own infrastructure with a clean UI and automated deployments.</p><p>One of its best features is <strong>Railpack</strong>, a buildpack system that automatically detects your project type and builds it accordingly.</p><h3>The Challenge with Angular SSR</h3><p>Angular SSR generates a Node.js server that needs to run on your hosting platform. While Railpack works great out of the box for Next.js, Nuxt, or Remix, Angular SSR requires a small configuration tweak.</p><p>The issue? Railpack looks for a start script in your package.json to know how to run your app after building it, but the one in an angular project is usually ng serve and we don’t want that.js</p><h3>The Solution</h3><p>Here’s how to make your Angular SSR app Railpack-compatible in two simple steps.</p><h3>Step 1: Update your package.json scripts</h3><p>Open your package.json and update the start script that points to your SSR server:</p><pre>{<br>  &quot;scripts&quot;: {<br>    &quot;build&quot;: &quot;ng build&quot;,<br>    &quot;start&quot;: &quot;node dist/&lt;your-project-name&gt;/server/server.mjs&quot;<br>  }<br>}</pre><p>Replace &lt;your-project-name&gt; with the actual name of your Angular project. You can find this in your angular.json file or by checking the dist/ folder after running ng build.</p><h3>Step 2: Configure the port</h3><p>Railpack typically expects your app to listen on port 3000, or on the port specified by the PORT environment variable.</p><p>In your server.ts file (usually at src/server.ts), make sure the port is configurable:</p><pre>const port = process.env[&#39;PORT&#39;] || 3000;</pre><p>That’s it for the code changes!</p><h3>Deploying on Dokploy</h3><p><strong>Create a new application</strong> in Dokploy</p><p><strong>Connect your Git repository</strong> (GitHub, GitLab, etc.)</p><p><strong>Select Railpack</strong> as the build method</p><p><strong>Add environment variables</strong> if needed:</p><ul><li>PORT=3000 (usually auto-detected)</li><li>Any API URLs or configuration your app needs</li></ul><p><strong>Deploy!</strong></p><p>Railpack will automatically:</p><ul><li>Detect your Node.js project</li><li>Run npm ci</li><li>Execute npm run build</li><li>Start your app with npm run start</li></ul><h3>Why Not Use a Dockerfile?</h3><p>You absolutely can use a Dockerfile, for complex setups it gives you more control. But Railpack offers some nice advantages:</p><ul><li><strong>Zero configuration</strong> for most projects</li><li><strong>Automatic caching</strong> of dependencies</li><li><strong>Faster iteration</strong> when you just want to ship</li></ul><h3>Conclusion</h3><p>Deploying Angular SSR on Dokploy with Railpack is straightforward once you know the trick: just add a start script and make your port configurable.</p><p>No Dockerfile, no complex CI/CD pipelines — just push your code and let Railpack handle the rest.</p><p><em>Have questions or found a better approach? Drop a comment below!</em></p><p><strong>Tags:</strong> Angular, SSR, Dokploy, Railpack, DevOps, Deployment, Self-Hosted</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=696cbf187fb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CSS Game-Changer: Ditch rgba() for color-mix()]]></title>
            <link>https://medium.com/@maitrenicolas/css-game-changer-ditch-rgba-for-color-mix-555b2f758830?source=rss-4211439e6d90------2</link>
            <guid isPermaLink="false">https://medium.com/p/555b2f758830</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[scss]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Nicolas Maitre]]></dc:creator>
            <pubDate>Mon, 27 May 2024 05:32:21 GMT</pubDate>
            <atom:updated>2024-05-27T05:32:21.990Z</atom:updated>
            <content:encoded><![CDATA[<p>So, you’ve made the leap from Sass variables to the shiny world of CSS variables, only to stumble when using the good ol’ rgba() function? Don&#39;t worry, you&#39;re not alone!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuqX_rs9MrlQ83buTIEgUg.jpeg" /></figure><p>If you’re anything like me, you once relied on Sass variables like this:</p><pre>$primary : #00ccff;</pre><p>And now, you’ve embraced the power of CSS variables:</p><pre>:root {<br>  --primary : #00ccff;<br>}</pre><p>The problem? Trying to translate your Sass-powered rgba() magic:</p><pre>background-color : rgba($color: $primary, $alpha: 0.6);</pre><p>Into something that works with CSS variables:</p><pre>/* Nope, this won&#39;t work! */ <br>background-color : rgba($color: var(--primary), $alpha: 0.6);</pre><p>Frustrating, right? Well, get ready to ditch that frustration because color-mix() is here to save the day!</p><h4>But wait… is color-mix() supported?</h4><p>The short answer is a resounding YES! Modern browsers (with a few exceptions for older versions) have got you covered. Check out the support details on <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/color_value/color-mix">MDN web docs</a> and <a href="https://caniuse.com/?search=color-mix">caniuse.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zGElS5N3QMolVLgYUO2eQA.png" /><figcaption>MDN web docs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xG1jgEphALmqWJz0Caxi5g.png" /><figcaption>caniuse.com</figcaption></figure><h4>Time to Mix Things Up!</h4><p>Let’s see how to use color-mix() to replicate the transparency effects you were used to with rgba().</p><p>Say goodbye to:</p><pre>background-color: rgba($color: $primary, $alpha: 0.6);</pre><p>And say hello to :</p><pre>background-color: color-mix(in srgb, var(--primary) 60%, transparent);</pre><p>Here’s the breakdown:</p><ul><li><strong>in srgb:</strong> We&#39;re specifying the color space (sRGB is the standard for web).</li><li><strong>var(--primary):</strong> Your trusty CSS variable is the first color we&#39;re mixing.</li><li><strong>60%:</strong> This sets the percentage of your --primary color in the mix (equivalent to an alpha of 0.6).</li><li><strong>transparent:</strong> The second color we&#39;re mixing in (this is what creates the transparency effect).</li></ul><h4>Why color-mix() Rocks</h4><ul><li><strong>Intuitive:</strong> The percentage-based approach makes it easier to visualize the transparency level.</li><li><strong>Flexible:</strong> You can mix any two colors, not just a color with transparency.</li><li><strong>Powerful:</strong> Open the door to creative color blending possibilities beyond simple transparency.</li></ul><h4>Give it a try !</h4><p>Go ahead and experiment with color-mix(). Adjust those percentages, try out different color combinations, and see what amazing results you can create. Happy styling!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=555b2f758830" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>