<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: nitishbali24</title>
    <description>The latest articles on DEV Community by nitishbali24 (@nitish_bali).</description>
    <link>https://dev.to/nitish_bali</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1142835%2F5376e9e5-6f0c-4c97-ab96-3846b5ac3225.png</url>
      <title>DEV Community: nitishbali24</title>
      <link>https://dev.to/nitish_bali</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nitish_bali"/>
    <language>en</language>
    <item>
      <title>Gatsby SSR docker image size is too large</title>
      <dc:creator>nitishbali24</dc:creator>
      <pubDate>Mon, 21 Aug 2023 08:56:14 +0000</pubDate>
      <link>https://dev.to/nitish_bali/gatsby-ssr-deployment-8jp</link>
      <guid>https://dev.to/nitish_bali/gatsby-ssr-deployment-8jp</guid>
      <description>&lt;p&gt;Hi all, I am facing issue while deploying Gatsby SSR code to GCP using docker as an image container.&lt;br&gt;
The image size is coming more than 3.0GB which is heavy for handling load and autoscaling in GCP.&lt;/p&gt;

&lt;p&gt;Right now using single stage build in Docker&lt;br&gt;
Where building the application first using Gatsby build and then serving it on a port using Gatsby serve command.&lt;/p&gt;

&lt;p&gt;Because node modules are also part of the image so size is very high.&lt;/p&gt;

&lt;p&gt;Tried nginx multi-stage build as well but that didn't work because it is not able to find the index.html in the root of the build folder.&lt;/p&gt;

&lt;p&gt;This is another issue index.html is not getting generated after running Gatsby build in my Gatsby SSR application&lt;/p&gt;

&lt;p&gt;Please help me reduce the image size at most priority.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
