<?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 MC Naveen on Medium]]></title>
        <description><![CDATA[Stories by MC Naveen on Medium]]></description>
        <link>https://medium.com/@mcnaveen?source=rss-2c7c8309d175------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kwzC4jcZ2nUKkMbumipXLw.png</url>
            <title>Stories by MC Naveen on Medium</title>
            <link>https://medium.com/@mcnaveen?source=rss-2c7c8309d175------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:16:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mcnaveen/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[I needed a WishKit-style feedback board on Android.]]></title>
            <link>https://medium.com/@mcnaveen/i-needed-a-wishkit-style-feedback-board-on-android-6128939e11b3?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/6128939e11b3</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 12:05:53 GMT</pubDate>
            <atom:updated>2026-09-20T12:05:53.520Z</atom:updated>
            <content:encoded><![CDATA[<p>WishKit is a nice Swift package. One configure call, a list of wishes, users vote inside the iOS app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dvytRyefOFo44bZbvJiPJg.jpeg" /></figure><p>I wanted that on Android.</p><p>There is no Android package. No Maven coordinate. No React Native package. No Flutter package. The site is honest about it if you read the platform list. The pricing page is still $0 / $15 / $39 for Apple platforms plus a web widget.</p><p>So you get three options.</p><h3>1. Keep WishKit on iOS and invent Android</h3><p>Second dashboard. Second vote count. Standup argument about which number is real.</p><p>I have done this with other tools. It lasts about two releases.</p><h3>2. Stuff the web board in a WebView</h3><pre>webView.loadUrl(&quot;https://your-board.example&quot;)</pre><p>It looks like an SDK in a demo. It is a website.</p><p>Theme will not match Settings. Airplane mode is a blank screen. Login often wants a popup the WebView cannot finish. Canny’s official mobile recipe also wants SSO before the screen renders. That is not “add a dependency.” That is “stand up JWT minting.”</p><h3>3. Use a package that actually has Android</h3><p>I work on <a href="https://feedbackjar.com/">FeedbackJar</a>. Same widget ID on Kotlin, Swift, React Native, and Flutter. Users vote in the app. The report carries OS, model, screen, app version. An agent can read that over MCP and mark the post Done so voters get a mail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2agVIZlZwH3r0z-eiPYPQ@2x.jpeg" /><figcaption>Feedbackjar</figcaption></figure><h3>The Android snippet I actually ship</h3><pre>// build.gradle.kts<br>implementation(&quot;com.feedbackjar:sdk:1.4.0&quot;)</pre><pre>class MyApp : Application() {<br>    override fun onCreate() {<br>        super.onCreate()<br>        FeedbackJar.init(this, &quot;your-widget-id&quot;)<br>    }<br>}</pre><pre>startActivity(FeedbackJarActivity.intent(this))</pre><p>In Settings row, label it as “Feature requests.” Not “Ideas.” Not shake. Shake is for crashes.</p><p>Compose if the app already uses Compose:</p><pre>FeedbackJarBoard(accentColor = Color(0xFFE5484D))</pre><p>Same widget ID in the Swift package if you also have an iOS app. One list. That was the whole point.</p><p>Full walkthrough with the WebView vs native table:<br><a href="https://feedbackjar.com/blog/wishkit-alternative-android-2026">https://feedbackjar.com/blog/wishkit-alternative-android-2026</a></p><h3>What I am not saying</h3><p>WishKit is fine if you will not leave the App Store. Their Free plan is real. Five visible requests, one project, no card.</p><p>The week Android is on the calendar, price the second tool or price a migration. Do not price “$15 vs $9” as if both rows include Android.</p><p>App Review does not care about a Settings-row board. Users bouncing on a login wall inside a WebView do.</p><h3>If you are still on email and Play Console reviews</h3><p>That is not a roadmap. You cannot merge “add dark mode” from twelve people. You cannot tell them you shipped.</p><p>Put the board in Settings. Seed two posts so the first user does not see an empty list. Then ignore the rest of the marketing pages.</p><p>7 Days, no card, on feedbackjar.com. Other tools exist. The package name in Gradle is the part that matters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6128939e11b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Use One App to Organize All My Health Data (Without Being a Tech Expert)]]></title>
            <link>https://medium.com/@mcnaveen/how-i-use-one-app-to-organize-all-my-health-data-without-being-a-tech-expert-67c2232668e3?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/67c2232668e3</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[webhooks]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Fri, 24 Apr 2026 15:43:05 GMT</pubDate>
            <atom:updated>2026-04-24T15:44:46.237Z</atom:updated>
            <content:encoded><![CDATA[<p>I own a smartwatch and a fitness tracker. I use Google Fit, Samsung Health, and Strava. Every single day, these apps are collecting data about my body.</p><p>The problem? All that data lives in separate apps. There is no single place to look at it together. No way to ask: “Am I actually getting healthier?” without opening four different apps and guessing.</p><p>So I built something to fix that. And it has genuinely changed how I understand my own health.</p><h3>What the Problem Actually Feels Like</h3><p>Imagine you go to your doctor and they ask: “How has your heart rate been over the last three months?”</p><p>You pull out your phone. Your heart rate is in Samsung Health. Your sleep is in Oura. Your workouts are in Strava. You can’t easily compare any of it. You end up saying “I think it was okay” because that is honestly all you know.</p><p>That is what I was doing. Generating data every single day and learning almost nothing from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WtIwFhbHPxsWH3Ke.png" /><figcaption>Health Connect Webhook</figcaption></figure><h3>The App I Built: HC Webhook</h3><p>I made an Android app called <a href="https://hcwebhook.com/?ref=medium"><strong>HC Webhook</strong></a>. Here is what it does in plain terms:</p><p>It collects all my health data from every app on my phone and sends it to one place I control, twice a day, automatically.</p><blockquote>It’s available in Google Playstore → <a href="https://play.google.com/store/apps/details?id=com.hcwebhook.app">Download Here ⬇️</a></blockquote><p>That is it. No manual exports. No remembering to check things. Just my health data flowing into one organized place every morning and evening.</p><p>The app reads from something called Google Health Connect, which is Android’s built-in hub for health data. Every health app on your phone (Samsung Health, Fitbit, Strava, Oura, and many more) can share data with Health Connect. <a href="https://play.google.com/store/apps/details?id=com.hcwebhook.app"><strong>HC Webhook</strong></a> then picks all of that up and sends it wherever I tell it to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*QM7_4ZDBJakE8Q8QOPROsA@2x.jpeg" /></figure><h4>Use Case 1: Understanding My Sleep</h4><p><strong>The old way: </strong>I open Samsung Health, see a sleep score, shrug, close the app.</p><p><strong>The new way:</strong> I can now see my sleep data next to my heart rate data, side by side, going back months.</p><p><strong>What I discovered:</strong> when I sleep fewer than 6 hours, my resting heart rate is noticeably higher two to three days later. Not the next morning. Two to three days later.</p><p>I would never have figured that out from Samsung Health alone. It only shows you one metric at a time. It does not show you how sleep connects to your heart health a few days down the line. Having all my data in one place made this connection visible.</p><h4>Use Case 2: Actually Seeing Fitness Progress</h4><p>I started doing more cardio in January. Samsung Health shows me individual workout summaries, but it does not show me a clear trend over months.</p><p>Because all my data now lives in one place, I can see that my VO2 Max (a measure of cardio fitness) has gone up 4 points since January. I can see exactly when it started improving. That kind of long-term visibility keeps me motivated in a way that individual workout summaries never did.</p><h4>Use Case 3: A Weekly Health Summary in My Inbox</h4><p>Every Sunday morning, I get an email that looks like this:</p><blockquote>Your week in health:</blockquote><blockquote>&gt; Steps this week: 62,400 (avg 8,914/day)</blockquote><blockquote>&gt; Sleep average: 6.8 hours</blockquote><blockquote>&gt; Resting heart rate: 58 bpm (down from 61 last week)</blockquote><blockquote>&gt; Workouts: 4</blockquote><p>I did not write this email. My setup sends it to me automatically. It takes about one minute to read and gives me a better weekly picture of my health than I ever had before.</p><blockquote>It’s available in Google Playstore → <a href="https://play.google.com/store/apps/details?id=com.hcwebhook.app">Download Here ⬇️</a></blockquote><h4>How It All Fits Together (Simply Explained)</h4><p><strong>Step 1.</strong> <a href="https://play.google.com/store/apps/details?id=com.hcwebhook.app">HC Webhook</a> runs quietly on my Android phone. Twice a day, it collects new health data from all my apps.</p><p><strong>Step 2.</strong> It sends that data to a tool called n8n. Think of n8n as a personal assistant that receives the data and decides what to do with it (store it, send an alert, email me a summary).</p><p><strong>Step 3.</strong> n8n saves everything into a database (Supabase) called Life. Think of it as a very organized spreadsheet that lives in the cloud and can answer questions instantly.</p><p><strong>Step 4.</strong> I can look at my health records any time, ask questions like “show me my average steps per week for the last three months,” and get a real answer.</p><p>The whole thing runs automatically. I do not touch it day to day.</p><h4>What Makes This Different From Just Using a Health App</h4><p>Samsung Health is great at collecting data. But it shows each metric in its own section. Steps here, sleep there, heart rate somewhere else. It does not connect the dots for you.</p><p>This setup connects everything. It treats your health data the way a good doctor would want to: as a complete picture of one person over time, not separate fragments across separate apps.</p><p>It also means you own your data. <a href="https://play.google.com/store/apps/details?id=com.hcwebhook.app">HC Webhook</a> does not send your health information to any company’s servers. It only goes where you tell it to go. Your data stays yours.</p><h4>What I Plan to Do Next</h4><p>I am building a simple visual dashboard so I can see all my key health numbers on one screen, like a personal health report card. Steps, sleep, heart rate, and blood pressure all on one page.</p><p>I am also experimenting with feeding my weekly health data to an AI and asking it: “What patterns should I pay attention to?” The data is already there. Connecting an AI to ask questions about it is the next step.</p><h4>Should You Try This?</h4><p>If you use any Android health or fitness app and you want to actually understand your health trends over time rather than just collecting data that sits unused, yes.</p><p>The technical setup (n8n and Supabase) takes a couple of hours the first time. But once it is running, it runs on its own. You just start learning things about your health that you could not see before.</p><p>That, to me, is worth every minute of setup.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67c2232668e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Nginx Reverse Proxying]]></title>
            <link>https://medium.com/timeless/mastering-nginx-reverse-proxying-f4f89017f68c?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4f89017f68c</guid>
            <category><![CDATA[nginx-proxy]]></category>
            <category><![CDATA[nginx]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Tue, 31 Dec 2024 12:45:56 GMT</pubDate>
            <atom:updated>2024-12-31T12:46:30.060Z</atom:updated>
            <content:encoded><![CDATA[<p>Nginx is an amazing piece of software that can be used solely as a web server or reverse proxy. This article covers basic to advanced levels of reverse proxying with load-balancing techniques.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*A1EIytQPiSU8SckOE2BWIA.png" /></figure><p><strong>Installing Nginx</strong></p><p>If you’re using Ubuntu as your server operating system, you can install Nginx using the simple command. (This command varies if you’re using a different operating system)</p><pre>sudo apt install nginx</pre><p>Most web servers need port 80 and 443 to be open. Port 80 handles the incoming and outgoing HTTP traffic whereas 443 handles the HTTPS protocol.</p><p>If you’re using any firewall like UFW, make sure you have set the ports open.</p><p>Now if you visit your server IP, You’ll be greeted with this page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmFDZjKQmWAmRwpcEPPuUw.png" /></figure><p>It means the nginx is successfully installed and working properly.</p><p>When the nginx is installed, It also creates a new directory called html inside /var/www of the system root directory.</p><p><strong>Important directory of nginx</strong></p><p>Once the nginx is installed, its configuration can be found in the /etc/nginx directory.</p><p>Configuration for every website we host on the server will be created in this location.</p><p>A simple configuration for a website will look like this</p><pre><br>server {<br>    location / {<br>        root /var/www/html;<br>    }<br>}</pre><p>This is called server block.</p><p>location / — Defines what happens when the root IP or domain is visited</p><p>root — Points to the directory where the request should responded with</p><p>For multiple websites, we can create multiple configuration files in the /etc/nginx/sites-available directory</p><p>After creating a configuration in /etc/nginx/sites-available directory, the configuration should be symlinked to /etc/nginx/sites-enabled directory to expose to the internet.</p><p>Nginx comes with a useful option to test and validate the present configuration.</p><p>You have to run ngnix -t to validate the current configuration.</p><h3><strong>Using Nginx as a Load Balancer</strong></h3><p>Nginx offers a feature to use as a Load Balancer. Let’s say you’re running multiple instances of the application and want to route the traffic automatically and switch between instances, You can easily do it with Nginx.</p><p>There are 5 load-balancing methods offered by nginx.</p><ol><li>Round Robin</li><li>Least Connection</li><li>IP Hash</li><li>Generic Hash</li><li>Least Time (Only available in Paid Version)</li></ol><p>Requests are routed evenly across the available instances</p><p>Requests are routed evenly across the available instances based on the available server load</p><pre>upstream backend {<br>   server localhost:3000;<br>   server localhost:3001;<br>}<br><br>server {<br>    location / {<br>      proxy_pass http://backend;<br>     }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*vaR0qkrtdEJ8lEdxbHKKUw@2x.png" /></figure><p><strong>Least Connection</strong></p><p>Incoming requests will be routed to the instance that has a less active connection</p><pre>upstream backend {<br>   least_conn;<br>   server localhost:3000;<br>   server localhost:3001;<br>}<br><br>server {<br>    location / {<br>      proxy_pass http://backend;<br>     }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*YH_RQW7d0nng7Q8yVgj_dA@2x.png" /></figure><p><strong>IP Hash</strong></p><p>This will route the request to the last connected instance based on the first three pairs of calculated hashed IP</p><pre>upstream backend {<br>   ip_hash;<br>   server localhost:3000;<br>   server localhost:3001;<br>}<br><br>server {<br>    location / {<br>      proxy_pass http://backend;<br>     }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*VQKhmwYV1tPtuDim1_c50Q@2x.png" /></figure><p><strong>Generic Hash</strong></p><p>Incoming requests will be routed to the user-defined hash key</p><pre>upstream backend {<br>   hash $request_uri consistent;<br>   server localhost:3000;<br>   server localhost:3001;<br>}<br><br>server {<br>    location / {<br>      proxy_pass http://backend;<br>     }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*5y75iiZ_Qbomo6PaoEpkeQ@2x.png" /></figure><p>Nginx is managed using system services in a Debian-based distro. We can use systemctl to manage the services.</p><p>To start the Nginx service</p><pre>sudo service nginx start</pre><p>To stop the Nginx service</p><pre>sudo service nginx stop</pre><p>To restart the Nginx service</p><pre>sudo service nginx restart</pre><p>These are the required things to set up and run Nginx as a reverse proxy.</p><blockquote><em>This article is written by </em><a href="https://github.com/mcnaveen"><em>MC.Naveen</em></a><em> for </em><a href="https://timeless.co/"><em>Timeless</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4f89017f68c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/mastering-nginx-reverse-proxying-f4f89017f68c">Mastering Nginx Reverse Proxying</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Scraping with different techniques (Puppeteer) — Part 2]]></title>
            <link>https://medium.com/timeless/web-scraping-with-different-techniques-puppeteer-part-2-eb2e3c4b8011?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb2e3c4b8011</guid>
            <category><![CDATA[web-scraping]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[puppeteer]]></category>
            <category><![CDATA[browser-automation]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Thu, 30 Mar 2023 12:56:02 GMT</pubDate>
            <atom:updated>2023-03-30T12:56:02.168Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Scraping with different techniques (Puppeteer) — Part 2</h3><p>Websites that use React or similar library has a technique that hydrates the DOM after the Initial Page load. This means every part of the DOM content or element is visible one by one. So on this Initial load, there will be only a white screen. Scrapping this type of webpage is not possible with Cheero and Axios like we did in Part 1 of this series. [Link]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*Pza3GUFm14j8_CCvvsM4Fw.png" /></figure><blockquote>This article is solely for educational purposes only</blockquote><p>In this article, We are going to use Puppeteer to do the scraping for us. Puppeteer is a popular tool from Google for performing automation testing. Good thing, It supports both headless and headful browsers.</p><p>Since Puppeteer is a web browser, We get plenty of options to control how it should behave.</p><p>We will be using Expressjs and Puppeteer.</p><ul><li>Express js is for creating an API endpoint.</li><li>Puppeteer will be our web browser for scraping content from the webpage.</li></ul><p>So, the flow will be something like this.</p><figure><img alt="Express + Puppeteer flow" src="https://cdn-images-1.medium.com/max/932/1*Wq9RPc8zIf3P1hxB5Ey6Tg.png" /><figcaption>Express + Puppeteer flow</figcaption></figure><p>So, whenever the Express server receives a request. It spins up a new Puppeteer instance and opens a webpage.</p><p>To get started, initialize a new project in an empty directory. I’ll be using Yarn as my package manager.</p><pre>yarn init -y</pre><p>Now, add the required dependencies:</p><pre>yarn add express puppeteer</pre><p>This will take a while based on your internet speed. Because the puppeteer downloads an executable browser bin.</p><p>Once installed, Create a new index.js file and start importing the installed libraries</p><pre>import puppeteer from &quot;puppeteer&quot;;<br>import express from &quot;express&quot;;<br>const app = express();</pre><p>Now, the Express needs an endpoint, also PORT to listen to the incoming connections.</p><pre>app.get(&quot;/&quot;, (req, res) =&gt; {<br>  // Response goes here<br>}<br><br>app.listen(3000, () =&gt; {<br>  console.log(&quot;Example app listening on port 3000!&quot;);<br>});</pre><p>Since the URL is needed, We can get from the URL via Query params.</p><pre>  const url = req.query.url;</pre><p>Now, inside the Endpoint block, paste the below code.</p><pre>puppeteer<br>  .launch({<br>    headless: true,<br>  })<br>  .then(async (browser) =&gt; {<br>    const page = await browser.newPage();<br>    await page.goto(url, { waitUntil: &#39;networkidle2&#39; });<br>    const featuredImage = await page.evaluate(() =&gt; {<br>      return document.querySelector(<br>        &quot;#mp-tfp &gt; table &gt; tbody &gt; tr:nth-child(1) &gt; td &gt; a &gt; img&quot;<br>      ).src;<br>    });<br>    const featuredDesc = await page.evaluate(() =&gt; {<br>      return document.querySelector(<br>        &quot;#mp-tfp &gt; table &gt; tbody &gt; tr:nth-child(2) &gt; td &gt; p:nth-child(1)&quot;<br>      ).innerText;<br>    });<br>    res.send({ featuredImage, featuredDesc });<br>  });</pre><p>Here is the breakdown of the above code.</p><ul><li>Puppeteer is launched as a headless browser</li><li><strong>await browser.newPage() — </strong>creates a new page in the launched browser</li><li><strong>page.goto(url)</strong> — This is open the URL you have passed in the request. In our case, It’s Wikipedia URL.</li><li><strong>await page.evaluate</strong> — This evaluates the element in the DOM and using the querySelector we fetch the element’s content.</li><li><strong>waitUntil: ‘networkidle2’ </strong>— This will make sure the Page is fully loaded, and the network becomes idle.</li></ul><p>Here is the complete code with Error handling.</p><pre>import express from &quot;express&quot;;<br>const app = express();<br><br>import puppeteer from &quot;puppeteer&quot;;<br><br>app.get(&quot;/&quot;, (req, res) =&gt; {<br>  const url = req.query.url;<br>  if (!url) {<br>    res.send(&quot;Please provide a url&quot;);<br>    return;<br>  } else {<br>    puppeteer<br>      .launch({<br>        headless: true,<br>      })<br>      .then(async (browser) =&gt; {<br>        const page = await browser.newPage();<br>        await page.goto(url, { waitUntil: &#39;networkidle2&#39; });<br>        const featuredImage = await page.evaluate(() =&gt; {<br>          return document.querySelector(<br>            &quot;#mp-tfp &gt; table &gt; tbody &gt; tr:nth-child(1) &gt; td &gt; a &gt; img&quot;<br>          ).src;<br>        });<br>        const featuredDesc = await page.evaluate(() =&gt; {<br>          return document.querySelector(<br>            &quot;#mp-tfp &gt; table &gt; tbody &gt; tr:nth-child(2) &gt; td &gt; p:nth-child(1)&quot;<br>          ).innerText;<br>        });<br>        res.send({ featuredImage, featuredDesc });<br>      });<br>  }<br>});<br><br>app.listen(3000, () =&gt; {<br>  console.log(&quot;Example app listening on port 3000!&quot;);<br>});</pre><p>Since we are using Wikipedia in this example, I have hard-coded the selectors. But if you’re using a different webpage. The Selector will change.</p><p>You can run the code using the command.</p><pre>node index.js</pre><p>Then, Open the Browser with the URL.</p><pre>http://localhost:3010/?url=https://en.wikipedia.org/wiki/Main_Page</pre><p>You’ll get a Response like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E15sWDbNCbYoMeX7x-AQTw.png" /></figure><p>You can start using it as your API to build your web project. This method works well for dynamic websites or client-side js apps.</p><p>I hope you find this article useful. Feel free to comment with your thoughts and let me know if you face any difficulties.</p><blockquote><em>This article is written by </em><a href="https://github.com/mcnaveen"><strong><em>MC.Naveen</em></strong></a><em> for </em><a href="https://timeless.co/"><strong><em>Timeless</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb2e3c4b8011" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/web-scraping-with-different-techniques-puppeteer-part-2-eb2e3c4b8011">Web Scraping with different techniques (Puppeteer) — Part 2</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Scraping with different techniques — Part 1]]></title>
            <link>https://medium.com/timeless/web-scraping-with-different-techniques-part-1-4a34db8e2bbb?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a34db8e2bbb</guid>
            <category><![CDATA[web-scraping]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[scraping]]></category>
            <category><![CDATA[cheeriojs]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Thu, 30 Mar 2023 12:53:56 GMT</pubDate>
            <atom:updated>2023-03-30T12:53:56.328Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Scraping with different techniques (Cheerio) -Part 1</h3><p>Web Scraping is a common practice used by crawlers, and robots to get information on websites. In this blog post, we will see how to do a similar scrapper to obtain information from the website. This blog post is divided into Two Parts and this explains how to scrape from the static website.</p><blockquote>This article is solely for educational purposes only</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*p0LmMqxqKjvN0yCZxWU5NA.png" /></figure><p>Web Scraping can be done with different programming languages and techniques. We will be using Node.js and a few other libraries.</p><p>Make sure you have Nodejs installed on your system.</p><p>Before moving on to the coding part, I hope you know about how websites are built these days and the basic concepts of building them.</p><p>For example. There are selectors which help to pick the single element in the webpage. It can be an ID, classname, etc.</p><p>We are using Axios, Cheerio, and Expressjs.</p><ul><li>Axios is a promise-based HTTP client which allows us to make requests to the URL.</li><li>Cheerio is HTML Parser that helps to extract the text or other attributes from the elements</li><li>Express is a web server that helps to turn the scraped data into an API.</li></ul><p>We are going to scrape Wikipedia&#39;s Today featured picture and turn it into an API.</p><p>If you look at the source of the Main page. We can see the whole section is wrapped with a div and its id is “mp-tfp”. So, it’s our root selector.</p><p>The image has a src and the body content is inside the root element with the p tag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9tAsbXJafAXb00FR7V5P8A.png" /></figure><p>In the Chrome Dev Tools, we can right-click on the Image tag, and under copy, select the Copy Selector option.</p><p>Which will give something like this, “<strong>#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(1) &gt; a &gt; img</strong>”. We also need the text inside the p tag. So right-click on it and do the same, and we will get this “<strong>#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(2) &gt; p:nth-child(1)</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*2Qj3_4esG-57C3_8xsIKrg.png" /></figure><p>Keep both selectors safe, we require this later in the article.</p><p>In an empty directory, runs the below command to initialize the project.</p><p>I’ll be using Yarn as a package manager. You can use the npm or pnpm.</p><pre>yarn init -y</pre><p>This will create a package.json file. Now installed the below dependencies.</p><pre>yarn add axios cheerio express</pre><p>Once the installation is complete. Create an index.js file.</p><p>Now we can start importing the libraries we have just installed inside the index.js</p><pre>const axios = require(&quot;axios&quot;);<br>const cheerio = require(&quot;cheerio&quot;);<br>const express = require(&quot;express&quot;);<br>const app = express();</pre><p>Since we are going to create an API out of it. We need to create a GET endpoint. So paste the below lines inside the file.</p><pre>app.get(&quot;/&quot;, (req, res) =&gt; {<br>   res.send(&quot;Hello World&quot;);<br>});<br><br>app.listen(3000, () =&gt; {<br>  console.log(&quot;Server is running on port 3000&quot;);<br>});</pre><p>You can start the node server by typing the below command.</p><pre>node index.js</pre><p>You will see a console log message “Server is running on port 3000”</p><p>If you open <a href="http://localhost:3000/">http://localhost:3000</a> in your browser. You will get a message, “Hello” world.</p><p>Just replace the <strong>res.send</strong> line with Axios request and Wikipedia URL. If you request a URL with Axios. You will get an HTML source as a response. Store the response in a variable called HTML.</p><pre>  axios<br>    .get(&quot;https://en.wikipedia.org/wiki/Main_Page&quot;)<br>    .then((response) =&gt; {<br>      const html = response.data;<br>    })<br>    .catch((error) =&gt; {<br>      console.log(error);<br>    });</pre><p>Load the HTML variable into Cheerio for parsing the data.</p><pre>const $ = cheerio.load(html);<br>const featuredImage = $(&quot;#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(1) &gt; a &gt; img&quot;).attr(&quot;src&quot;);<br>const featuredDesc = $(&quot;#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(2) &gt; p:nth-child(1)&quot;).text().trim();</pre><p>Create two variables “<strong>featuredImage</strong>” and “<strong>featuredDesc” </strong>and pass the selector we got from the previous step. Now send it as an API response.</p><pre>res.send({ featuredImage, featuredDesc });</pre><p>The final code will look something like this.</p><pre>const axios = require(&quot;axios&quot;);<br>const cheerio = require(&quot;cheerio&quot;);<br>const express = require(&quot;express&quot;);<br>const app = express();<br><br>app.get(&quot;/&quot;, (req, res) =&gt; {<br>  axios<br>    .get(&quot;https://en.wikipedia.org/wiki/Main_Page&quot;)<br>    .then((response) =&gt; {<br>      const html = response.data;<br>      const $ = cheerio.load(html);<br><br>      const featuredImage = $(<br>        &quot;#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(1) &gt; a &gt; img&quot;<br>      ).attr(&quot;src&quot;);<br>      const featuredDesc = $(<br>        &quot;#mp-tfp &gt; table &gt; tbody &gt; tr &gt; td:nth-child(2) &gt; p:nth-child(1)&quot;<br>      )<br>        .text()<br>        .trim();<br><br>      res.send({ featuredImage, featuredDesc });<br>    })<br>    .catch((error) =&gt; {<br>      console.log(error);<br>    });<br>});<br><br>app.listen(3000, () =&gt; {<br>  console.log(&quot;Server is running on port 3000&quot;);<br>});</pre><p>Restart the node server and open <a href="http://localhost:3000/">http://localhost:3000</a> in the browser. Now you’ll see something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dBuJ5zGEcvBDTzOIENZzlA.png" /></figure><p>You can start using it as your API to build your web project. This method works well for static websites.</p><p>I hope you find this article useful. In Part — 2 of this series, we will see how to scrape data from Reactive websites with a different approach.</p><p>Feel free to comment with your thoughts and let me know if you face any difficulties.</p><blockquote><em>This article is written by </em><a href="https://github.com/mcnaveen"><strong><em>MC.Naveen</em></strong></a><em> for </em><a href="https://timeless.co/"><strong><em>Timeless</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a34db8e2bbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/web-scraping-with-different-techniques-part-1-4a34db8e2bbb">Web Scraping with different techniques — Part 1</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Nginx Load Balancing for Express Server]]></title>
            <link>https://medium.com/timeless/implementing-nginx-load-balancing-for-express-server-adcd849c37e2?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/adcd849c37e2</guid>
            <category><![CDATA[load-balancer]]></category>
            <category><![CDATA[express]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[load-balancing]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Wed, 15 Feb 2023 13:40:59 GMT</pubDate>
            <atom:updated>2023-02-15T13:40:59.641Z</atom:updated>
            <content:encoded><![CDATA[<p>Nginx is Open Source reverse proxy server better known for its performance and lightweight, It offers multiple functionalities like Reverse Proxying, Load balancing, and so many others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*CfxUFzrP-WLTvlK3dm3Y9Q.png" /></figure><p>In this article, We will see how to use Nginx as a Load Balancer to handle incoming traffic load and distribute it across multiple servers.</p><p>This feature comes out of the box in Nginx and doesn’t need any other dependency to be installed. Only requirement is a bit of modification in the configuration file.</p><p>I’ll be using Express.js to spin up a server that shows a welcome message along with a current port as a JSON Response. The Node process is being handled by pm2.</p><p><strong>Prerequisite:</strong></p><ul><li>Nodejs</li><li>Pm2 installed globally</li></ul><h4>Creating a Server</h4><p>I’m using it as my package manager. Let’s start initiating our project by running the following command. Make sure you’re inside an empty directory.</p><pre>yarn init -y</pre><p>Now, Install these dependencies</p><pre>yarn add express</pre><p>Create a new file index.js and paste the below code.</p><pre>const express = require(&quot;express&quot;);<br>const app = express();<br><br>const port =<br>  process.argv.find((arg) =&gt; arg.startsWith(&quot;--port=&quot;)) || &quot;--port=3000&quot;;<br>const portNumber = port.split(&quot;=&quot;)[1];<br><br>app.get(&quot;/&quot;, (req, res) =&gt; {<br>  res.send({<br>    message: &quot;Hello World!&quot;,<br>    port: `This app is running on ${portNumber}`,<br>  });<br>});<br><br>app.listen(portNumber, () =&gt; {<br>  console.log(`Example app listening at http://localhost:${portNumber}`);<br>});</pre><p>Here is the breakdown of what’s happening in the code.</p><ul><li>First, we are importing the express library</li><li>Then, We are getting the port number from the args with --port</li><li>When the / is requested, the JSON response is sent with the Message and Port Number.</li><li>We will be running on a dynamic port. So the user must pass the PORT. If there is no PORT in args. The default 3000 will be used.</li></ul><p>We are done creating our server. I assume you have pm2 installed globally. If not installed, please follow <a href="https://pm2.io/docs/runtime/guide/installation/">this documentation</a> to install it.</p><p>Now, let’s start our server with pm2 along with the process. Our goal is to have multiple servers running.</p><p>Start multiple servers in different ports 3001, 3002, 3003, 3004, 3005 for each server.</p><pre>pm2 start index.js --name my-server-1 -- --port=3001</pre><p>You can pass any name you want, But I’m keeping my-server-1 it for my identification and passing the port as 3001. Just by modifying these two args. We have to start 4 more servers. Once all is up and running. You’ll something like this in the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXP0Zk3ZXWpmb79gwJQ7-w.png" /><figcaption>pm2 running 5 Express servers</figcaption></figure><p>Now, In your web browser, visit <a href="http://localhost:3001/">http://localhost:3001</a> you will see this message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*QJHXx-0R55rGnQXEcjj3wA.png" /><figcaption>JSON Response from Express App running on PORT 3001</figcaption></figure><p>There are 4 more servers running on 3002, 3003, 3004, and 3005. You can see the response getting changed on each port.</p><h4>Configuring Nginx as a load balancer.</h4><p>By this step, I hope all your node servers are running</p><p>In your Nginx conf. Add an upstream block like this, with all pointing to the express server running on multiple ports, and modify the proxy_pass with the servers. Here the word servers is an alias of the upstream block.</p><pre> upstream servers {<br>        server 127.0.0.1:3001;<br>        server 127.0.0.1:3002;<br>        server 127.0.0.1:3003;<br>        server 127.0.0.1:3004;<br>        server 127.0.0.1:3005;<br>    }<br><br>    server {<br>        listen 80;<br>        server_name example.com;<br><br>        location / {<br>            proxy_pass http://servers;<br>            proxy_set_header Host $host;<br>            proxy_set_header X-Real-IP $remote_addr;<br>        }<br>    }</pre><p>You have to reload the Nginx for changes to take effect. From now, the Nginx not just act as a reverse proxy, but also as a load balancer distributing the traffic across the upstream servers.</p><p>This is a basic implementation, But there is more configuration available to utilize the powerful load-balancing.</p><ul><li>The default, methodology is <strong>Round Robin</strong>. The traffic load is distributed evenly across the servers.</li><li><strong>Least Connections</strong> — This method distributes the load to the server which has the least connection or load.</li><li><strong>IP Hash</strong> — This always forwards the request to the server where the client is connected for the first time.</li></ul><p>There are a few more, but these are the most widely used.</p><p>Here is the config changes for Each of the methods. Round Robin is the default.</p><p><strong>Least Connections:</strong></p><pre>upstream servers {<br>        least_conn;<br>        server 127.0.0.1:3001;<br>        server 127.0.0.1:3002;<br>        server 127.0.0.1:3003;<br>        server 127.0.0.1:3004;<br>        server 127.0.0.1:3005;<br>    }<br><br>    server {<br>        listen 80;<br>        server_name example.com;<br><br>        location / {<br>            proxy_pass http://servers;<br>            proxy_set_header Host $host;<br>            proxy_set_header X-Real-IP $remote_addr;<br>        }<br>    }</pre><p><strong>IP Hash:</strong></p><pre>upstream servers {<br>        ip_hash;<br>        server 127.0.0.1:3001;<br>        server 127.0.0.1:3002;<br>        server 127.0.0.1:3003;<br>        server 127.0.0.1:3004;<br>        server 127.0.0.1:3005;<br>    }<br><br>    server {<br>        listen 80;<br>        server_name example.com;<br><br>        location / {<br>            proxy_pass http://servers;<br>            proxy_set_header Host $host;<br>            proxy_set_header X-Real-IP $remote_addr;<br>        }<br>    }</pre><p>That’s it for this article. Hope this will be helpful to Implement Nginx Load Balancing for Express Server</p><p>Feel free to comment with your thoughts and let me know if you face any difficulties.</p><blockquote><em>This article is written by </em><a href="https://github.com/mcnaveen"><strong><em>MC.Naveen</em></strong></a><em> for </em><a href="https://timeless.co/"><strong><em>Timeless</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=adcd849c37e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/implementing-nginx-load-balancing-for-express-server-adcd849c37e2">Implementing Nginx Load Balancing for Express Server</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploy Express API with Docker]]></title>
            <link>https://medium.com/timeless/deploy-express-api-with-docker-7e814f427fa8?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e814f427fa8</guid>
            <category><![CDATA[dockerfiles]]></category>
            <category><![CDATA[expressjs]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[docker-image]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Tue, 28 Jun 2022 13:37:54 GMT</pubDate>
            <atom:updated>2022-06-28T13:37:54.212Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dockerizing a simple Express API</h3><p>Docker is a cross-platform virtualization technology that provides OS-level virtualization to run applications on the cloud. It enables developers to ship their apps as containers and avoid system conflicts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5GnAjKzwp3AIV-cwg7JJAA.png" /></figure><p>Docker containers can be published via DockerHub or can be distributed locally using zip files. As of writing this article, DockerHub hosts more than one million public docker containers and images.</p><h4>Setting up our Express API</h4><p>Our Express API is pretty simple and contains only one GET route which says hello message.</p><p>This is what my index.js file looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wiwgeiGQ_8Ex2p6wK1k-zg.png" /></figure><p>Now, create a new file called Dockerfile and paste the below code inside it.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc41530d658901e18420d5ba585c0bd4/href">https://medium.com/media/cc41530d658901e18420d5ba585c0bd4/href</a></iframe><p>Breakdown of the Above file contents.</p><ul><li><strong>FROM Node:16</strong> will pull the Node v16 image from the DockerHub</li><li><strong>WORKDIR /usr/src/app </strong>—<strong> </strong>Here is where our app lives inside the container</li><li><strong>COPY package*.json ./</strong> — Copy the package.json from local dir to docker image.</li><li><strong>RUN yarn install </strong>— This will install all the dependencies.</li><li><strong>COPY . . </strong>— This will copy all the project files into the Docker image.</li><li><strong>EXPOSE 3000</strong> — This will allocate a docker container to use port 3000</li><li><strong>CMD [ “node”, “index.js”]</strong> — This will start the Node JS app.</li></ul><h4>The Dockerignore file:</h4><p>Now create a .dockerignore file and add the below content inside it.</p><pre>node_modules</pre><pre>yarn*.log</pre><p>Similar to .gitignore this will ignore the below-mentioned files when building the docker image.</p><h4>Building the Docker Image:</h4><p>Once the above process is done, We have to build our project as a docker image to use it.</p><p>Docker image can be built using a single line of command.</p><pre>docker build . -t=&quot;timeless-hello-world&quot;</pre><ul><li>-t — holds the name of the docker image we are building. You can use any name you want.</li></ul><h4>Running the Docker Image:</h4><p>To run the docker image we built, we have to run another command and pass the name of the image we just built.</p><pre>docker run -d -p 3000:3000 --name my-app timeless-hello-world</pre><p>Breakdown of the above command:</p><ul><li><strong>-d</strong> will detach the terminal after the successful run. Otherwise, the server will stop if we close the terminal.</li><li><strong>-p 3000:3000</strong> is the port we want our application to run.</li><li><strong>--name my-app</strong> is the name of the container.</li><li>Finally, <strong>timeless-hello-world</strong> is the docker image we built in the above step.</li></ul><p>Once you press the enter key. You’ll be prompted with the container ID.</p><p>We can also verify whether the container is running using the docker ps command.</p><p>If you open <a href="http://localhost:3000/">http://localhost:3000</a> in the browser, You’ll get an API response like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8i6qthikmjxxVGE2dTNRg.png" /></figure><p>That’s it for this article. Hope this will be helpful to deploy your Express API using docker.</p><p>Feel free to comment your thoughts and let me know if you face any difficulty.</p><blockquote><em>This article is written by </em><a href="https://github.com/mcnaveen"><strong><em>MC.Naveen</em></strong></a><em> for </em><a href="https://timeless.co/"><strong><em>Timeless</em></strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e814f427fa8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/deploy-express-api-with-docker-7e814f427fa8">Deploy Express API with Docker</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scheduled Netlify Builds with GitHub Actions]]></title>
            <link>https://medium.com/timeless/scheduled-netlify-builds-with-github-actions-2b2d8ca79971?source=rss-2c7c8309d175------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b2d8ca79971</guid>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[netlify]]></category>
            <dc:creator><![CDATA[MC Naveen]]></dc:creator>
            <pubDate>Thu, 23 Jun 2022 08:04:49 GMT</pubDate>
            <atom:updated>2022-06-23T08:04:49.574Z</atom:updated>
            <content:encoded><![CDATA[<p>GitHub actions are super helpful for so many use cases. Such as Triggering CI/CD Builds on specific actions like pushing to a branch. This behavior can be expanded to run the cron job at a specific time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*CM8Csf6MLJLT0d5YnuH7Iw.png" /></figure><p>In this blog post, we will see how we can use GitHub Actions to Trigger the Netlify build at a specific time.</p><p>I had a use case to rebuild the site hosted on Netlify daily at 12 AM. Doing this manually is nearly impossible since I live in a different time zone.</p><p>For this method, you need a GitHub Account, Site Hosted on Netlify with Continuous Deployment enabled.</p><h3>What is Netlify Build Hooks?</h3><p>According to Netlify, Build Hooks are kinda webhook URLs you can use to trigger new builds and deploys. You can read more about it <a href="https://docs.netlify.com/configure-builds/build-hooks/">here</a>.</p><p>You can get Build Hooks under Settings &gt; Build &amp; deploy &gt; Continuous deployment &gt; Build hooks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KMJV4wg735xp3C8X" /><figcaption>Netlify Build Hooks</figcaption></figure><p>Click on the Add Build Hook button. Fill in the Name and Select the GitHub Branch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jo53YOaWEJ96s2sK" /><figcaption>Creating a Netlify Build Hooks</figcaption></figure><p><em>Please note that this method requires you to connect your GitHub repository to Netlify and Continous Deployment is enabled.</em></p><p>Copy the URL provided since we need it later in during the setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KtURT6n3FG2U3rnr" /><figcaption>Copy the Created Build Hook</figcaption></figure><h3>Implementing Actions</h3><p>Now in the root of your project folder, create a folder called <strong><em>.github</em></strong> inside of it create another folder called <strong><em>workflows</em></strong> then inside that create a <strong><em>main.yml</em></strong> file and paste the below code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/85361c0da0b1548e5be77b9a73ffa038/href">https://medium.com/media/85361c0da0b1548e5be77b9a73ffa038/href</a></iframe><p>Make sure to replace <strong>URL_GOT_FROM_NETLIFY</strong> with the URL you got from the above step.</p><blockquote><strong>The path should be like this:</strong> .github/workflows/main.yml</blockquote><p>Once you did that, push the code to the repo. The Workflow will execute at the specified time. Right now it’s set to 12 AM UTC.</p><p><strong>You can change that in line 7.</strong></p><p>You can get a little help from <a href="https://crontab.guru/">https://crontab.guru/</a> for cron times.</p><p>This can be expanded even further with the help of the <a href="https://github.com/marketplace/actions/set-timezone">Set Timezone plugin</a> to perform cron based on your preferred timezone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tc1rN7zO3YQoXjF5bBrhhQ.png" /></figure><p>That’s it for this article. Hope this will be helpful to deploy your static site at a specific time.</p><p>Feel free to comment your thoughts and let me know if you face any difficulty.</p><blockquote>This article is written by <a href="https://github.com/mcnaveen"><strong>MC.Naveen</strong></a> for <a href="https://timeless.co/"><strong>Timeless</strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b2d8ca79971" width="1" height="1" alt=""><hr><p><a href="https://medium.com/timeless/scheduled-netlify-builds-with-github-actions-2b2d8ca79971">Scheduled Netlify Builds with GitHub Actions</a> was originally published in <a href="https://medium.com/timeless">Timeless</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>