<?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 Firat Gulec on Medium]]></title>
        <description><![CDATA[Stories by Firat Gulec on Medium]]></description>
        <link>https://medium.com/@firat-gulec?source=rss-7d2e2e2eae1a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*A-v1zL2jGw87iy_j72hQ6g.png</url>
            <title>Stories by Firat Gulec on Medium</title>
            <link>https://medium.com/@firat-gulec?source=rss-7d2e2e2eae1a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:43:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@firat-gulec/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[Riding the Invisible Waves: The Modern Pilot’s Challenge and a Digital Companion (Final Part)]]></title>
            <link>https://medium.com/@firat-gulec/riding-the-invisible-waves-the-modern-pilots-challenge-and-a-digital-companion-final-part-40d31ea7dd63?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/40d31ea7dd63</guid>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[tourism]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 12:21:00 GMT</pubDate>
            <atom:updated>2026-06-13T12:21:00.826Z</atom:updated>
            <content:encoded><![CDATA[<h3>We mapped the roads. We mapped the oceans. We mapped the stars. But how do you navigate something you cannot even see?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bZguww8e0WOD__GQsDpbjA.jpeg" /></figure><p>If you ask most people what a pilot does, they imagine control.</p><p>A steering wheel.<br>An engine.<br>Buttons, switches, instruments.<br>The ability to point a machine toward a destination and go there directly.</p><p>But hot air balloon pilots live in a completely different world.</p><p>A balloon pilot does not truly “drive” through the sky.</p><p>They negotiate with it.</p><p>They read it.<br>Interpret it.<br>Respect it.</p><p>And above all else: They surrender to the wind.</p><p>More than 240 years after the first flights of the Montgolfier brothers, the core mechanics of balloon flight remain almost unchanged.</p><p>You heat the air to climb.<br>You cool the air to descend.</p><p>That’s it.</p><p>No steering wheel.<br>No wings.<br>No directional thrust.</p><p>Everything else depends on invisible rivers of moving air.</p><p>And in today’s increasingly crowded skies, that ancient simplicity creates an incredibly modern problem.</p><h3>Flying Without Steering</h3><p>This is one of the hardest concepts for non-pilots to fully understand:</p><p>Hot air balloons cannot steer like airplanes.</p><p>A pilot cannot simply “turn left.”</p><p>Instead, balloon pilots navigate vertically in order to move horizontally.</p><p>Different wind layers exist at different altitudes. One layer may drift east. Another may move south. A higher layer may suddenly push west.</p><p>The pilot’s real skill lies in finding the right altitude at the right moment to catch the right wind.</p><p>In many ways, ballooning resembles: Sailing without water, surfing invisible currents or playing three-dimensional chess against the atmosphere itself.</p><p>And unlike most forms of aviation, the environment is constantly changing.</p><p>The sky is alive.</p><h3>The Invisible Battlefield Above the Earth</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ybivBNHpreXvqttB" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RgV_IL5q3wCYKg6x" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g3tsWPAKswPFX3KY" /></figure><p>From the ground, ballooning appears peaceful.</p><p>Tourists sip champagne.<br>Passengers take photographs.<br>The sunrise paints the valleys gold.</p><p>But inside the basket, the pilot’s mind is processing an enormous amount of information every second.</p><p>Especially in locations like: Cappadocia</p><p>On busy mornings, more than 100 balloons may share the same airspace.<br>That creates extraordinary complexity.</p><p>A pilot must constantly monitor:</p><ul><li>altitude,</li><li>vertical separation,</li><li>surrounding balloon traffic,</li><li>terrain,</li><li>fuel consumption,</li><li>changing wind directions,</li><li>possible landing zones,</li><li>restricted airspaces,</li><li>emergency landing options,</li><li>and communication with chase crews on the ground.</li></ul><p>Unlike airplanes operating in structured air corridors, balloon pilots move dynamically with atmospheric conditions.</p><p>Every flight becomes unique.</p><p>Even pilots launching from the same location at the same time may land in entirely different valleys depending on wind layers.</p><p>And because balloons move relatively slowly, pilots are continuously planning ahead.</p><p>Where will this wind take me in 10 minutes?<br>What happens if the upper layer shifts?<br>Is another balloon descending into my path?<br>Can my chase crew reach this landing area?<br>Is the terrain safe if the wind speed increases?</p><p>The workload is far greater than most passengers realize.</p><h3>The Problem With Generic Aviation Tools</h3><p>Despite the complexity of ballooning, pilots have historically relied on fragmented and improvised tools.</p><p>For decades, many balloon pilots managed flights using combinations of:</p><ul><li>generic weather applications,</li><li>paper maps,</li><li>radios,</li><li>GPS devices,</li><li>handwritten notes,</li><li>and verbal communication with chase crews.</li></ul><p>The problem is simple:</p><p>Most aviation tools are not designed for balloons.</p><p>And most weather apps are designed for ordinary people.</p><p>A standard weather app answers questions like:</p><ul><li>“Will it rain today?”</li><li>“What’s the temperature?”</li><li>“Do I need an umbrella?”</li></ul><p>But balloon pilots require something far more specialized.</p><p>They need to know:</p><ul><li>wind direction at multiple altitudes,</li><li>wind speed transitions,</li><li>terrain-induced turbulence,</li><li>vertical atmospheric behavior,</li><li>and how all of those variables interact in real time.</li></ul><p>Because for a balloon pilot, altitude is navigation.</p><p>A difference of only a few hundred feet can completely change the direction of travel.</p><p>That is not normal aviation logic.</p><p>It is uniquely ballooning.</p><h3>A Gap in Modern Aviation</h3><p>As both a software developer and someone deeply fascinated by aviation, I began noticing something strange.</p><p>Modern aviation had evolved dramatically.</p><p>Airline pilots use advanced navigation systems.<br>Private pilots have sophisticated flight planning tools.<br>Drone operators use live telemetry and mapping systems.<br>Even hikers and cyclists now have powerful digital navigation companions.</p><p>But balloon pilots — descendants of the very first humans to fly — were still piecing together disconnected tools for one of the most weather-dependent forms of aviation in existence.</p><p>That felt wrong.</p><p>Ballooning is not outdated.</p><p>In fact, modern balloon operations are becoming increasingly complex:</p><ul><li>more balloons,</li><li>more tourism,</li><li>more regulations,</li><li>more airspace awareness,</li><li>more safety considerations,</li><li>and greater coordination requirements.</li></ul><p>Yet the software ecosystem remained surprisingly limited.</p><p>I realized there was a major gap.<br>Not a gap in ballooning itself.<br>A gap in digital support for balloon pilots.</p><p>And that realization became the beginning of something much bigger.</p><h3>The Question That Started Everything</h3><p>At some point, one question kept returning to my mind:</p><blockquote><em>“What would the ideal digital companion for a balloon pilot actually look like?”</em></blockquote><p>Not a generic aviation app.<br>Not a modified hiking app.<br>Not another standard weather dashboard.</p><p>But a platform designed specifically around the unique logic of hot air balloon navigation.</p><p>A system built around:</p><ul><li>altitude-based movement,</li><li>wind-layer awareness,</li><li>flight coordination,</li><li>landing prediction,</li><li>and chase crew communication.</li></ul><p>Because balloon pilots do not need to overpower the atmosphere.<br>They need to understand it better.</p><p>That idea eventually became: <strong>Hot Air Balloon Map AI.</strong></p><p><a href="https://firatgulec.com/hotairballoonmap?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=riding-the-invisible-waves&amp;utm_content=inline-link">Hot Air Balloon Map</a></p><h3>Building a Digital Copilot</h3><p>The goal behind Hot Air Balloon Map was never to replace pilot instinct.</p><p>That instinct is sacred in ballooning.</p><p>Experienced pilots develop extraordinary environmental awareness over years of flying:</p><ul><li>reading terrain,</li><li>sensing thermal activity,</li><li>interpreting subtle wind behavior,</li><li>and making rapid safety decisions.</li></ul><p>No application can replace human judgment.<br>But technology can reduce cognitive overload.<br>It can improve situational awareness.</p><p>It can organize information in ways that help pilots focus on what matters most: Safe and intelligent flight decisions.</p><p>The idea was to create something that feels less like software…</p><p>and more like a true aerial companion.</p><h3>Solving Real Pilot Problems</h3><p>Every feature concept came from real operational challenges balloon pilots face.</p><p>For example:</p><h3>Real-Time Position Awareness</h3><p>Pilots need accurate live positioning during flights, especially in crowded airspace environments.</p><h3>Wind Layer Visualization</h3><p>Instead of simply showing surface weather, pilots need altitude-sensitive wind understanding.</p><p>Because a balloon’s direction changes with altitude, visualizing atmospheric layers becomes incredibly valuable.</p><h3>Chase Crew Coordination</h3><p>One of the most overlooked aspects of ballooning is the ground crew.</p><p>After launch, chase vehicles follow balloons across roads and valleys, attempting to predict landing areas.</p><p>Poor coordination creates:</p><ul><li>delays,</li><li>confusion,</li><li>unsafe retrieval conditions,</li><li>and communication problems.</li></ul><p>A dedicated system can help synchronize:</p><ul><li>pilot location,</li><li>projected landing zones,</li><li>route visibility,</li><li>and team coordination.</li></ul><h3>Flight Path Awareness</h3><p>In highly active skies, situational awareness matters enormously.</p><p>Pilots benefit from understanding nearby balloon activity and projected movement patterns.</p><h3>Simplifying the Pilot Workflow</h3><p>Instead of juggling: Radios, weather apps, GPS tools and disconnected mapping systems,</p><p>the vision was to unify critical flight information into a cleaner, more intuitive experience.</p><p>Not more complexity.<br>Less.</p><h3>Respecting the Art of Ballooning</h3><p>One of the most important design philosophies behind the project was this:</p><p>Technology should support ballooning — not sterilize it.<br>Because ballooning is emotional.</p><p>It is one of the few remaining forms of aviation where pilots remain deeply connected to nature itself.</p><p>You feel:<br>Temperature changes, wind shifts, silence, sunlight and terrain.</p><p>There is no sealed cockpit separating the pilot from the environment.<br>That raw connection is part of what makes ballooning beautiful.<br>The purpose of digital tools should never be to remove that humanity.</p><p>The goal is simply to help pilots: See more clearly, coordinate more effectively and fly more safely.</p><p>The romance of ballooning should remain untouched.</p><p>Only the information layer evolves.</p><h3>From 1783 to the Digital Sky</h3><p>When the first balloon rose above France in 1783, humanity entered the sky for the first time.</p><p>Back then, balloonists relied purely on: <br>Instinct, observation, courage and experimentation.</p><p>More than two centuries later, the spirit remains the same.</p><p>Pilots still wake before sunrise.<br>They still study the weather.<br>They still trust the wind.<br>They still surrender part of the journey to nature itself.</p><p>But today, we also have something the Montgolfier brothers never could have imagined:</p><p>real-time digital information.</p><p>The story of ballooning has always been about pushing boundaries.</p><p>First physical boundaries.<br>Then atmospheric boundaries.<br>Now digital boundaries.</p><p>And perhaps that is the next evolution of flight: not replacing human skill…<br>but augmenting it.</p><h3>The Future of Ballooning</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yDflEAJwQjN-Ec5w" /></figure><p>The skies are becoming busier.</p><p>Tourism continues growing.<br>Safety expectations are increasing.<br>Airspace management is evolving rapidly.</p><p>Balloon pilots deserve tools designed specifically for their world.<br>Because ballooning is not simply a tourist activity.</p><p>It is a specialized form of aviation with its own unique challenges, risks, and beauty.</p><p>And while the wind may always remain invisible…<br>It no longer needs to remain unpredictable.</p><h3>Explore Hot Air Balloon Map</h3><p>If you are:<br>A balloon pilot, chase crew member, balloon operator, aviation enthusiast or simply fascinated by the intersection of history, nature and technology,</p><p>I invite you to explore the journey behind <strong>Hot Air Balloon Map</strong>.</p><p>The dream that began with smoke and fabric in 1783 is still evolving today.</p><p>Only now, it lives not just in the sky but also in the digital world helping pilots navigate it.</p><h3>Sources &amp; References</h3><ul><li>General ballooning operational practices and aviation safety procedures</li><li>Historical balloon navigation methodologies</li><li>Modern hot air balloon flight coordination workflows</li><li>Author’s personal development journey and aviation technology research</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40d31ea7dd63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Modern Renaissance: Propane, Festivals, and the Magic of Tourism (Part-3)]]></title>
            <link>https://medium.com/@firat-gulec/the-modern-renaissance-propane-festivals-and-the-magic-of-tourism-part-3-476ae657c5cf?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/476ae657c5cf</guid>
            <category><![CDATA[history]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[tourism]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[travel-writing]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 13:31:00 GMT</pubDate>
            <atom:updated>2026-06-06T13:31:00.671Z</atom:updated>
            <content:encoded><![CDATA[<h3>How hot air balloons escaped extinction, conquered the tourism world, and became one of humanity’s most breathtaking experiences.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sI0l4W_8NUM_Bj6i" /><figcaption>Photo by <a href="https://unsplash.com/@farshadrezvanian?utm_source=medium&amp;utm_medium=referral">Freddy Rezvanian</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>By the middle of the 20th century, hot air balloons were becoming relics of the past.</p><p>The world had changed.<br>Airplanes crossed oceans at incredible speed. Military jets shattered the sound barrier. Helicopters hovered with precision above cities and battlefields. Humanity was entering the age of powered aviation, rockets, and eventually space travel.</p><p>Compared to these technological marvels, balloons seemed primitive.<br>Slow.<br>Uncontrollable.<br>Outdated.</p><p>The very invention that had first carried humans into the sky now appeared destined for museums and history books.<br>And honestly, many people believed ballooning’s story was over.</p><p>But aviation history has a strange pattern: Sometimes the oldest ideas return in entirely new forms.</p><p>Because just when hot air ballooning was fading into obscurity, one inventor transformed it from a dangerous scientific curiosity into one of the world’s most magical aerial experiences.</p><p>And in doing so, he sparked a global renaissance.</p><h3>The Problem That Nearly Killed Ballooning</h3><p>Early ballooning had always suffered from the same core problems: Danger, complexity, poor control and impracticality.</p><p>Traditional hot air balloons required enormous open fires fueled by: <br>Wood, straw, wool or coal.</p><p>The fire had to remain active throughout the flight, directly beneath highly flammable fabric. It was terrifyingly unsafe.</p><p>Gas balloons solved some endurance problems, especially hydrogen-filled designs, but hydrogen introduced an even greater danger:</p><blockquote>explosion.</blockquote><p>Throughout the 19th and early 20th centuries, countless balloon accidents occurred because of: Fires, structural failures, weather or gas ignition.</p><p>Then came rigid airships like the Zeppelin, which briefly appeared to be the future of lighter-than-air travel.</p><p>But after disasters such as the Hindenburg disaster, public trust in lighter-than-air aviation collapsed dramatically.</p><p>By the 1950s, ballooning survived mostly as a niche hobby practiced by enthusiasts and historians.</p><p>The romance remained.<br>But the practicality was gone.<br>Until one man changed everything.</p><h3>Ed Yost — The Father of Modern Ballooning</h3><p>Ed Yost is often called: <em>“The Father of Modern Hot Air Ballooning.” a</em>nd that title is absolutely deserved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/486/0*k6Z7CUduLcFtGnut" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*_KiMpkOvVoaeG3Js" /></figure><p>In October 1960, Yost accomplished something revolutionary.</p><p>He took the ancient concept of hot air ballooning and rebuilt it using modern materials and engineering.</p><p>His innovations included: Lightweight nylon fabric, portable propane fuel systems, efficient burners and improved balloon envelope design.</p><p>This combination solved the biggest historical problems of balloon flight.</p><p>Instead of maintaining a dangerous wood fire, pilots could now generate controlled bursts of heat using propane burners.</p><p>The advantages were enormous: Safer operation, longer flights, better altitude control, easier transportation, faster inflation and more reliable performance.</p><p>For the first time in history, ballooning became genuinely practical for recreational flight.</p><p>Yost’s modern balloon could be packed into a trailer or pickup truck, transported easily, inflated within minutes, and flown safely by trained pilots.</p><p>It was no longer an experiment.</p><p>It became an experience.</p><h3>Ballooning Becomes Emotional Again</h3><p>Modern ballooning succeeded for a fascinating reason:</p><p>it stopped trying to compete with airplanes.</p><p>Airplanes are about efficiency.<br>Helicopters are about maneuverability.<br>Jets are about speed.</p><p>But hot air balloons offered something entirely different.</p><blockquote>Silence.<br>Stillness.<br>Wonder.</blockquote><p>The experience of floating in a balloon feels unlike any other form of aviation.</p><p>There is no violent acceleration.<br>No roaring engine vibration.<br>No sensation of mechanical force pushing you forward.</p><p>Instead, the Earth quietly drifts beneath you.</p><p>The only sound is the occasional roar of the burner — a deep burst of fire interrupting long periods of peaceful silence.</p><p>Passengers do not feel like they are traveling.</p><p>They feel like they are dreaming. And that emotional experience became the true power of modern ballooning.</p><h3>The Birth of Balloon Festivals</h3><p>As ballooning spread across the United States and Europe during the 1960s and 1970s, public gatherings of balloons became increasingly popular.</p><p>Pilots realized that dozens — or even hundreds — of colorful balloons rising together created an almost surreal visual spectacle.</p><p>Soon, balloon festivals emerged around the world.</p><p>These events combined: Aviation, tourism, photography, local culture and celebration.</p><p>And eventually, one festival became legendary.</p><h3>Albuquerque — The Sky Becomes a Canvas</h3><p>Every October, the skies above Albuquerque transform into one of the most visually extraordinary scenes on Earth:</p><p>The Albuquerque International Balloon Fiesta.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3VomKrPWraWhHXsw" /></figure><p>What began in 1972 with only a handful of balloons evolved into the world’s largest balloon festival.</p><p>Today:</p><ul><li>over 500 balloons participate,</li><li>pilots travel from dozens of countries,</li><li>and hundreds of thousands of spectators attend annually.</li></ul><p>At sunrise, massive “mass ascensions” fill the desert sky with impossible colors.</p><p>Some balloons resemble:</p><ul><li>dragons,</li><li>cartoon characters,</li><li>castles,</li><li>animals,</li><li>spacecraft,</li><li>and abstract art.</li></ul><p>The event feels less like transportation and more like living inside a painting.</p><p>At night, the famous “Balloon Glow” illuminates the darkness as tethered balloons fire their burners simultaneously, creating giant glowing lanterns across the field.</p><p>For many people, Albuquerque becomes their first realization that ballooning is not an obsolete technology.</p><p>It is a living culture.</p><h3>Cappadocia — The Ultimate Balloon Landscape</h3><p>Halfway across the world, another region transformed ballooning into something even more cinematic:</p><blockquote>Cappadocia.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qdL0XcfgP2cLjee8" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Yo1quXSgbb-gUWmn" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rhv3H7ao8hzIeYMg" /></figure><p>The volcanic landscapes of Cappadocia look almost alien:</p><ul><li>fairy chimneys,</li><li>deep valleys,</li><li>cave dwellings,</li><li>and rock formations carved by millions of years of erosion.</li></ul><p>The environment already feels dreamlike from the ground.</p><p>From the sky, it becomes unforgettable.</p><p>Beginning in the 1990s and accelerating rapidly in the 2000s, Cappadocia evolved into one of the world’s premier ballooning destinations.</p><p>Today, during ideal weather conditions, as many as:</p><ul><li>100 to 150 balloons<br>can launch before sunrise on busy mornings.</li></ul><p>The coordination required is extraordinary.</p><p>Before dawn:</p><ul><li>crews unpack envelopes,</li><li>burners roar to life,</li><li>pilots analyze weather reports,</li><li>chase vehicles position themselves,</li><li>and passengers gather in darkness awaiting takeoff.</li></ul><p>Then, almost simultaneously, the balloons rise.</p><p>Within minutes, the sky becomes filled with floating color above ancient valleys glowing orange under the first sunlight of morning.</p><p>For tourists, it feels magical.</p><p>For pilots, it is highly technical aviation.</p><h3>The Hidden Complexity of Balloon Flight</h3><p>To most passengers, ballooning appears effortless.</p><p>The balloon rises peacefully.<br>The landscape drifts below.<br>The sunrise creates perfect photographs.</p><p>But inside the basket, the pilot is constantly working.</p><p>And unlike airplane pilots, balloon pilots face a unique challenge:</p><p>they cannot steer directly.</p><p>This is one of the most misunderstood aspects of balloon flight.</p><p>A hot air balloon has no:</p><ul><li>steering wheel,</li><li>rudder,</li><li>wings,</li><li>or engine-based directional control.</li></ul><p>Instead, pilots navigate by understanding the atmosphere itself.</p><p>Different wind currents exist at different altitudes.</p><p>A pilot changes direction not by turning left or right — but by climbing or descending into different wind layers.</p><p>This means ballooning is less like driving…</p><p>and more like surfing invisible rivers in the sky.</p><h3>Reading the Wind</h3><p>Modern balloon pilots become experts in:</p><ul><li>meteorology,</li><li>terrain effects,</li><li>thermal activity,</li><li>wind shear,</li><li>and atmospheric behavior.</li></ul><p>Even small changes matter enormously.</p><p>A slight altitude adjustment might completely change the balloon’s direction.</p><p>Pilots must constantly evaluate:</p><ul><li>launch safety,</li><li>nearby balloons,</li><li>wind speed,</li><li>landing options,</li><li>fuel reserves,</li><li>terrain obstacles,</li><li>and emergency procedures.</li></ul><p>In crowded environments like Cappadocia or major festivals, the complexity increases dramatically.</p><p>Now pilots must also track:</p><ul><li>surrounding balloon traffic,</li><li>vertical separation,</li><li>landing coordination,</li><li>radio communication,</li><li>and changing tourist flight patterns.</li></ul><p>To spectators, ballooning looks peaceful.</p><p>To pilots, it is dynamic aerial decision-making every second of the flight.</p><h3>Ballooning Enters the Digital Era</h3><p>As tourism ballooning expanded globally, aviation technology evolved as well.</p><p>Pilots increasingly began relying on:</p><ul><li>GPS systems,</li><li>live weather data,</li><li>wind forecasting,</li><li>terrain mapping,</li><li>flight tracking,</li><li>and digital coordination tools.</li></ul><p>Because modern ballooning no longer involves just a few isolated flights.</p><p>In places like Cappadocia, dozens or even hundreds of balloons may share the same airspace simultaneously.</p><p>The margin for error becomes smaller.</p><p>And while instinct and experience remain essential, modern pilots now require something else too:</p><p>real-time information.</p><p>The ancient dream of ballooning had entered the digital age.</p><h3>The Sky Is Still Wild</h3><p>Despite all modern advances, ballooning remains beautifully unpredictable.</p><p>That unpredictability is part of its magic.</p><p>Unlike airplanes, balloons never completely dominate the sky.</p><p>They cooperate with it.</p><p>Pilots still wake before sunrise to study winds.<br>Weather still decides whether flights happen.<br>Nature still holds the final authority.</p><p>And perhaps that is why ballooning continues to fascinate humanity after more than two centuries.</p><p>It reminds us that flight does not always need to be fast.</p><p>Sometimes the most powerful journeys happen slowly, silently, and with the wind itself as your guide.</p><p>But as balloon traffic grows, skies become more crowded, and pilots demand better situational awareness, a new question emerges:</p><p>What if technology could become a true companion for balloon pilots?</p><p>Not replacing their instincts…</p><p>but helping them see the invisible patterns of the sky more clearly than ever before.</p><p>And that question would eventually inspire a new generation of digital tools designed specifically for the unique world of hot air ballooning.</p><h3>Sources &amp; Historical References</h3><ul><li>National Balloon Museum — Ed Yost Biography</li><li><a href="https://balloonfiesta.com/?utm_source=chatgpt.com">Albuquerque International Balloon Fiesta Official Site</a></li><li><a href="https://www.britannica.com/technology/hot-air-balloon?utm_source=chatgpt.com">Britannica — Hot Air Balloon History</a></li><li><a href="https://www.fai.org/commission/cia?utm_source=chatgpt.com">FAI Ballooning Commission</a></li></ul><blockquote><em>As I explore the history of ballooning, I’m also working on its future. I built Hot Air Balloon Map to help pilots manage their flights and live tracking effortlessly. If you’re in the industry, I’d love for you to check it out and download it here:</em></blockquote><p><a href="https://firatgulec.com/hotairballoonmap?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=the-modern-renaissance&amp;utm_content=inline-link">Hot Air Balloon Map</a></p><p><em>(To be continued in the final part: The digital companion for the modern pilot…)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476ae657c5cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Kings to Cannons: The Golden Age and Military Era of Hot Air Balloons (Part-2)]]></title>
            <link>https://medium.com/@firat-gulec/from-kings-to-cannons-the-golden-age-and-military-era-of-hot-air-balloons-part-2-bdec3242385d?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdec3242385d</guid>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[science]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 30 May 2026 13:31:00 GMT</pubDate>
            <atom:updated>2026-05-30T13:31:00.652Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a fragile fabric balloon evolved from royal entertainment into one of history’s first aerial military technologies.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nbegR1RVfwz6w_q2eyqeUA.jpeg" /></figure><p>When humanity first rose into the sky in 1783, the world reacted with wonder.</p><p>Crowds screamed in amazement as enormous fabric balloons floated above cities. Kings watched from palace gardens. Scientists argued excitedly about the future of aviation. Newspapers described balloon ascents as miracles of modern science.</p><p>For the first time in history, humans had escaped the Earth.</p><p>But after the applause faded, reality arrived quickly.</p><p>Flying was easy.</p><p>Controlling flight was nearly impossible.</p><p>The skies that had once seemed magical became unpredictable, violent, and deeply unforgiving. Winds changed direction without warning. Storms swallowed balloons whole. Fires threatened to ignite fragile fabric envelopes suspended above open flames.</p><p>And yet, despite all these dangers, balloons refused to disappear.</p><p>Because governments, militaries, and inventors had already realized something revolutionary:</p><p>Even if a balloon could not reliably transport people…</p><p>it could still change the world.</p><h3>The Balloon Craze That Swept Europe</h3><p>Following the historic flights of Jean-François Pilâtre de Rozier and François Laurent d’Arlandes, Europe entered what historians later called:</p><blockquote><em>“Balloonomania.”</em></blockquote><p>Balloons became symbols of progress, intelligence, and modernity.</p><p>In France and England especially, balloon imagery appeared everywhere:</p><p>Paintings, jewelry, furniture, wallpaper, porcelain, theater productions, hairstyles and even luxury dresses designed to resemble balloon envelopes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-eUoytc_WyIlpNTKqNOs_A.jpeg" /></figure><p>Public launches became massive social events.</p><p>Thousands gathered in fields and palace gardens to watch ascents. Wealthy aristocrats paid enormous sums for private demonstrations. Scientists raced to improve designs while entertainers transformed balloon flights into spectacles.</p><p>Some early balloonists became celebrities across Europe.</p><p>To ordinary citizens, balloon pilots looked almost supernatural — people brave enough to challenge gravity itself.</p><p>But beneath the glamour, ballooning remained extremely primitive.</p><h3>The Brutal Reality of Early Balloon Flight</h3><p>The first generation of balloons suffered from severe limitations.</p><p>Hot air balloons required: Constant fuel, open flames, enormous fabric envelopes and perfect weather conditions.</p><p>The onboard fire created continuous danger. Sparks could ignite the balloon at any moment. Rain weakened the paper and silk materials. Strong winds could drag balloons uncontrollably across forests, rivers, and villages.</p><p>Worst of all:</p><p>Pilots had almost no steering capability.</p><p>A balloon could rise.<br> A balloon could descend.<br> But horizontal direction belonged entirely to the wind.</p><p>This meant that flights were essentially controlled drifting.</p><p>Passengers never truly knew where they would land.</p><p>Some balloons crashed into mountains. Others vanished into storms. Many landed violently in farmland, frightening local villagers who had never seen such machines before.</p><p>In some rural areas, terrified peasants attacked landed balloons, believing they were monsters or devices of witchcraft.</p><p>Humanity had touched the sky — but the sky remained wild.</p><h3>The Hydrogen Revolution</h3><p>Scientists quickly searched for alternatives to traditional hot air balloons.</p><p>One of the most important innovators was: <a href="https://tr.wikipedia.org/wiki/Jacques_Charles">Jacques Charles</a></p><p>Unlike the Montgolfier brothers, Charles believed hydrogen gas offered a far superior lifting method.</p><p>Hydrogen had several advantages:</p><ul><li>it was lighter than hot air,</li><li>required no continuous fire,</li><li>allowed longer flights,</li><li>and provided more stable lift.</li></ul><p>In December 1783, only weeks after the first manned hot air flight, Jacques Charles launched the first successful hydrogen balloon.</p><p>The new gas balloons could remain airborne for dramatically longer periods — sometimes for days rather than minutes.</p><p>This transformed ballooning from a short public demonstration into something with practical potential. But hydrogen introduced a terrifying new risk:</p><blockquote>explosion.</blockquote><p>Hydrogen is highly flammable, and many future balloon disasters would be caused by fire and ignition.</p><p>Still, the advantages were too significant to ignore.<br>Throughout the 19th century, gas balloons became the dominant form of long-distance balloon flight.</p><h3>Balloons Become Tools of Science</h3><p>Before becoming military tools, balloons first became scientific instruments.</p><p>Researchers realized balloons could carry humans higher than any mountain on Earth.</p><p>This opened entirely new possibilities: Atmospheric studies, temperature measurements, pressure experiments, wind analysis and astronomical observation.</p><p>Balloonists became explorers of the upper atmosphere.<br>Some flights reached dangerously high altitudes where oxygen deprivation caused hallucinations, unconsciousness and death.</p><p>Yet scientists kept ascending.<br>For the first time, humanity could directly study the skies instead of merely observing them from below.</p><p>Meteorology itself advanced because of ballooning. <br>The sky was slowly transforming from mythology into measurable science.</p><h3>The Military Sees the Future</h3><p>It did not take long for military strategists to recognize the true power of balloons.</p><p>For thousands of years, generals fought wars with limited visibility. Commanders relied on horseback scouts, signal towers, and messengers to understand enemy movements.</p><p>Battlefields were chaotic.<br>Dust, smoke, forests, hills, and distance made coordination incredibly difficult.</p><p>But a balloon changed everything.<br>From the air, observers could suddenly see: Troop formations, artillery positions, supply routes, cavalry movements and defensive lines.</p><p>For the first time in history, war could be observed from above.<br>And that changed warfare forever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mIDlVBAOsS6X_RXHYAk1Ig.jpeg" /></figure><h3>The First Air Force in History</h3><p>In 1794, during the chaos of the <a href="https://en.wikipedia.org/wiki/French_Revolutionary_Wars">French Revolutionary Wars</a>, France established the world’s first military aviation unit:</p><p>The <strong>Compagnie d’Aérostiers</strong>.<br><a href="https://fr.wikipedia.org/wiki/Compagnie_d%27a%C3%A9rostiers">Compagnie d’Aérostiers</a> was effectively the first air force in human history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/0*Sjl1e_zZRMo030wQ" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QTKvyY6cETOPlW84" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hWUAcYwkWbf1KoAR" /></figure><p>Their most famous balloon was named:<br><strong>L’Entreprenant</strong> (“The Enterprising One”).</p><p>During the <a href="https://en.wikipedia.org/wiki/Battle_of_Fleurus_(1794)">Battle of Fleurus</a>, French observers ascended in a tethered balloon and monitored Austrian troop movements from above.</p><p>This was revolutionary.<br>Instead of relying purely on ground reports, commanders now received real-time battlefield intelligence from the sky.</p><p>Observers reportedly dropped written notes to troops below containing tactical information.</p><p>It was primitive aerial reconnaissance — the ancestor of: Spy planes, reconnaissance aircraft, surveillance drones and military satellites.</p><p>The modern concept of “air superiority” had begun.</p><h3>Napoleon and the Limits of Balloon Warfare</h3><p>Although balloons showed promise, they were not perfect military machines.</p><p>They required: Large crews, difficult transportation, gas production equipment, favorable weather and open launch areas.</p><p>Strong winds made them unreliable near active combat zones.</p><p>As warfare became faster and more mobile during the Napoleonic era, balloons struggled to keep up.</p><p><a href="https://tr.wikipedia.org/wiki/Napolyon_Bonapart">Napoleon Bonaparte</a> reportedly lost interest in military balloon programs because of their logistical complexity.</p><p>For a time, balloon warfare faded into the background. But not for long.</p><h3>The American Civil War and the Return of Military Balloons</h3><p>Nearly seventy years later, balloons returned dramatically during the <a href="https://en.wikipedia.org/wiki/American_Civil_War">American Civil War</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gQaXqdb5TKcrWv-O" /></figure><p>The Union Army created the: <a href="https://en.wikipedia.org/wiki/Union_Army_Balloon_Corps">Union Army Balloon Corps</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*otgPTdXYQYsrI0_0" /></figure><p>The program was led by: <a href="https://en.wikipedia.org/wiki/Thaddeus_S._C._Lowe">Thaddeus Lowe</a></p><p>Lowe was not merely a showman — he was a brilliant aeronautical innovator. He convinced President <a href="https://tr.wikipedia.org/wiki/Abraham_Lincoln">Abraham Lincoln</a> that balloons could provide crucial battlefield intelligence.</p><p>Lincoln became fascinated with the idea.<br>Soon, military balloons were being deployed across Union operations.</p><p>Observers ascended hundreds of feet above battlefields using tethered balloons connected to the ground.</p><p>From the air, they could identify: Confederate troop concentrations, hidden artillery, defensive movements and attack preparations.</p><p>Even more impressive, some balloons communicated with commanders using telegraph lines connected directly from the balloon basket to the ground.</p><p>This effectively created one of history’s earliest forms of airborne real-time communication.</p><h3>The First Aircraft Carriers?</h3><p>One of the most remarkable innovations of the Civil War involved balloon launches from boats.</p><p>Thaddeus Lowe adapted flat barges and riverboats into mobile balloon platforms.</p><p>These floating launch systems allowed reconnaissance balloons to operate near waterways and battle zones.</p><p>Historians sometimes describe them as primitive ancestors of modern aircraft carriers.</p><p>Long before airplanes existed, militaries were already experimenting with mobile aerial warfare.</p><h3>The Siege of Paris — Balloons as Lifelines</h3><p>Perhaps the most dramatic chapter in balloon history occurred during the <a href="https://en.wikipedia.org/wiki/Siege_of_Paris_(1870%E2%80%931871)">Siege of Paris</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ql7PSw0qKtboC_0P" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DaL75bl-LtuE16ns" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JfERlOCebZS2xYE_" /></figure><p>During the <a href="https://en.wikipedia.org/wiki/Franco-Prussian_War">Franco-Prussian War</a>, Prussian forces completely surrounded Paris.</p><p>The city became isolated.<br>Roads were blocked.<br>Railways were cut off.<br>Communication collapsed.<br>But Paris still had balloons.</p><p>In desperation, the French began launching manned gas balloons out of the besieged city.</p><p>These flights carried: <br>Letters, military messages, government officials, newspapers and carrier pigeons.</p><p>Over the course of the siege: <br>66 balloons escaped Paris, millions of letters were transported and critical communications survived because of aerial delivery.</p><p>Some balloons traveled hundreds of kilometers.<br>Others crashed behind enemy lines or vanished in storms.</p><p>But the balloon network became one of history’s earliest large-scale air mail systems.</p><p>It was both heroic and chaotic — a desperate society surviving through aviation.</p><h3>The Romance and Danger of Ballooning</h3><p>Throughout the 19th century, ballooning occupied a strange place in society.</p><p>It was: Scientific, military, adventurous and theatrical all at once.</p><p>Balloon pilots became international celebrities. Crowds attended ascents the way modern audiences attend airshows or rocket launches.</p><p>Yet fatalities remained common.</p><p>Pilots faced:<br>Fires, gas explosions, freezing temperatures, storms, lightning and catastrophic crashes.</p><p>Some balloonists disappeared forever.<br>Still, the fascination never faded.</p><p>Because ballooning represented something deeply emotional:<br>humanity refusing to remain earthbound.</p><h3>The End of the First Balloon Era</h3><p>By the late 19th century, balloons had achieved remarkable things: Scientific discovery, aerial reconnaissance, military observation, long-distance communication and atmospheric exploration.</p><p>But they still suffered from one fatal weakness: They could not truly be controlled.<br>Then, at the dawn of the 20th century, a new invention appeared.<br>The airplane.<br>Powered flight offered: Speed, steering, maneuverability and military precision.</p><p>Compared to airplanes, traditional balloons suddenly looked outdated.<br>The age of the balloon appeared to be ending.</p><p>But history had one final surprise waiting.</p><p>Because decades later, a technological breakthrough involving propane burners and modern materials would resurrect hot air ballooning in an entirely new form — transforming it from military tool into one of the world’s most breathtaking aerial experiences.</p><p>And that rebirth would begin in the skies of postwar America.</p><h3>Sources &amp; Historical References</h3><ul><li><a href="https://library.si.edu/exhibition/fantastic-worlds/age-of-the-aeronaut">Smithsonian National Air and Space Museum — Ballooning History</a></li><li><a href="https://www.britannica.com/technology/balloon-flight">Encyclopaedia Britannica — Balloon Flight History</a></li><li><a href="https://www.sciencehistory.org/stories/disappearing-pod/the-great-balloon-escape/">History of Siege of Paris Balloon Mail</a></li></ul><blockquote>As I explore the history of ballooning, I’m also working on its future. I built Hot Air Balloon Map to help pilots manage their flights and live tracking effortlessly. If you’re in the industry, I’d love for you to check it out and download it here:</blockquote><p><a href="https://firatgulec.com/hotairballoonmap?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=from-king&amp;utm_content=inline-link">Hot Air Balloon Map</a></p><p><em>(To be continued in Part 3: The Modern Renaissance: Propane, Festivals, and the Magic of Tourism)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdec3242385d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Spark of Flight: How Humanity First Touched the Sky (Part-1)]]></title>
            <link>https://medium.com/@firat-gulec/the-spark-of-flight-how-humanity-first-touched-the-sky-a8e12a414cd2?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8e12a414cd2</guid>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[transportation]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[history]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sun, 24 May 2026 18:57:45 GMT</pubDate>
            <atom:updated>2026-05-31T04:23:03.440Z</atom:updated>
            <content:encoded><![CDATA[<h3>Before airplanes, engines, or helicopters, there was fire, fabric, fear, and one impossible dream: to rise above the Earth.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQOmluWyVaGxBkmQGglT4Q.jpeg" /></figure><p>For thousands of years, humanity looked upward with envy.</p><p>Birds crossed mountains effortlessly. Clouds drifted over kingdoms untouched by roads, rivers, or borders. The sky represented freedom, divinity, mystery, and power. Ancient civilizations filled their myths with flying gods, winged horses, dragons, and celestial chariots because the idea of flight felt supernatural — something beyond human reach.</p><p>And yet, generation after generation, people kept trying.</p><p>Some strapped feathers to their arms and leapt from towers. Others designed mechanical wings inspired by eagles. Inventors imagined flying ships centuries before technology could support them. Most attempts ended in failure, ridicule, or death.</p><p>But then, in the late 1700s, something extraordinary happened.</p><p>Humanity discovered that the sky did not need to be conquered with strength.</p><p>It could be entered gently.</p><p>Not through force.<br>Not through machinery.<br>But through heat.</p><p>That realization would ignite one of the most beautiful revolutions in human history: the birth of balloon flight.</p><h3>The World Before Flight</h3><p>To understand how shocking balloon flight was, you must imagine the world before it existed.</p><p>In the 18th century, people had never seen a human leave the ground intentionally and survive. The highest perspective most people would ever experience came from a church tower or a mountain. The heavens were unreachable territory.</p><p>This was the age of the Enlightenment — a period when Europe became obsessed with science, experimentation, and discovery. Philosophers challenged old beliefs. Scientists explored electricity, chemistry, astronomy, and physics. Across France and Britain, public demonstrations of scientific experiments became social spectacles.</p><p>People gathered in salons and royal courts to witness strange new inventions:</p><ul><li>electrical machines,</li><li>chemical reactions,</li><li>telescopes,</li><li>and mechanical automata.</li></ul><p>The impossible suddenly felt possible.</p><p>It was in this atmosphere of intellectual excitement that two paper manufacturers from France began experimenting with smoke.</p><h3>The Montgolfier Brothers</h3><p>The pioneers of balloon flight were two brothers from the town of Annonay in southern France:</p><ul><li>Joseph-Michel Montgolfier</li><li>Jacques-Étienne Montgolfier</li></ul><p><a href="https://en.wikipedia.org/wiki/Montgolfier_brothers">Joseph-Michel Montgolfier and Jacques-Étienne Montgolfier</a> were not formally trained physicists in the modern sense. Their family owned a successful paper manufacturing business, and much of their creativity came from practical experimentation rather than academic theory.</p><p>Joseph, the more imaginative of the two, was known for constantly inventing unusual mechanisms and ideas. He observed the world with intense curiosity.</p><p>According to popular accounts, one evening Joseph watched sparks and ash rise from a fire in his fireplace. He noticed that smoke seemed capable of lifting lightweight materials upward. Small pieces of paper danced above the flames as though carried by an invisible force.</p><p>He became convinced he had discovered a new substance — a mysterious gas capable of defying gravity.</p><p>He called it: <em>“Montgolfier Gas.”</em></p><p>Of course, we now know the truth: hot air rises because it is less dense than cooler surrounding air.</p><p>But science often advances through imperfect understanding. What mattered was not that Joseph misunderstood the mechanism.</p><p>What mattered was that he recognized the possibility.</p><h3>The First Experiments</h3><p>The brothers began privately testing small fabric and paper balloons.<br>At first, the experiments were modest:</p><ul><li>silk bags,</li><li>paper chambers,</li><li>lightweight cloth structures.</li></ul><p>Whenever heated air filled the interior, the balloons rose.<br>Again and again.</p><p>The brothers realized they had discovered something historic.<br>Soon they began constructing a much larger balloon made from:</p><ul><li>sackcloth,</li><li>paper lining,</li><li>rope reinforcements.</li></ul><p>The structure was enormous for its time — fragile, experimental, and unlike anything people had ever seen.</p><p>Then came the moment that would astonish France.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9MfX5vBf52nYKVuuzu22Q.jpeg" /></figure><h3>June 4, 1783 — Humanity Watches the Sky Change</h3><p>On June 4, 1783, the Montgolfier brothers organized a public demonstration in their hometown of Annonay, France.</p><p>A large crowd gathered.</p><p>Local officials, merchants, townspeople, and nobles stood watching the strange fabric sphere suspended above a fire pit. Beneath the balloon, workers burned straw and wool to generate thick hot smoke.</p><p>Slowly, the balloon began to move.<br>The fabric expanded.<br>The ropes strained.<br>And then — <br>it lifted off the ground.</p><p>The balloon rose into the sky before stunned spectators, climbing approximately 1,500 to 2,000 meters into the air and traveling over a mile before descending.</p><p>The audience reportedly erupted in disbelief.<br>Many had never imagined such a thing was physically possible.</p><p>Humanity had entered the sky for the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5NnecFbMhmC4gpA6kU8Ow.jpeg" /></figure><h3>Paris Becomes Obsessed With Balloon Fever</h3><p>News spread rapidly across France.</p><p>Soon, Paris became consumed by what historians later called: <em>“Balloonomania.”</em></p><p>Balloon-themed fashion appeared everywhere: Dresses, hats, paintings, furniture, decorations, even hairstyles inspired by balloons.</p><p>Scientists debated the future of air travel.</p><p>Could humans cross oceans through the air?<br>Could armies attack from above?<br>Could flight reshape civilization itself?</p><p>The French royal court demanded a demonstration.<br>And so the Montgolfier brothers traveled to Versailles.</p><h3>King Louis XVI and the Fear of Human Flight</h3><p>At the royal palace of <a href="https://en.wikipedia.org/wiki/Palace_of_Versailles">Palace of Versailles</a>, the brothers prepared a larger balloon for the attention of <a href="https://en.wikipedia.org/wiki/Louis_XVI">Louis XVI</a> and Queen <a href="https://en.wikipedia.org/wiki/Marie_Antoinette">Marie Antoinette</a>.</p><p>But a terrifying question emerged: Who would be the first passenger?</p><p>No one truly knew what would happen to a living creature in the sky.</p><p>People feared: Lack of breathable air, deadly altitude effects, violent crashes, fire or unknown atmospheric dangers.</p><p>The King initially proposed using condemned prisoners for the experiment. If they survived, they could earn freedom.</p><p>The idea reflected the enormous perceived risk.<br>But others objected strongly.</p><p>The first flight, they argued, should belong to courageous volunteers — not criminals.</p><p>Before risking human lives, they decided to test animals.</p><h3>The First Passengers in Aviation History</h3><p>On September 19, 1783, thousands gathered at Versailles to witness one of history’s strangest scientific experiments.</p><p>The passengers were: a sheep, a duck and a rooster.</p><p>The sheep, named <em>Montauciel</em> (“Climb-to-the-sky”), represented human physiology. Scientists believed its body might react similarly to a person’s.</p><p>The duck served as a control because ducks naturally fly at altitude.</p><p>The rooster represented a bird that normally remains near the ground.</p><p>Oddly enough, the logic was scientifically reasonable for the era.</p><p>The balloon launched successfully.</p><p>For approximately eight minutes, the animals floated through the air before landing safely.</p><p>The sheep survived.<br>The duck survived.<br>The rooster survived.</p><p>Human flight suddenly seemed possible.</p><h3>The Men Who Risked Everything</h3><p>Now came the final step.</p><p>Two men volunteered to enter history.</p><p>The first was:<br><a href="https://tr.wikipedia.org/wiki/Jean-Fran%C3%A7ois_Pil%C3%A2tre_de_Rozier">Jean-François Pilâtre de Rozier</a> — a daring science teacher and physicist fascinated by experimentation.</p><p>The second:<br><a href="https://en.wikipedia.org/wiki/Fran%C3%A7ois_Laurent_d%27Arlandes">François Laurent d’Arlandes</a> — an infantry officer willing to risk death for glory and discovery.</p><p>Their balloon was enormous:</p><ul><li>made from paper and fabric,</li><li>decorated in royal blue and gold,</li><li>suspended above a fire basket fueled by wood and straw.</li></ul><p>Unlike modern balloons, early flights required the passengers themselves to actively manage the fire mid-flight. They had to continuously feed fuel into the flames while airborne.</p><p>One mistake could ignite the balloon.<br>One gust of wind could destroy them.<br>One structural failure could send them falling into Paris.<br>Still, they climbed aboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*r_D2yGsIRWCCDvJt5ZlvNg.jpeg" /></figure><h3>November 21, 1783 — The First Human Flight</h3><p>On November 21, 1783, the balloon lifted into the skies above Paris.</p><p>For approximately 25 minutes, the two men floated freely above the city.</p><p>Below them: Streets, rooftops, churches, rivers, crowds of astonished citizens.</p><p>Above them:<br> only sky.</p><p>They traveled roughly 5.5 miles (about 9 kilometers), becoming the first humans in recorded history to achieve free flight.</p><p>Imagine the psychological impact of that moment.</p><p>For the first time ever, human beings looked down upon Earth from the open sky.</p><p>No mountain.<br>No tower.<br>No myth.</p><p>Real flight.</p><p>The age-old boundary between humanity and the heavens had finally been broken.</p><h3>The Danger Behind the Wonder</h3><p>Despite its beauty, early ballooning was incredibly dangerous.</p><p>The balloons: Burned easily, had limited steering, depended entirely on wind and frequently crashed.</p><p>Pilâtre de Rozier himself would later die attempting to cross the English Channel in a hybrid balloon experiment, becoming one of aviation’s first fatalities.</p><p>Yet the danger only increased public fascination.</p><p>Balloon ascents became grand public spectacles across Europe.</p><p>Crowds gathered by the thousands to witness launches. Scientists raced to improve designs. Adventurers dreamed of crossing continents through the air.</p><p>Humanity had discovered a new frontier.</p><h3>More Than Transportation</h3><p>The first balloons changed something deeper than travel.</p><p>They changed perspective.</p><p>For the first time, humans could observe: Landscapes from above, cities as patterns, rivers as systems and the Earth as something vast and interconnected.</p><p>Ballooning transformed science itself.</p><p>It helped inspire: Meteorology, atmospheric studies, aerial mapping, military reconnaissance and eventually powered aviation.</p><p>Without balloons, the dream of flight may have remained fantasy for much longer.</p><p>The Wright brothers would eventually master controlled powered flight more than a century later — but the psychological barrier had already been shattered in 1783.</p><p>The sky was no longer forbidden.</p><h3>The Beginning of a New Age</h3><p>What started with smoke rising from a fireplace became humanity’s first doorway into the heavens.</p><p>The Montgolfier brothers did not build airplanes.<br> They did not invent engines.<br> They did not conquer the skies with precision.</p><p>What they did was perhaps even more important:</p><p>They proved humans could leave the Earth.</p><p>And once humanity understood that flight was possible, there was no turning back.</p><p>The age of aviation had begun.</p><h3>Sources &amp; Historical References</h3><ul><li><a href="https://airandspace.si.edu/stories/editorial/presidential-writings-reveal-early-interest-ballooning">Smithsonian National Air and Space Museum — Early Balloon Flight</a></li><li><a href="https://www.fai.org/commission/cia">FAI Ballooning Commission</a></li><li><a href="https://www.britannica.com/biography/Montgolfier-brothers">Encyclopaedia Britannica — Montgolfier Brothers</a></li><li><a href="https://en.wikipedia.org/wiki/History_of_ballooning">History of Ballooning</a></li></ul><blockquote>As I explore the history of ballooning, I’m also working on its future. I built <strong>Hot Air Balloon Map</strong> to help pilots manage their flights and live tracking effortlessly. If you’re in the industry, I’d love for you to check it out and download it here:</blockquote><p><a href="https://firatgulec.com/hotairballoonmap?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=the-spark-of-flight&amp;utm_content=inline-link">Hot Air Balloon Map</a></p><p><em>(To be continued in Part 2: How balloons became tools of war and exploration…)</em></p><p><a href="https://medium.com/@firat-gulec/from-kings-to-cannons-the-golden-age-and-military-era-of-hot-air-balloons-part-2-bdec3242385d">From Kings to Cannons: The Golden Age and Military Era of Hot Air Balloons (Part-2)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8e12a414cd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Before Sunrise: Why I Built a Digital Companion for Hot Air Balloon Pilots]]></title>
            <link>https://medium.com/@firat-gulec/before-sunrise-why-i-built-a-digital-companion-for-hot-air-balloon-pilots-b249fbce859f?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b249fbce859f</guid>
            <category><![CDATA[travel-writing]]></category>
            <category><![CDATA[balloon-aviation]]></category>
            <category><![CDATA[aviation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Tue, 19 May 2026 05:09:43 GMT</pubDate>
            <atom:updated>2026-05-24T22:27:42.684Z</atom:updated>
            <content:encoded><![CDATA[<p>Flying a balloon is magical for passengers.<br> For pilots, it’s preparation, pressure, weather, timing, and responsibility.</p><p>It’s 4:10 AM in Cappadocia.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTeSVtqMpC3mck4fvSeNKQ.jpeg" /></figure><p>The valleys are still dark.<br> Most tourists are asleep.<br> The sky is silent.</p><p>But balloon pilots are already awake.</p><p>Because hot air ballooning is far more than the peaceful view people see in photos.</p><p>Weather conditions are checked.<br> Wind directions are analyzed again.<br> The crew prepares the equipment.<br> Vehicles start moving.<br> Burners are tested.</p><p>All of this happens before the first passenger even takes a picture.</p><p>From the outside, hot air ballooning looks effortless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K3YduG81x4ie20AQJAkmXA@2x.jpeg" /></figure><p>Quiet.<br> Smooth.<br> Almost dreamlike.</p><p>But pilots know the reality behind every flight:</p><p>Planning.<br> Timing.<br> Weather decisions.<br> Responsibility.<br> Experience.</p><p>Even when the sky looks calm, there is a lot happening behind the scenes.</p><p>I’ve always been passionate about both aviation and technology.</p><p>And after spending time around the ballooning world, I noticed something:</p><p>There are very few modern digital tools designed specifically for hot air balloon pilots.</p><p>Many existing systems feel outdated.<br> Some are difficult to use on mobile devices.<br> Others focus only on operations and forget the actual flying experience.</p><p>But ballooning is not just another aviation activity.</p><p>It’s something much more personal.</p><p>That’s why I started building my own app. Hot Air Balloon Map AI</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Ozod7mRkkfHYEf-8yJZCg.png" /></figure><p>I didn’t want to create just another map application.</p><p>I wanted to build something that could feel like a small digital companion for pilots during flight days.</p><p>So while designing the app, I focused on:</p><ul><li>simple and clean flight information,</li><li>an intuitive map experience,</li><li>easy mobile usability,</li><li>quick access during busy mornings,</li><li>and a more modern interface for pilots.</li></ul><p>Because during a flight, simplicity matters.</p><p>Pilots don’t need complicated screens.<br> They need information that is fast, clear, and easy to read.</p><p>Hot air ballooning is unique because technology and nature work together.</p><p>Flights are not controlled entirely by computers.</p><p>Pilots still rely on:</p><ul><li>reading the wind,</li><li>understanding altitude,</li><li>navigating valleys,</li><li>and making real-time decisions.</li></ul><p>Maybe that’s exactly why ballooning still feels magical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCv8DrORCrknWDaFuiY5QA.png" /></figure><p>One of the things I enjoyed most while building this app was realizing that technology can quietly support the people behind the experience.</p><p>Most people only see the colorful balloons in the sky.</p><p>But for pilots, every flight also represents:</p><ul><li>responsibility,</li><li>preparation,</li><li>teamwork,</li><li>and safety.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ot6jxOYlSaJnHjnCPYrRaw.png" /></figure><p>This is still only the beginning.</p><p>In the future, I’d love to expand the app with:</p><ul><li>advanced flight history,</li><li>weather integrations,</li><li>detailed route insights,</li><li>pilot-focused tools,</li><li>and smarter post-flight summaries.</li></ul><p>But the core idea will always stay the same:</p><blockquote><em>Make the pilot experience more modern, more intuitive, and more enjoyable.</em></blockquote><p>Every morning in Cappadocia, hundreds of people look up at the sky and capture unforgettable photos.</p><p>But sometimes, the most interesting story isn’t the one taking the photo.</p><p>It’s the pilot quietly guiding the balloon above the valleys before sunrise.</p><p>If you would like to explore the app, learn more about the project, or download it, you can visit the official website below:</p><p><a href="https://firatgulec.com/hotairballoonmap?utm_source=medium&amp;utm_medium=article&amp;utm_campaign=balloon-flight-planning&amp;utm_content=inline-link">Hot Air Balloon Map</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b249fbce859f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2 —  Bringing Your Server to Life | Setting Up Your Server (Raspberry Pi or Cloud VM)]]></title>
            <link>https://medium.com/@firat-gulec/part-2-bringing-your-server-to-life-setting-up-your-server-raspberry-pi-or-cloud-vm-6802031d8371?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6802031d8371</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 10:31:56 GMT</pubDate>
            <atom:updated>2026-01-17T10:31:56.960Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 2 — Bringing Your Server to Life | Setting Up Your Server (Raspberry Pi or Cloud VM)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fa_l_0WActhaWvu0" /><figcaption>Photo by <a href="https://unsplash.com/@grakozy?utm_source=medium&amp;utm_medium=referral">Greg Rakozy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the <strong>Introduction (Part 1)</strong>, we talked about the vision: building a modern, automated infrastructure completely under your control.</p><p>Now, it’s time to get our hands dirty.</p><p>In this part, we are going to build the heart of our project: the server itself. Whether you are working on a <strong>Raspberry Pi</strong> sitting on your desk or a <strong>Cloud VM</strong> rented from a provider like DigitalOcean, Hetzner, or AWS, the process is fundamentally the same.</p><p>Our goal is not just to install an operating system; it is to make it secure, up-to-date, and ready to host Docker containers.</p><p>If you are ready, let’s begin.</p><h3>1. Make Your Choice: Raspberry Pi or Cloud?</h3><p>If you’ve been following the series, you’ve probably already made your decision, but let’s do a quick recap:</p><ul><li><strong>Raspberry Pi:</strong> You have physical access, it runs on your home network, and the learning cost is essentially zero. However, you will need to configure your modem (port forwarding) to open it to the internet. Additionally, since a static IP address is usually required for reliable external access, there may be an extra cost depending on your internet service provider. Raspberry Pi is also an environmentally friendly solution due to its very low power consumption and is more than sufficient for small projects such as personal websites, blogs, or lightweight applications.</li><li><strong>Cloud VM:</strong> Comes with a Static IP, is instantly accessible from anywhere in the world, and isn’t affected by home power outages. However, it comes with a monthly cost.</li></ul><p>Whichever path you choose, we will be using <strong>Linux</strong> as our operating system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vPqYB9nQKlWs5J487esSrw.png" /></figure><h3>2. Operating System Installation</h3><h3>Option A: Raspberry Pi Setup</h3><p>For a server, the cleanest and most performant method is a “Headless” installation (without a monitor). We don’t want to waste system resources on a desktop interface.</p><ol><li>Download the <strong>Raspberry Pi Imager</strong>.</li><li><strong>OS Selection:</strong> Choose Raspberry Pi OS (other) -&gt; Raspberry Pi OS Lite (64-bit). (The Lite version has no GUI, which is perfect for servers).</li><li><strong>Settings (The Gear Icon):</strong> This is critical!</li></ol><ul><li>Set Hostname: myserver (or any name you prefer).</li><li><strong>Enable SSH.</strong></li><li>Set a username and password.</li><li>Configure your Wi-Fi settings (skip this if using Ethernet).</li></ul><p>Once the writing process is done, insert the SD card into the Pi and power it up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*HUtPoL1wmWip_IopfJGjIA.png" /><figcaption>Raspberry Pi Imager</figcaption></figure><h3>Option B: Cloud VM Setup (Detailed Guide)</h3><p>Using a Cloud Virtual Machine (VM) is one of the fastest and most reliable ways to publish your web application to the internet. Unlike a home server, a cloud VM comes with a public static IP address, high availability, and professional infrastructure managed by the provider.</p><p>Below is a step-by-step explanation of how to set up your first Cloud VM.</p><h3>1. Choose a Cloud Provider</h3><p>Popular and beginner-friendly cloud providers include:</p><ul><li><strong>DigitalOcean</strong> — Very simple UI, great for learning</li><li><strong>AWS (EC2)</strong> — Industry leader, highly scalable</li><li><strong>Google Cloud Compute Engine</strong></li><li><strong>Hetzner Cloud</strong> — Cost-effective, popular in Europe</li><li><strong>Azure Virtual Machines</strong></li></ul><blockquote><em>The core concepts are the same across all providers. Only the UI and naming differ (Droplet, Instance, VM).</em></blockquote><h3>2. Create a New Virtual Machine</h3><p>Once logged in to your cloud provider’s dashboard:</p><ul><li>Click <strong>Create → Droplet / Instance / Virtual Machine</strong></li><li>Choose <strong>Virtual Machine</strong> (not managed services like App Platform or Kubernetes for now)</li></ul><p>This gives you full control over the server and is ideal for learning Linux, Docker, and DevOps fundamentals.</p><h3>3. Select the Operating System</h3><p>Choose:</p><ul><li><strong>Ubuntu 22.04 LTS</strong> or <strong>Ubuntu 24.04 LTS</strong></li><li>Type: <strong>Ubuntu Server</strong></li></ul><blockquote>Avoid desktop versions. Server editions are lighter and more secure, as they run only the components required for server workloads. While Ubuntu Server is a common industry standard, I personally prefer Alpine Linux whenever possible. Alpine is extremely lightweight, security-focused, and widely adopted in modern development environments — especially in the container and DevOps world. Its minimal footprint, fast boot times, and strong security model make it an excellent choice for small to medium-scale projects and cloud-native applications.</blockquote><h3>4. Choose the Server Size (Resources)</h3><p>For a personal project or learning environment:</p><ul><li><strong>1 vCPU</strong></li><li><strong>1 GB RAM</strong></li><li><strong>25–30 GB SSD</strong></li></ul><p>This is more than enough for:</p><ul><li>Personal websites</li><li>Blogs</li><li>APIs</li><li>Dockerized apps</li><li>CI/CD experiments</li></ul><p>You can always <strong>scale up later</strong> without rebuilding everything.</p><h3>5. Select the Region (Data Center Location)</h3><p>Choose a region <strong>physically close to you</strong> or your target audience:</p><p>Examples:</p><ul><li><strong>Frankfurt / Amsterdam</strong> → Europe</li><li><strong>London</strong> → UK</li><li><strong>New York / NYC</strong> → North America</li><li><strong>Singapore</strong> → Asia</li></ul><p>Why this matters:</p><ul><li>Lower latency (faster response times)</li><li>Better user experience</li><li>Sometimes lower data transfer costs</li></ul><h3>6. Final Review &amp; Create</h3><p>Before clicking <strong>Create</strong>:</p><ul><li>OS: Ubuntu 22.04 / 24.04 LTS</li><li>Size: 1 vCPU / 1GB RAM</li><li>Region: Closest to you</li><li>Authentication: SSH key</li><li>Firewall: Enabled</li></ul><p>Once created, you’ll receive:</p><ul><li>A <strong>public static IP address</strong></li><li>Full root or sudo access</li></ul><p>Your server is now live and accessible from anywhere in the world 🌍</p><h3>3. First Connection (SSH)</h3><p>Our server is running. Now, we need to connect to it remotely. Open your Terminal (Mac/Linux) or PowerShell/PuTTY (Windows).</p><p><strong>For Raspberry Pi:</strong> You can find the Pi’s local IP address via your modem interface or by using a network scan tool.</p><p><strong>For Cloud:</strong> Use the Public IP address provided by your hosting provider.</p><p>Bash</p><pre>ssh username@YOUR_SERVER_IP</pre><p>After entering your password, you will see the famous command line prompt. Congratulations, you are in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*oEaPllLND52T0hSb4M9snA.png" /><figcaption>Terminal</figcaption></figure><p>4. Basic Updates and Preparation</p><p>The very first thing you should do on a fresh server is update the packages. This patches security vulnerabilities and ensures stability.</p><p>Bash</p><pre>sudo apt update &amp;&amp; sudo apt upgrade -y</pre><p>Depending on your internet speed, this may take a few minutes.</p><h3>5. Firewall &amp; Hardening</h3><p>Since we are opening our server to the internet (or local network), we need to lock the doors. In the Linux world, leaving the “root” user accessible or relying solely on passwords is risky.</p><h3>Step 1: Firewall (UFW) Configuration</h3><p>We will use <strong>UFW (Uncomplicated Firewall)</strong> on Ubuntu. We only want to open the ports we actually need:</p><ul><li><strong>22:</strong> For SSH connection (Crucial — don’t lock yourself out!)</li><li><strong>80:</strong> HTTP (For your website)</li><li><strong>443:</strong> HTTPS (For secure connections)</li></ul><p>Bash</p><pre>sudo ufw allow 22/tcp<br>sudo ufw allow 80/tcp<br>sudo ufw allow 443/tcp<br>sudo ufw enable</pre><h3>Step 2: Using SSH Keys</h3><p>Typing passwords is both insecure (vulnerable to Brute-force attacks) and bad for automation. You should copy the SSH key generated on your computer to your server.</p><p>Run this on your local computer (NOT inside the server):</p><p>Bash</p><pre>ssh-copy-id username@YOUR_SERVER_IP</pre><p>Once you confirm you can log in without a password, you can edit the /etc/ssh/sshd_config file on the server and set PasswordAuthentication no to increase your security to 100%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*FMxJcaxSPqHePDvxifEFMA.png" /><figcaption>ufw status</figcaption></figure><h3>Conclusion &amp; Next Steps</h3><p>Right now, you have an up-to-date, secure, and remotely accessible Linux server. This is the “concrete foundation” of the modern infrastructure we are building.</p><p>However, the server is currently “empty.” No applications are running on it yet.</p><p><strong>In Part 3, things get interesting:</strong> Next up is <strong>Docker</strong>. We won’t run our apps the old-fashioned way; we will use container architecture. Then, we will prepare our <strong>GitLab CI/CD</strong> pipeline to create an automation workflow where your code goes live the moment you “push” it.</p><p>Stay tuned, the real fun begins now!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6802031d8371" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1 — Let’s Build Your Own Home or Cloud Web Server Together]]></title>
            <link>https://medium.com/@firat-gulec/part-1-lets-build-your-own-home-or-cloud-web-server-together-08b1940ee4db?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/08b1940ee4db</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 18:02:50 GMT</pubDate>
            <atom:updated>2026-01-07T18:02:50.732Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1 — Let’s Build Your Own Home or Cloud Web Server Together</h3><p>Raspberry Pi · Cloud Infrastructure · DevOps Pipelines · Dockerized Deployments</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bUZ3tZeCXmSWwZB8" /><figcaption>Photo by <a href="https://unsplash.com/@vertex_800?utm_source=medium&amp;utm_medium=referral">Vertex Designs</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>Have you ever wanted to run your own web server — completely under your control — either at home or in the cloud? In this technical series, I will guide you step by step through building a modern, secure, fully automated web hosting environment using Raspberry Pi, Linux, Cloud VM providers, Docker, and DevOps CI/CD pipelines.</p><p>Whether you’re a beginner who wants to learn real-world infrastructure or an experienced engineer looking to create a hybrid home–cloud setup, this series will give you a complete blueprint you can follow.</p><h3>Why Am I Building My Own Server?</h3><p>For years, I’ve hosted personal projects, websites, and development environments across different platforms. But I wanted a solution that was:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7QNfh0m9MM2NsFulOEcMuA.png" /></figure><p><strong>Cost-effective</strong> (Raspberry Pi or cheap cloud VMs)<br><strong>Fully automated</strong> using CI/CD pipelines<br><strong>Containerized</strong> so environments are portable<br><strong>Resilient</strong>, with home server + cloud failover potential<br><strong>Educational</strong>, both for myself and others</p><p>Instead of relying on shared hosting or expensive managed platforms, I wanted to combine the simplicity of Raspberry Pi with the scalability of the cloud — while building everything with modern DevOps workflows.</p><p>This project became the foundation of this tutorial series.</p><p>I will focus on building automated failover capabilities, intelligent self-deploying workflows, and adaptive usage scenarios — all while ensuring the entire platform remains cost-effective and easily scalable. By evolving the system in this direction, I aim to create a modern infrastructure that can heal itself during failures, automatically expand during high traffic, and minimize operational costs, ultimately delivering a resilient and future-proof environment for personal projects and real-world applications.</p><h3>What We Are Going to Build</h3><p>Across this four-part series, we will create:<br><strong>✔ A home or cloud-based Linux server</strong><br>— running on Raspberry Pi or a free-tier cloud VM.</p><p><strong>✔ A secure remote-access environment</strong><br>— using SSH, firewall rules, and basic hardening.</p><p><strong>✔ A Dockerized web service infrastructure</strong><br>— where your website or application runs inside containers.</p><p><strong>✔ A GitLab CI/CD pipeline</strong><br>— automatically building, pushing, and deploying your web application directly to your server.</p><p><strong>✔ A complete “push-to-deploy” workflow</strong><br>— meaning: you push code → pipeline runs → Docker image updated → server deploys.</p><p>This setup is lightweight, modern, and can be used for personal websites, blogs, APIs, portfolio projects, or small production workloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wLrrEiGQgHUzBcTaSLrp8A.png" /><figcaption>flexibility explanation</figcaption></figure><h3>Home Server with Raspberry Pi:</h3><ul><li>Energy efficient</li><li>Extremely cheap</li><li>Fun to learn</li><li>Perfect for development or personal use</li></ul><h3>Cloud Server:</h3><ul><li>24/7 uptime</li><li>No dependency on home electricity or internet</li><li>Great for public-facing personal websites</li><li>Easy scaling</li></ul><p>In this series, you can choose either option — or even combine both for a hybrid architecture with failover.</p><h3>How the Series Will Be Structured</h3><p>This is <strong>Part 1</strong>, where I explain the vision, the architecture, and the roadmap.</p><p>Here’s what’s coming next:<br>🔹 Part 2 — Setting Up Your Server (Raspberry Pi or Cloud VM)<br>🔹 Part 3 — Preparing GitLab CI/CD and Your Web Environment<br>🔹 Part 4 — First Deployment: Running Your Pipeline and Going Live</p><p>Whether you’re hosting a personal site or planning future production projects, this foundation will give you full control, flexibility, and a powerful learning experience.</p><p>Stay tuned for Part 2, where we begin the hands-on setup!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=08b1940ee4db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring Website Content with Playwright and Nagios]]></title>
            <link>https://medium.com/@firat-gulec/monitoring-website-content-with-playwright-and-nagios-4842075a1f96?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4842075a1f96</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[nagios]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 17:42:19 GMT</pubDate>
            <atom:updated>2025-12-27T17:42:19.052Z</atom:updated>
            <content:encoded><![CDATA[<p>it’s very important to simply ensuring your users always see the latest updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bnNtU3SEBak5ofA4" /><figcaption>Photo by <a href="https://unsplash.com/@enka80?utm_source=medium&amp;utm_medium=referral">nine koepfer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Keeping a close eye on your website’s content is crucial, whether for uptime monitoring, regulatory compliance, or simply ensuring your users always see the latest updates. Traditionally, Nagios plugins focused on server availability or response times, but modern tools like Playwright allow us to perform <strong>end-to-end content checks</strong> automatically. In this article, we’ll explore how to build a custom Nagios plugin using Playwright inside Docker, capable of monitoring both text and element presence on your website.</p><h3>Why Playwright?</h3><p><a href="https://playwright.dev/">Fast and reliable end-to-end testing for modern web apps | Playwright</a></p><p>Playwright is a modern browser automation library that supports Chromium, Firefox, and WebKit. It allows for robust, end-to-end testing of web applications and provides features like:</p><ul><li>Cross-browser testing</li><li>Headless execution for CI/CD pipelines</li><li>Powerful selectors (getByText, locator, CSS, etc.)</li><li>JSON reporters for structured test results</li></ul><p>By combining Playwright with Nagios, we can move beyond simple HTTP checks and verify <strong>actual page content</strong>.</p><h3>Project Structure</h3><p>Here’s a clean directory layout for our monitoring setup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/332/1*4F23VxTQKSaZigbQGkD3gQ.png" /></figure><ul><li><strong>product/tests</strong> – Contains the Playwright test files.</li><li><strong>product/out</strong> – Stores JSON results and logs for Nagios.</li><li><strong>Dockerfile</strong> – Encapsulates the Playwright environment.</li><li><strong>run-tests.sh</strong> – Executes Playwright tests inside Docker.</li><li><strong>check_website_content.sh</strong> – Nagios plugin script that generates the test, runs Docker, parses results, and outputs Nagios-compatible status.</li></ul><h3>Setting Up Playwright</h3><p>Inside the product/tests folder:</p><pre>mkdir -p product/tests product/out<br>cd product/tests</pre><p>playwright.config.ts</p><pre>import { defineConfig } from &#39;@playwright/test&#39;;<br>export default defineConfig({<br>  reporter: [<br>    [&#39;json&#39;, { outputFile: &#39;/tests/out/product-result.json&#39; }]<br>  ],<br>  projects: [<br>    {<br>      name: &#39;chromium&#39;,<br>      use: { browserName: &#39;chromium&#39; },<br>    },<br>  ],<br>});<br>package.json<br>{<br>  &quot;devDependencies&quot;: {<br>    &quot;@playwright/test&quot;: &quot;1.56.1&quot;<br>  }<br>}</pre><p>product.spec.ts</p><pre>import { test, expect } from &#39;@playwright/test&#39;;<br>test(&#39;Firat Gulec Website Check&#39;, async ({ page }) =&gt; {<br>  await page.goto(&#39;www.webpagecheck.com&#39;);<br>  let buttonCheck = &#39;Skipped&#39;;<br>  let textCheck = &#39;Failed&#39;;<br>  let contentCheck = &#39;Skipped&#39;;<br>  let cssCheck = &#39;Skipped&#39;;<br>  try {<br>    await expect(page.getByText(&#39;checktext_script&#39;)).toBeVisible();<br>    textCheck = &#39;Passed&#39;;<br>  } catch {<br>    textCheck = &#39;Failed&#39;;<br>  }<br>  try {<br>    const body = await page.textContent(&#39;body&#39;);<br>    if (body &amp;&amp; body.includes(&quot;checktext_script&quot;)) {<br>      contentCheck = &#39;Passed&#39;;<br>    } else {<br>      contentCheck = &#39;Failed&#39;;<br>    }<br>  } catch {<br>    contentCheck = &#39;Failed&#39;;<br>  }<br>  console.log(&quot;RESULT_JSON:&quot; + JSON.stringify({<br>    buttonCheck,<br>    textCheck,<br>    contentCheck,<br>    cssCheck<br>  }));<br>});</pre><h3>Dockerizing Playwright</h3><p>We use Docker to ensure <strong>consistent, isolated test environments</strong>, avoiding dependency issues on the host machine.</p><p>Dockerfile</p><pre># FROM mcr.microsoft.com/playwright:v1.56.1-jammy<br># AMD64 Mimaride Playwright imaj<br>FROM --platform=linux/amd64 mcr.microsoft.com/playwright:v1.56.1-jammy<br>WORKDIR /tests<br># Package.json<br>COPY product/tests/package.json .<br># Install Dependencies<br>RUN npm install<br># Copy test files<br>COPY product/tests ./tests<br># Copy and set permissions for the test runner script<br>COPY run-tests.sh .<br>RUN chmod +x run-tests.sh<br>ENTRYPOINT [&quot;./run-tests.sh&quot;]<br>##<br>## To build the Docker image, use:  docker build -t playwright-runner .<br>## for x86_64 ## docker build --platform=linux/amd64 -t playwright-runner .</pre><p>You should check host mimari uname -m if your mimari is x86_64 you must use --platform=linux/amd64 command parameters docker build and in dockerfile from</p><p><a href="http://run-tests.sh/">run-tests.sh</a></p><pre>#!/bin/bash<br>set -e<br>echo &quot;Running Playwright tests...&quot;<br>cd /tests/tests<br># it creates JSON report in /tests/out by using playwright.config.ts<br>npx playwright test --config=playwright.config.ts<br>echo &quot;Done. JSON report created in /tests/out&quot;</pre><h3>Building the Nagios Plugin</h3><p>The check_website_content.sh script dynamically generates a Playwright test based on input parameters (URL, text, buttons, CSS selectors), runs the test in Docker, and parses the JSON result into <strong>Nagios-compatible status codes</strong>.</p><p>Key features:</p><ol><li><strong>Dynamic test generation</strong> — Supports button clicks, text visibility, CSS content checks, and full-body content searches.</li><li><strong>Dockerized execution</strong> — Runs Playwright tests in a container, ensuring environment consistency.</li><li><strong>Nagios integration</strong> — Outputs OK or CRITICAL with detailed information.</li></ol><p>check_website_content.sh</p><pre>#!/bin/bash<br># Default values<br>HELP=false<br>URL=&quot;&quot;<br>TEXT_SEARCH=&quot;&quot;<br>BUTTON_TEXT=&quot;&quot;<br>CSS_SELECTOR=&quot;&quot;<br>CSS_TEXT=&quot;&quot;<br>CONTENT_TEXT=&quot;&quot;<br>usage() {<br>    echo &quot;Usage:&quot;<br>    echo &quot;  $0 -w &lt;URL&gt; -t &lt;TEXT_SEARCH&gt; [-b &lt;BUTTON_TEXT&gt;] [-c &lt;CONTENT_TEXT&gt; -cc content] [-s &lt;CSS_TEXT&gt; -ss &lt;CSS_SELECTOR&gt;]&quot;<br>    echo &quot;&quot;<br>    echo &quot;Options:&quot;<br>    echo &quot;  -w      URL of the page to test&quot;<br>    echo &quot;  -t      Text to search using Playwright getByText()&quot;<br>    echo &quot;  -b      Optional button text to click first&quot;<br>    echo &quot;&quot;<br>    echo &quot;Content-based search (body text):&quot;<br>    echo &quot;  -c      Text to find inside full page body text&quot;<br>    echo &quot;  -cc     Enable content search mode (must be used with -cc then -c together)&quot;<br>    echo &quot;&quot;<br>    echo &quot;CSS selector search:&quot;<br>    echo &quot;  -s      Text to search inside items returned by CSS selector&quot;<br>    echo &quot;  -ss     CSS selector (must be used with -s)&quot;<br>    echo &quot;&quot;<br>    echo &quot;Examples:&quot;<br>    echo &quot;  ./script.sh -w &lt;https://site&gt; -t \\&quot;Start hier\\&quot; -cc -c \\&quot;Transavia\\&quot;&quot;<br>    echo &quot;  ./script.sh -w &lt;https://site&gt; -t \\&quot;Start\\&quot; -ss \\&quot;.faq-title\\&quot; -s \\&quot;Transavia\\&quot;&quot;<br>    exit 1<br>}<br># Parse parameters<br>while [[ $# -gt 0 ]]; do<br>    case &quot;$1&quot; in<br>        -w) URL=&quot;$2&quot;; shift 2 ;;<br>        -t) TEXT_SEARCH=&quot;$2&quot;; shift 2 ;;<br>        -b) BUTTON_TEXT=&quot;$2&quot;; shift 2 ;;<br>        -s) CSS_TEXT=&quot;$2&quot;; shift 2 ;;<br>        -ss) CSS_SELECTOR=&quot;$2&quot;; shift 2 ;;<br>        -c) CONTENT_TEXT=&quot;$2&quot;; shift 2 ;;<br>        -cc) CONTENT_MODE=&quot;enabled&quot;; shift 1 ;;<br>        -help|--help) usage ;;<br>        *) usage ;;<br>    esac<br>done<br># Mandatory checks<br>if [ -z &quot;$URL&quot; ] || [ -z &quot;$TEXT_SEARCH&quot; ]; then<br>    usage<br>fi<br># Validate CSS search pairing<br>if { [ ! -z &quot;$CSS_TEXT&quot; ] &amp;&amp; [ -z &quot;$CSS_SELECTOR&quot; ]; } || \\<br>   { [ -z &quot;$CSS_TEXT&quot; ] &amp;&amp; [ ! -z &quot;$CSS_SELECTOR&quot; ]; }; then<br>    echo &quot;ERROR: -s and -ss must be used together.&quot;<br>    exit 1<br>fi<br># Validate content search pairing<br>if { [ ! -z &quot;$CONTENT_TEXT&quot; ] &amp;&amp; [ &quot;$CONTENT_MODE&quot; != &quot;enabled&quot; ]; } || \\<br>   { [ -z &quot;$CONTENT_TEXT&quot; ] &amp;&amp; [ &quot;$CONTENT_MODE&quot; = &quot;enabled&quot; ]; }; then<br>    echo &quot;ERROR: -c and -cc must be used together.&quot;<br>    exit 1<br>fi<br># Paths<br>#<br>TEST_DIR=&quot;/usr/local/nagios/libexec/check_website_content/product&quot;<br>OUT_DIR=&quot;$TEST_DIR/out&quot;<br>SPEC_FILE=&quot;$TEST_DIR/tests/product.spec.ts&quot;<br>LOG_FILE=&quot;$OUT_DIR/playwright_log.txt&quot;<br>mkdir -p &quot;$OUT_DIR&quot;<br>mkdir -p &quot;$TEST_DIR/tests&quot;<br>rm -f &quot;$SPEC_FILE&quot; &quot;$LOG_FILE&quot;<br>###############################<br># Generate Playwright Test    #<br>###############################<br>cat &gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>import { test, expect } from &#39;@playwright/test&#39;;<br>test(&#39;Firat Gulec Website Check&#39;, async ({ page }) =&gt; {<br>  await page.goto(&#39;$URL&#39;);<br>  let buttonCheck = &#39;Skipped&#39;;<br>  let textCheck = &#39;Failed&#39;;<br>  let contentCheck = &#39;Skipped&#39;;<br>  let cssCheck = &#39;Skipped&#39;;<br>EOF<br># Button click<br>if [ ! -z &quot;$BUTTON_TEXT&quot; ]; then<br>cat &gt;&gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>  try {<br>    await page.getByRole(&#39;button&#39;, { name: /$BUTTON_TEXT/i }).click();<br>    buttonCheck = &#39;Passed&#39;;<br>  } catch {<br>    buttonCheck = &#39;Failed&#39;;<br>  }<br>EOF<br>fi<br># Standard getByText()<br>cat &gt;&gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>  try {<br>    await expect(page.getByText(&#39;$TEXT_SEARCH&#39;)).toBeVisible();<br>    textCheck = &#39;Passed&#39;;<br>  } catch {<br>    textCheck = &#39;Failed&#39;;<br>  }<br>EOF<br># Content-based search<br>if [ &quot;$CONTENT_MODE&quot; = &quot;enabled&quot; ]; then<br>cat &gt;&gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>  try {<br>    const body = await page.textContent(&#39;body&#39;);<br>    if (body &amp;&amp; body.includes(&quot;$CONTENT_TEXT&quot;)) {<br>      contentCheck = &#39;Passed&#39;;<br>    } else {<br>      contentCheck = &#39;Failed&#39;;<br>    }<br>  } catch {<br>    contentCheck = &#39;Failed&#39;;<br>  }<br>EOF<br>fi<br># CSS Selector Search<br>if [ ! -z &quot;$CSS_SELECTOR&quot; ]; then<br>cat &gt;&gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>  try {<br>    const list = await page.locator(&#39;$CSS_SELECTOR&#39;).allTextContents();<br>    if (list.some(x =&gt; x.includes(&quot;$CSS_TEXT&quot;))) {<br>      cssCheck = &#39;Passed&#39;;<br>    } else {<br>      cssCheck = &#39;Failed&#39;;<br>    }<br>  } catch {<br>    cssCheck = &#39;Failed&#39;;<br>  }<br>EOF<br>fi<br>cat &gt;&gt; &quot;$SPEC_FILE&quot; &lt;&lt;EOF<br>  console.log(&quot;RESULT_JSON:&quot; + JSON.stringify({<br>    buttonCheck,<br>    textCheck,<br>    contentCheck,<br>    cssCheck<br>  }));<br>});<br>EOF<br># echo &quot;INFO: Spec file created at $SPEC_FILE&quot;<br>###############################<br># Run Docker Runner           #<br>###############################<br>docker run --rm \\<br>    -v &quot;$TEST_DIR/tests:/tests/tests&quot; \\<br>    -v &quot;$OUT_DIR:/tests/out&quot; \\<br>    playwright-runner &gt; &quot;$LOG_FILE&quot; 2&gt;&amp;1<br>RAW_JSON=$(grep &quot;RESULT_JSON:&quot; &quot;$LOG_FILE&quot; | sed &#39;s/RESULT_JSON://&#39;)<br>if [ -z &quot;$RAW_JSON&quot; ]; then<br>    echo &quot;CRITICAL: No JSON output received!&quot;<br>    exit 2<br>fi<br># Extract all statuses<br>BUTTON_STATUS=$(echo &quot;$RAW_JSON&quot; | jq -r &#39;.buttonCheck&#39;)<br>TEXT_STATUS=$(echo &quot;$RAW_JSON&quot; | jq -r &#39;.textCheck&#39;)<br>CONTENT_STATUS=$(echo &quot;$RAW_JSON&quot; | jq -r &#39;.contentCheck&#39;)<br>CSS_STATUS=$(echo &quot;$RAW_JSON&quot; | jq -r &#39;.cssCheck&#39;)<br># Count totals<br>TOTAL=0<br>PASSED=0<br>FAILED=0<br>for item in &quot;$BUTTON_STATUS&quot; &quot;$TEXT_STATUS&quot; &quot;$CONTENT_STATUS&quot; &quot;$CSS_STATUS&quot;; do<br>    if [ &quot;$item&quot; = &quot;Skipped&quot; ]; then<br>        continue<br>    fi<br>    ((TOTAL++))<br>    if [ &quot;$item&quot; = &quot;Passed&quot; ]; then<br>        ((PASSED++))<br>    else<br>        ((FAILED++))<br>    fi<br>done<br>MSG=&quot;Website check: $PASSED/$TOTAL passed, $FAILED failed | Text: $TEXT_STATUS | Button: $BUTTON_STATUS | Content: $CONTENT_STATUS | CSS: $CSS_STATUS&quot;<br>if [ &quot;$FAILED&quot; -gt 0 ]; then<br>    echo &quot;CRITICAL: $MSG&quot;<br>    exit 2<br>else<br>    echo &quot;OK: $MSG&quot;<br>    exit 0<br>fi</pre><h3>Running the Plugin</h3><p>Example usage:</p><pre>./check_website_content.sh -w &quot;&lt;https://www.firatgulec.com&gt;&quot; -t &quot;Firat Gulec&quot; -cc -c &quot;Hot Air Balloon Map&quot;<br>OK: Website check: 2/2 passed, 0 failed | Text: Passed | Button: Skipped | Content: Passed | CSS: Skipped</pre><ul><li>Checks that the page contains “Firat Gulec”.</li><li>Optionally clicks a button if provided.</li><li>Verifies that body content includes “Hot Air Balloon Map”.</li><li>Outputs status for Nagios.</li></ul><h3>Adding the Plugin to Nagios Using NConf</h3><p>After creating the Playwright-based content monitoring plugin, the next step is to integrate it into Nagios so it can run as part of your regular checks. If you’re using <strong>NConf</strong>, the web-based configuration tool for Nagios, the process becomes much easier and more structured.</p><p>Below is a step-by-step guide explaining how to add the new plugin and create a Nagios service using NConf.</p><h3>1. Place the Plugin in Nagios libexec</h3><p>First, copy the plugin script into the Nagios libexec directory (or your custom plugin folder):</p><pre>sudo cp check_website_content.sh /usr/local/nagios/libexec/<br>sudo chmod +x /usr/local/nagios/libexec/check_website_content.sh</pre><p>If you followed the earlier structure, your Playwright test folder should be here:</p><pre>/usr/local/nagios/libexec/check_website_content/product</pre><p>This directory needs proper permissions:<br>Permissions and volume mounts are critical to make Docker writable for Nagios:</p><pre>sudo chown -R nagios:nagios /usr/local/nagios/libexec/check_website_content/product<br>sudo chmod -R 755 /usr/local/nagios/libexec/check_website_content/product</pre><ul><li>for container rights</li></ul><pre>sudo chmod -R 777 /usr/local/nagios/libexec/check_website_content/product/out<br>sudo chmod -R 777 /usr/local/nagios/libexec/check_website_content/product/tests</pre><h3>2. Define a Command in NConf</h3><p>Open <strong>NConf Web UI</strong> and follow these steps:</p><h4>➤ Navigate to <strong>“Advanced » Commands”</strong></h4><h4>➤ Click “Add”</h4><h4>➤ Fill in the command details:</h4><ul><li><strong>Name: </strong>check_website_content</li><li><strong>Command line:</strong></li></ul><p>$USER1$/check_website_content.sh -w $ARG1$ -t $ARG2$ -b $ARG3$ -cc -c $ARG4$ -ss -s $ARG5$</p><p>This structure allows flexible arguments for URL, visible text, button clicks, content mode, CSS selector, and CSS text.</p><pre>root@PCFIRAT:/FG-Script/playwright# ./check_website_content.sh -w &quot;https://firatgulec.com&quot; -t &quot;Ballon&quot; -c &quot;Hot Air Balloon&quot;<br>ERROR: -c and --cc must be used together.<br>root@PCFIRAT:/FG-Script/playwright# ./check_website_content.sh -help<br>Usage:<br>  ./check_website_content.sh -w &lt;URL&gt; -t &lt;TEXT_SEARCH&gt; [-b &lt;BUTTON_TEXT&gt;] [-c &lt;CONTENT_TEXT&gt; --cc content] [-s &lt;CSS_TEXT&gt; --ss &lt;CSS_SELECTOR&gt;]<br><br>Options:<br>  -w        URL of the page to test<br>  -t        Text to search using Playwright getByText()<br>  -b        Optional button text to click first<br><br>Content-based search (body text):<br>  -c        Text to find inside full page body text<br>  --cc      Enable content search mode (must be used with --cc then -c together)<br><br>CSS selector search:<br>  -s        Text to search inside items returned by CSS selector<br>  --ss      CSS selector (must be used with -s)<br><br>Examples:<br>  ./script.sh -w https://site -t &quot;TEST&quot; --cc -c &quot;TestTEXT&quot;<br>  ./script.sh -w https://site -t &quot;TEST&quot; --ss &quot;.faq-title&quot; -s &quot;TestTEXT&quot;<br><br>root@PCFIRAT:/FG-Script/playwright#</pre><h4>➤ Press Submit and Save.</h4><h3>3. Create a Service Using the Command</h3><p>Now that the command exists, we can assign it to a host or host group.</p><h4>➤ Go to <strong>“Basic » Services”</strong></h4><h4>➤ Click “Add Service”</h4><p>Fill in the following:</p><ul><li><strong>Service Name: </strong>Website Content Check</li><li><strong>Check Command: </strong>check_website_content</li></ul><p>After selecting the command, <strong>argument fields (ARG1–ARG7)</strong> will appear.</p><h3>Example Arguments</h3><p>ARG Value Description ARG1 https://www.firatgulec.com Website URL ARG2 Firat Gulec Text to check via getByText() ARG3 Agree Button text (optional) ARG4 Hot Air Balloon Map Text to find in body (optional)</p><p>If a parameter is not needed (e.g., no CSS checking), simply put: noneor leave the argument empty (NConf allows empty args depending on your config).</p><h3>4. Assign to a Host</h3><p>Under <strong>“Assign to hosts”</strong>, select:</p><p>Specific host<br>Or a host group like: web-servers</p><p>Using NConf makes it much easier to manage custom Nagios plugins, especially when they require multiple arguments. Your Playwright-powered plugin becomes a flexible, powerful website monitoring tool that can be deployed across dozens of hosts without manually editing configuration files.</p><h3>Conclusion</h3><p>Combining <strong>Playwright</strong> with <strong>Nagios</strong> provides a modern, reliable way to monitor actual website content, not just uptime. By containerizing your tests, dynamically generating scripts, and integrating structured JSON output, you can create a scalable, automated monitoring system that catches issues before your users do.</p><p>This approach is flexible and can be adapted for almost any website or web application scenario, giving DevOps teams the visibility they need into site content integrity.</p><p>Feel free to check out the scripts on <a href="https://github.com/Firat-Gulec/CheckWebsiteContent-Playwright">GitHub</a> and contribute your improvements or suggestions. Happy testing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4842075a1f96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sending Nagios Alerts to Microsoft Teams Without Webhooks]]></title>
            <link>https://medium.com/@firat-gulec/sending-nagios-alerts-to-microsoft-teams-without-webhooks-1d70b78a5b3f?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d70b78a5b3f</guid>
            <category><![CDATA[nagios]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[microsoft-teams]]></category>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Sat, 06 Dec 2025 17:06:40 GMT</pubDate>
            <atom:updated>2025-12-06T17:06:40.821Z</atom:updated>
            <content:encoded><![CDATA[<p>A Modern PowerShell &amp; App Registration Approach for Nagios</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y6TyFW68wapcXdlo" /><figcaption>Photo by <a href="https://unsplash.com/@edhardie?utm_source=medium&amp;utm_medium=referral">Ed Hardie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>Nagios has long been the backbone of infrastructure monitoring. However, as teams increasingly rely on real-time communication platforms like <strong>Microsoft Teams</strong>, classic email notifications often fall short. Many organizations hesitate to use <strong>incoming webhooks</strong> due to security restrictions, auditing concerns, or strict governance policies.</p><p>In my case, we needed Nagios to send alerts directly to Teams <strong>without using webhook URLs</strong>. Instead, we wanted a secure, Azure AD-based method using <strong>App Registration + Microsoft Graph API</strong>.</p><p>To achieve this, I created two PowerShell scripts:</p><ul><li>One sends Nagios alerts to a Teams Channel</li><li>One sends Nagios alerts to a Teams Chat</li></ul><p>In this article, I will walk you through:</p><ol><li><strong>Why</strong> we chose to avoid webhooks</li><li><strong>What you need in Azure Portal</strong> and how to configure it</li><li><strong>The PowerShell scripts</strong> and how they work</li><li>Requirements for sending messages to channels and chats</li><li>How to integrate the scripts into <strong>Nagios using NConf<br></strong>Let’s begin.</li></ol><h3>Why Avoid Using Webhooks?</h3><p>While Teams Incoming Webhooks are simple, they come with limitations:</p><ul><li>Webhook URLs must be exposed in scripts or environment variables</li><li>Limited auditing — webhook actions don’t appear in Azure AD sign-in logs</li><li>Hard to rotate or restrict programmatically</li><li>Some enterprise security policies completely block webhook usage</li><li>No conditional access controls</li></ul><p>By instead using an <strong>App Registration + Microsoft Graph</strong>, we gain:</p><ul><li>Centralized Azure AD authentication</li><li>Conditional Access support</li><li>Token expiration and refresh control</li><li>Logging of every API call in Azure</li><li>Secure permissions management</li><li>No public URLs stored anywhere</li></ul><p>For enterprises, this is a massive win.</p><h3>Azure Portal Requirements (Step-by-Step)</h3><p>To send Teams alerts using Graph API, we need:</p><h3>1. Azure App Registration</h3><p>Go to: <strong>Azure Portal → Azure Active Directory → App Registrations → New Registration</strong></p><p>Give it a name, e.g.: <em>NagiosTeamsIntegration<br></em>Choose:</p><ul><li>Supported account type: <em>Single Tenant</em> (recommended)</li></ul><p>After creation, note:</p><ul><li><strong>Application (client) ID</strong></li><li><strong>Directory (tenant) ID</strong></li></ul><p>You’ll need them in the script.</p><h3>2. Create a Client Secret</h3><p>Under the App panel:<br><strong>Certificates &amp; Secrets → New Client Secret → Add<br></strong>Save the secret <strong>securely</strong> — you will need it in your PowerShell scripts.</p><h3>3. API Permissions</h3><p>We need Microsoft Graph delegated permissions:<br>For <strong>Teams Channel Messages</strong>:</p><ul><li>ChannelMessage.Send</li><li>Group.ReadWrite.All</li></ul><p>For <strong>Teams Chat Messages</strong>:</p><ul><li>Chat.ReadWrite</li><li>ChatMessage.Send</li><li>User.Read</li></ul><p>After adding these permissions: Click <strong>Grant admin consent<br></strong>Without this, your scripts will not authenticate properly.</p><h3>PowerShell Scripts Explained</h3><p>You mentioned two scripts — one for Teams <strong>Channel</strong>, one for <strong>Chat</strong>.<br>Both authenticate using:</p><pre>client_id<br>client_secret<br>tenant_id</pre><p>Then they retrieve an access token from:&lt;https://login.microsoftonline.com/$tenant_id/oauth2/v2.0/token&gt;</p><p>And send the formatted Nagios alert to Microsoft Graph using:</p><ul><li>/teams/{teamId}/channels/{channelId}/messages</li><li>/chats/{chatId}/messages</li></ul><h3>Channel Script Requirements</h3><p>You must know: Teams <strong>ID, </strong>Channel <strong>ID<br></strong>These can be retrieved using Graph Explorer or PowerShell.</p><h3>Chat Script Requirements</h3><p>You must know:</p><ul><li>The chat’s <strong>ID</strong>, or</li><li>The user IDs in a 1:1 or group chat</li></ul><p>The script then formats the Nagios alert:<br>Host name, Service description, Status, Time, Additional info and sends it to Teams.</p><h3>How the Scripts Work (Technical Explanation)</h3><ol><li>Nagios executes the script using command definitions.</li><li>The PowerShell script retrieves an OAuth2 token from Azure AD.</li><li>The message body is created using JSON:</li></ol><pre>{<br>  &quot;body&quot;: {<br>     &quot;content&quot;: &quot;Nagios Alert: HOST/SERVICE STATUS...&quot;<br>  }<br>}</pre><ol><li>Script sends the data using Invoke-RestMethod to Graph API.</li><li>Microsoft Teams receives and displays the alert.<br>This creates a secure, scalable, webhook-free messaging pipeline.<br>NagiosTeamsChatNotifier.ps1</li></ol><pre>#Send Teams Chat<br>param(<br>        [string]$HOSTNAME,<br>        [string]$SERVICEDESC,<br>        [string]$SERVICESTATE,<br>        [string]$OUTPUT<br>)<br>$tenantId = &quot;xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx&quot;<br>$clientId = &quot;xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx&quot;<br>$scopes = &quot;offline_access Chat.ReadWrite User.Read&quot;<br>$clientSecret = &quot;xxxxx~xxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxx&quot;<br>$tokenFile  = &quot;/usr/local/nagios/libexec/.nagios_graph_refresh&quot;<br>$chatId = &quot;19:meeting_xxxxxxxxxxxxxxxxxxxxxxxx@thread.v2&quot;<br># ---------- Functions ----------<br>function Save-RefreshToken($refreshToken, $path) {<br>    [System.IO.File]::WriteAllText($path, $refreshToken)<br>     #sudo chown nagios:nagios $path<br>     #sudo chmod 600 $path<br>}<br>function Load-RefreshToken($path) {<br>    if (-not (Test-Path $path)) { return $null }<br>    return Get-Content -Path $path -Raw<br>}<br>function Get-Token-By-Refresh($refreshToken) {<br>    $resp = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token&gt;&quot; -Body @{<br>        client_id    = $clientId<br>        grant_type   = &quot;refresh_token&quot;<br>        refresh_token= $refreshToken<br>        scope        = $scopes<br>    } -ErrorAction Stop<br>    return $resp<br>}<br>function Do-DeviceCodeFlow() {<br>    $deviceCodeResponse = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/devicecode&gt;&quot; -Body @{<br>        client_id = $clientId<br>        scope     = $scopes<br>    }<br>    Write-Host $deviceCodeResponse.message -ForegroundColor Yellow<br>    $accessToken = $null<br>    $interval = [int]$deviceCodeResponse.interval<br>    $expires_in = [int]$deviceCodeResponse.expires_in<br>    $start = Get-Date<br>    while (-not $accessToken) {<br>        Start-Sleep -Seconds $interval<br>        try {<br>            $tokenResponse = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token&gt;&quot; -Body @{<br>                grant_type  = &quot;urn:ietf:params:oauth:grant-type:device_code&quot;<br>                client_id   = $clientId<br>                device_code = $deviceCodeResponse.device_code<br>            } -ErrorAction Stop<br>            if ($tokenResponse.access_token) {<br>                return $tokenResponse<br>            }<br>        } catch {<br>            # authorization_pending or slow_down<br>            if ((Get-Date) -gt $start.AddSeconds($expires_in)) {<br>                throw &quot;Device code timeout..&quot;<br>            }<br>        }<br>    }<br>}<br># ---------- Get Token ----------<br>try {<br>    $saved = Load-RefreshToken -path $tokenFile<br>    if ($saved) {<br>        Write-Host &quot;Saved refresh token found, I will try refreshing...&quot; -ForegroundColor Cyan<br>        try {<br>            $tokenResp = Get-Token-By-Refresh -refreshToken $saved<br>        } catch {<br>            Write-Warning &quot;Could not get token with Refresh: $_. Will fallback to device code.&quot;<br>            $tokenResp = $null<br>        }<br>    } else {<br>        $tokenResp = $null<br>    }<br>    # 2) refresh is not working get refresh_token by device_code (Refresh Error)<br>    if (-not $tokenResp) {<br>        Write-Host &quot;You need to log in with your device code...&quot; -ForegroundColor Yellow<br>        $tokenResp = Do-DeviceCodeFlow<br>        # device code response&#39;s refresh_token (offline_access scope)<br>        if (-not $tokenResp.refresh_token) {<br>            throw &quot;No refresh_token was received as a result of the device flow. Check the offline_access scope and application permissions.&quot;<br>        }<br>        # Save<br>        Save-RefreshToken -refreshToken $tokenResp.refresh_token -path $tokenFile<br>        Write-Host &quot;Refresh token saved: $tokenFile&quot; -ForegroundColor Green<br>    }<br>    $accessToken = $tokenResp.access_token<br>    # If tokenResp has new refresh_token (rotation), It&#39;ll be save<br>    if ($tokenResp.refresh_token -and $tokenResp.refresh_token -ne $saved) {<br>        Save-RefreshToken -refreshToken $tokenResp.refresh_token -path $tokenFile<br>        Write-Host &quot;Refresh token updated.&quot; -ForegroundColor Green<br>    }<br># ---------- Send message ---------- #<br>$time = Get-Date -Format &#39;u&#39;<br># Select Icons and colors <br>switch ($SERVICESTATE) {<br>    &quot;OK&quot; {<br>        $icon = &quot;&amp;#x2705;&quot;<br>        $color = &quot;#28a745&quot;  # Green<br>    }<br>    &quot;WARNING&quot; {<br>        $icon = &quot;&amp;#x26A0;&amp;#xFE0F;&quot;<br>        $color = &quot;#ffc107&quot;  # Yellow<br>    }<br>    &quot;CRITICAL&quot; {<br>        $icon = &quot;&amp;#x1F6A8;&quot;<br>        $color = &quot;#dc3545&quot;  # Red<br>    }<br>    default {<br>        $icon = &quot;&amp;#x1F4AC;&quot;<br>        $color = &quot;#6c757d&quot;  # Gray<br>    }<br>}<br># HTML content<br>$htmlContent = @&quot;<br>&lt;div style=&#39;font-family:Segoe UI, Arial, sans-serif; padding:12px; border-left:5px solid $color; background:#f9f9f9; border-radius:6px;&#39;&gt;<br>  &lt;h2 style=&#39;margin-top:0; color:$color;&#39;&gt;$icon Nagios Alert - $SERVICESTATE&lt;/h2&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Host:&lt;/b&gt; $HOSTNAME&lt;/p&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Service:&lt;/b&gt; $SERVICEDESC&lt;/p&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Output:&lt;/b&gt; $OUTPUT&lt;/p&gt;<br>  &lt;p style=&#39;margin-top:10px; font-size:12px; color:#777;&#39;&gt;⏰ $time&lt;/p&gt;<br>&lt;/div&gt;<br>&quot;@<br># Teams JSON body<br>$messageBody = @{<br>    body = @{<br>        contentType = &quot;html&quot;<br>        content = $htmlContent<br>    }<br>} | ConvertTo-Json -Depth 4<br>    $resp = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://graph.microsoft.com/v1.0/chats/$chatId/messages&gt;&quot; `<br>        -Headers @{ Authorization = &quot;Bearer $accessToken&quot;; &quot;Content-Type&quot; = &quot;application/json&quot; } `<br>        -Body $messageBody -ErrorAction Stop<br>    Write-Host &quot;Message has been sent. ID: $($resp.id)&quot; -ForegroundColor Green<br>} catch {<br>    Write-Error &quot;Error: $_&quot;<br>}</pre><p>NagiosTeamsChannelNotifier.ps1</p><pre># Send Teams Channel<br>param(<br>        [string]$HOSTNAME,<br>        [string]$SERVICEDESC,<br>        [string]$SERVICESTATE,<br>        [string]$OUTPUT<br>)<br>$tenantId = &quot;xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx&quot;<br>$clientId = &quot;xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx&quot;<br>$scopes = &quot;offline_access Chat.ReadWrite User.Read&quot;<br>$clientSecret = &quot;xxxxxxxx~xxxxxxxxx-xxxxxxxxxxxxxxxxxxx&quot;<br>$tokenFile  = &quot;/usr/local/nagios/libexec/.nagios_graph_refresh&quot;<br># Teams Channel<br>$teamId    = &quot;xxxxxx-xxxxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx&quot;<br>$channelId = &quot;19:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@thread.tacv2&quot;<br># ---------- Functions ----------<br>function Save-RefreshToken($refreshToken, $path) {<br>    [System.IO.File]::WriteAllText($path, $refreshToken)<br>     #sudo chown nagios:nagios $path<br>     #sudo chmod 600 $path<br>}<br>function Load-RefreshToken($path) {<br>    if (-not (Test-Path $path)) { return $null }<br>    return Get-Content -Path $path -Raw<br>}<br>function Get-Token-By-Refresh($refreshToken) {<br>    $resp = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token&gt;&quot; -Body @{<br>        client_id    = $clientId<br>        grant_type   = &quot;refresh_token&quot;<br>        refresh_token= $refreshToken<br>        scope        = $scopes<br>    } -ErrorAction Stop<br>    return $resp<br>}<br>function Do-DeviceCodeFlow() {<br>    $deviceCodeResponse = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/devicecode&gt;&quot; -Body @{<br>        client_id = $clientId<br>        scope     = $scopes<br>    }<br>    Write-Host $deviceCodeResponse.message -ForegroundColor Yellow<br>    $accessToken = $null<br>    $interval = [int]$deviceCodeResponse.interval<br>    $expires_in = [int]$deviceCodeResponse.expires_in<br>    $start = Get-Date<br>    while (-not $accessToken) {<br>        Start-Sleep -Seconds $interval<br>        try {<br>            $tokenResponse = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://login.microsoftonline.com/$tenantId/oauth2/v2.0/token&gt;&quot; -Body @{<br>                grant_type  = &quot;urn:ietf:params:oauth:grant-type:device_code&quot;<br>                client_id   = $clientId<br>                device_code = $deviceCodeResponse.device_code<br>            } -ErrorAction Stop<br>            if ($tokenResponse.access_token) {<br>                return $tokenResponse<br>            }<br>        } catch {<br>            # authorization_pending or slow_down<br>            if ((Get-Date) -gt $start.AddSeconds($expires_in)) {<br>                throw &quot;Device code timeout..&quot;<br>            }<br>        }<br>    }<br>}<br># ---------- Get Token ----------<br>try {<br>    $saved = Load-RefreshToken -path $tokenFile<br>    if ($saved) {<br>        Write-Host &quot;Saved refresh token found, I will try refreshing...&quot; -ForegroundColor Cyan<br>        try {<br>            $tokenResp = Get-Token-By-Refresh -refreshToken $saved<br>        } catch {<br>            Write-Warning &quot;Could not get token with Refresh: $_. Will fallback to device code.&quot;<br>            $tokenResp = $null<br>        }<br>    } else {<br>        $tokenResp = $null<br>    }<br>    # 2) refresh is not working get refresh_token by device_code (Refresh Error)<br>    if (-not $tokenResp) {<br>        Write-Host &quot;You need to log in with your device code...&quot; -ForegroundColor Yellow<br>        $tokenResp = Do-DeviceCodeFlow<br>        # device code response&#39;s refresh_token (offline_access scope)<br>        if (-not $tokenResp.refresh_token) {<br>            throw &quot;No refresh_token was received as a result of the device flow. Check the offline_access scope and application permissions.&quot;<br>        }<br>        # Save<br>        Save-RefreshToken -refreshToken $tokenResp.refresh_token -path $tokenFile<br>        Write-Host &quot;Refresh token saved: $tokenFile&quot; -ForegroundColor Green<br>    }<br>    $accessToken = $tokenResp.access_token<br>    # If tokenResp has new refresh_token (rotation), It&#39;ll be save<br>    if ($tokenResp.refresh_token -and $tokenResp.refresh_token -ne $saved) {<br>        Save-RefreshToken -refreshToken $tokenResp.refresh_token -path $tokenFile<br>        Write-Host &quot;Refresh token updated.&quot; -ForegroundColor Green<br>    }<br># ---------- Send message ---------- #<br>$time = Get-Date -Format &#39;u&#39;<br># Select colors and icons<br>switch ($SERVICESTATE) {<br>    &quot;OK&quot; {<br>        $icon = &quot;&amp;#x2705;&quot;<br>        $color = &quot;#28a745&quot;  # Green<br>    }<br>    &quot;WARNING&quot; {<br>        $icon = &quot;&amp;#x26A0;&amp;#xFE0F;&quot;<br>        $color = &quot;#ffc107&quot;  # Yellow<br>    }<br>    &quot;CRITICAL&quot; {<br>        $icon = &quot;&amp;#x1F6A8;&quot;<br>        $color = &quot;#dc3545&quot;  # Red<br>    }<br>    default {<br>        $icon = &quot;&amp;#x1F4AC;&quot;<br>        $color = &quot;#6c757d&quot;  # Gray<br>    }<br>}<br># HTML content<br>$htmlContent = @&quot;<br>&lt;div style=&#39;font-family:Segoe UI, Arial, sans-serif; padding:12px; border-left:5px solid $color; background:#f9f9f9; border-radius:6px;&#39;&gt;<br>  &lt;h2 style=&#39;margin-top:0; color:$color;&#39;&gt;$icon Nagios Alert - $SERVICESTATE&lt;/h2&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Host:&lt;/b&gt; $HOSTNAME&lt;/p&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Service:&lt;/b&gt; $SERVICEDESC&lt;/p&gt;<br>  &lt;p style=&#39;margin:6px 0;&#39;&gt;&lt;b&gt;Output:&lt;/b&gt; $OUTPUT&lt;/p&gt;<br>  &lt;p style=&#39;margin-top:10px; font-size:12px; color:#777;&#39;&gt;⏰ $time&lt;/p&gt;<br>&lt;/div&gt;<br>&quot;@<br># Teams JSON body<br>$messageBody = @{<br>    body = @{<br>        contentType = &quot;html&quot;<br>        content = $htmlContent<br>    }<br>} | ConvertTo-Json -Depth 4<br>    $resp = Invoke-RestMethod -Method Post -Uri &quot;&lt;https://graph.microsoft.com/v1.0/teams/$teamId/channels/$channelId/messages&gt;&quot; `<br>        -Headers @{ Authorization = &quot;Bearer $accessToken&quot;; &quot;Content-Type&quot; = &quot;application/json&quot; } `<br>        -Body $messageBody -ErrorAction Stop<br>    Write-Host &quot;Message has been sent. ID: $($resp.id)&quot; -ForegroundColor Green<br>} catch {<br>    Write-Error &quot;Error: $_&quot;<br>}</pre><h3>Integrating with Nagios via NConf</h3><p>Now that the scripts work, let’s integrate them into Nagios.</p><h3>Step 1: Create a Nagios Command in NConf</h3><p>Go to: <strong>NConf → Commands → Add Command<br></strong>For host alerts:</p><pre>/usr/bin/pwsh /usr/local/nagios/scripts/send-teams-host.ps1 \\<br>  -HostName &quot;$HOSTNAME$&quot; \\<br>  -HostState &quot;$HOSTSTATE$&quot; \\<br>  -Output &quot;$HOSTOUTPUT$&quot;</pre><p>For service alerts:</p><pre>/usr/bin/pwsh /usr/local/nagios/scripts/send-teams-service.ps1 \\<br>  -HostName &quot;$HOSTNAME$&quot; \\<br>  -ServiceName &quot;$SERVICEDESC$&quot; \\<br>  -ServiceState &quot;$SERVICESTATE$&quot; \\<br>  -Output &quot;$SERVICEOUTPUT$&quot;</pre><p>Save the commands.</p><h3>Step 2: Create a Contact in NConf</h3><p>Go to: <strong>NConf → Contacts → Add Contact</strong></p><p>Create a contact named:<em> Teams_Notification</em>s<br>Set notification methods to the commands you created.</p><h3>Step 3: Attach Contact to Contactgroup</h3><p>Create a new group:<em> teams-notification-grou</em>p<br>Add the contact to this group.</p><h3>Step 4: Assign Contactgroup to Hosts/Services</h3><p>Under:</p><ul><li>Host templates</li><li>Service templates</li></ul><p>Add the contact group so all alerts send to Teams automatically.<br>That’s it.</p><p>Feel free to check out the scripts on <a href="https://github.com/Firat-Gulec/NagiosTeamsNotifier">GitHub</a> and contribute your improvements or suggestions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d70b78a5b3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Affordable Cloud in 2025]]></title>
            <link>https://medium.com/@firat-gulec/affordable-cloud-in-2025-4082c00446e0?source=rss-7d2e2e2eae1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4082c00446e0</guid>
            <dc:creator><![CDATA[Firat Gulec]]></dc:creator>
            <pubDate>Thu, 04 Sep 2025 22:08:21 GMT</pubDate>
            <atom:updated>2025-09-04T22:11:01.306Z</atom:updated>
            <content:encoded><![CDATA[<p>Hetzner • DigitalOcean • AWS • Cloudflare • Azure Compared</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Men2VOGhKf-3JEPz" /><figcaption>Photo by <a href="https://unsplash.com/@nasa?utm_source=medium&amp;utm_medium=referral">NASA</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Affordable Cloud in 2025: Hetzner vs DigitalOcean vs AWS vs Cloudflare vs Azure Cloud</h3><p>Choosing the right cloud provider in 2025 is less about raw compute power and more about <strong>price predictability, egress costs, and simplicity</strong>. For indie developers, startups, or even small enterprises, “affordable cloud” is the sweet spot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AoS51vZHybVuhjOPXBYf3w.png" /></figure><p>In this article, I’ll compare <strong>Hetzner</strong>, <strong>DigitalOcean</strong>, <strong>AWS (EC2/Lightsail)</strong>, <strong>Cloudflare (Workers/R2) and Azure Cloud </strong>across compute, storage, egress, and usability — then break down two realistic cost scenarios.</p><h3>1. Compute (VMs &amp; Serverless)</h3><p><strong>Hetzner Cloud (EU/US/SIN)<br>VM Pricing:</strong> Entry-level CX11 plan (1 vCPU, 2 GB RAM, 20 GB SSD) starts at <strong>€3.49/month</strong> with 20 TB included traffic (EU/US).<br><strong>Scaling:</strong> Larger instances up to 48 vCPUs, very cost-efficient<br><strong>Serverless:</strong> No native function service.</p><p><strong>DigitalOcean Droplets<br>VM Pricing: </strong>Starts at $6/month (1 vCPU, 1 GB RAM, 1 TB transfer).<br><strong>Bandwidth: </strong>Shared pool across Droplets, overage $0.01/GB.<br><strong>Serverless:</strong> “App Platform” has Functions at ~$5/month entry.</p><p><strong>AWS EC2 / Lightsail<br>EC2 Pricing:</strong> t3.small (2 vCPU, 2 GB) ~<strong>$15/month</strong> (Linux, 24/7 usage).<br><strong>Lightsail Pricing:</strong> More predictable, $10/month for 1 vCPU + 2 GB RAM + 60 GB SSD + 2 TB transfer.<br><strong>Serverless (Lambda):</strong> 1M free requests, then $0.20/million requests.</p><p><strong>Cloudflare Workers<br>Pricing:</strong> $5/month includes 10M requests, free egress.<br><strong>Scope:</strong> Only serverless, no traditional VM.</p><p><strong>Azure Cloud<br>VM Pricing:</strong> B1s instance (1 vCPU, 1 GB RAM) ~<strong>$10–12/month</strong>, depending on region.<br><strong>Serverless (Azure Functions):</strong> 1M requests/month free, then $0.20 per million requests (same as AWS).</p><h3>2. Containers &amp; Kubernetes</h3><ul><li><strong>Hetzner:</strong> No managed Kubernetes. You can deploy k3s/K8s yourself. Community projects (like k3sup) help.</li><li><strong>DigitalOcean:</strong> Managed Kubernetes (DOKS), $12/month per node. Very developer-friendly.</li><li><strong>AWS:</strong> EKS ($0.10/hr control plane + EC2/ Fargate costs). Expensive but enterprise-ready.</li><li><strong>Cloudflare:</strong> No native Kubernetes. Workers Durable Objects / D1 for stateful apps.</li><li><strong>Azure:</strong> Azure Kubernetes Service (AKS), no control-plane cost, pay for VMs only. Strong enterprise integrations.</li></ul><h3>3. Databases</h3><ul><li><strong>Hetzner:</strong> Managed DBs (Postgres, MySQL, Redis). Starting at €4.90/month.</li><li><strong>DigitalOcean:</strong> Managed DBs (Postgres, MySQL, Redis, MongoDB). Start at $15/month.</li><li><strong>AWS:</strong> RDS (Postgres, MySQL, MariaDB, Oracle, SQL Server). Pricing starts ~$15–20/month. DynamoDB also available.</li><li><strong>Cloudflare:</strong> D1 (SQLite-based), KV store, Durable Objects. Low-cost, serverless-style.</li><li><strong>Azure:</strong> Managed DBs (Azure SQL, CosmosDB, Postgres, MySQL, MariaDB). Entry at ~$5–10/month for smallest tiers. Cosmos DB billed per RU/s, costly at scale.</li></ul><h3>4. Data Services (Storage &amp; Analytics)</h3><ul><li><strong>Hetzner:</strong> Object Storage (S3-compatible), €4.90/month for 1 TB. Very cheap.</li><li><strong>DigitalOcean:</strong> Spaces, $5/month (250 GB + 1 TB egress). Additional storage $0.02/GB.</li><li><strong>AWS:</strong> S3, $0.023/GB storage + $90/TB egress. Glue, Athena, Redshift for analytics.</li><li><strong>Cloudflare:</strong> R2 Storage, $0.015/GB, free egress. Workers KV and Durable Objects available.</li><li><strong>Azure:</strong> Blob Storage, from $0.0184/GB. Azure Synapse for analytics (enterprise-grade, expensive).</li></ul><h3>5. Security &amp; Compliance</h3><ul><li><strong>Hetzner:</strong> GDPR-focused (data centers in Germany/Finland). Basic firewalls, private networking.</li><li><strong>DigitalOcean:</strong> VPC, firewalls, monitoring, GDPR compliant but less enterprise certifications.</li><li><strong>AWS:</strong> Strong compliance portfolio (HIPAA, PCI-DSS, FedRAMP). Security Hub, GuardDuty.</li><li><strong>Cloudflare:</strong> WAF, DDoS protection, Zero Trust features included by default.</li><li><strong>Azure:</strong> Enterprise compliance, integrates with Microsoft security stack (Defender for Cloud).</li></ul><h3>6. DevOps &amp; Scope (IaC, IaP, IaS, Automation &amp; CI/CD)</h3><p><strong>Hetzner:<br>IaC/IaP/IaaS:</strong> Terraform provider available, mostly IaaS. Limited PaaS/SaaS.<br><strong>Automation:</strong> Supported via Ansible, Python, Bash using API modules.<br><strong>CI/CD:</strong> No native platform. Can integrate GitHub Actions, GitLab CI, Jenkins, or Drone via SSH/API. DIY approach.</p><p><strong>DigitalOcean:<br>IaC/IaP/IaaS:</strong> Good Terraform support, App Platform (PaaS). SMB/dev-focused.<br><strong>Automation:</strong> Ansible, Python scripts, API/CLI.<br><strong>CI/CD:</strong> Native App Platform CI/CD available. Works well with GitHub Actions, GitLab CI, Jenkins.</p><p><strong>AWS:<br>IaC/IaP/IaaS:</strong> Full support (CloudFormation, Terraform, Amplify, AppRunner), IaaS/PaaS/SaaS. Enterprise-ready.<br><strong>Automation:</strong> Ansible (official modules), Python (boto3), Bash, Go SDKs.<br><strong>CI/CD:</strong> Full ecosystem (CodePipeline, CodeBuild, CodeDeploy), integrates with GitHub/GitLab/Bitbucket. Highly scalable.</p><p><strong>Cloudflare:<br>IaC/IaP/IaaS:</strong> Serverless focus. Terraform support. Mostly Functions + Edge Network services.<br><strong>Automation:</strong> Community Ansible modules, APIs (Python, JS, Go).<br><strong>CI/CD:</strong> Mainly for Workers deployments. Supports GitHub Actions, Wrangler CLI. Edge-first workflows, not full container orchestration.</p><p><strong>Azure:<br>IaC/IaP/IaaS:</strong> Complete scope (Bicep/Terraform, IaP, SaaS like Office 365). Enterprise integrations.<br><strong>Automation:</strong> Ansible (official modules), PowerShell, Python, CLI.<br><strong>CI/CD:</strong> Rich ecosystem via Azure DevOps, GitHub Actions, Pipelines. Supports IaaS, PaaS, serverless, hybrid deployments. Enterprise-ready.</p><blockquote>💡 <strong>Summary:<br>Hetzner:</strong> DIY, flexible, but no native CI/CD.<br><strong>DigitalOcean:</strong> Lightweight native CI/CD + integrations.<br><strong>AWS:</strong> Full enterprise CI/CD suite.<br><strong>Cloudflare:</strong> Edge/serverless focused CI/CD.<br><strong>Azure:</strong> Full CI/CD support, strong for Microsoft ecosystem and hybrid workloads.</blockquote><h3>7. Storage (Object Storage &amp; CDN)</h3><ul><li><strong>Cloudflare R2:</strong> <strong>$0.015/GB per month</strong> with <strong>zero egress fees</strong>. Game-changer for media-heavy apps.</li><li><strong>DigitalOcean Spaces:</strong> <strong>$5/month</strong> for 250 GB storage + 1 TB bandwidth. Extra: <strong>$0.02/GB storage</strong> and <strong>$0.01/GB bandwidth</strong>.</li><li><strong>Hetzner Storage Box / Object Storage:</strong> Extremely low-cost storage options. Great for backups and archives.</li><li><strong>AWS S3:</strong> Feature-rich but expensive on bandwidth. First 100 GB egress per month free; after that ~<strong>$0.09/GB</strong>.</li></ul><blockquote>⚠️ CDN Security Note: Cloudflare Vulnerability</blockquote><blockquote>In early 2025, security researchers discovered a vulnerability in <strong>Cloudflare’s CDN</strong> that could leak users’ approximate location data, even in privacy-focused apps like Signal and Discord. The issue exploited the way Cloudflare routes traffic to the nearest data center, making it possible to infer a user’s physical region with high accuracy.</blockquote><blockquote>Cloudflare has since <strong>patched the vulnerability</strong>, but this case highlights the importance of regularly auditing CDN configurations, filtering unnecessary response headers, and keeping all WAF/CDN updates applied. Developers running sensitive applications should review their caching, logging, and security policies to reduce metadata exposure.</blockquote><p><a href="https://www.bleepingcomputer.com/news/security/cloudflare-cdn-flaw-leaks-user-location-data-even-through-secure-chat-apps/?utm_source=chatgpt.com">Cloudflare CDN flaw leaks user location data, even through secure chat apps</a></p><h3>8. Bandwidth (Egress) Costs</h3><blockquote>This is the “hidden killer” of cloud pricing.</blockquote><ul><li><strong>Hetzner:</strong> 20 TB included (EU/US). Extra traffic = <strong>€1/TB</strong>.</li><li><strong>DigitalOcean:</strong> <strong>$0.01/GB</strong> (~$10/TB).</li><li><strong>AWS EC2/S3:</strong> First 100 GB free, then <strong>~$0.09/GB</strong> (~$90/TB).</li><li><strong>Cloudflare Workers + R2:</strong> <strong>No egress fees at all.</strong></li></ul><h3>9. Ecosystem &amp; Ease of Use</h3><ul><li><strong>AWS:</strong> Unmatched ecosystem (databases, AI, analytics, compliance), but billing is complex. Best for enterprises.</li><li><strong>DigitalOcean:</strong> Simple dashboard, predictable pricing, good documentation. Great for small teams.</li><li><strong>Hetzner:</strong> Best raw performance per dollar. EU-based, attractive for GDPR-conscious teams.</li><li><strong>Cloudflare:</strong> Edge-first stack (Workers, Pages, KV, D1, R2). Excellent for serverless-first, CDN-heavy apps.</li></ul><h3>10. Quick Comparison Table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kr8xtH3EkV__26SMUdJCLw.png" /><figcaption>VMs, Serverless, Kubernetes, Database, Storage and Compliance</figcaption></figure><h3>11. Cost Scenarios (Extended)</h3><h4>Scenario A: Static Site + API + Media Delivery</h4><ul><li><strong>Cloudflare Workers (Paid):</strong> $5/month</li><li><strong>Cloudflare R2 (100 GB storage):</strong> ~$1.5/month</li><li><strong>Total:</strong> ~$6.5/month with unlimited egress.</li></ul><p>💡 <strong>Equivalent on AWS (S3 + CloudFront, 1 TB egress):</strong> ~$90+ per month.</p><blockquote>⚠️ <strong>Note: Why Azure and AKS Are Not Included in Scenario A<br></strong>Scenario A focuses on <strong>static sites, APIs, and media-heavy delivery</strong> with <strong>ultra-low egress costs</strong>, which is why Cloudflare Workers + R2 is ideal.</blockquote><blockquote><strong>Azure Static Web Apps + Blob Storage + CDN</strong> can achieve similar functionality, but <strong>egress costs are high</strong> (e.g., ~$87 for 1 TB), making it much more expensive than Cloudflare’s free egress.<br><strong>AKS (Azure Kubernetes Service)</strong> is meant for containerized workloads, not lightweight static sites or serverless APIs, so it doesn’t fit this cost-effective media delivery scenario.<br><strong>Hetzner and DigitalOcean</strong> also lack global edge/CDN for free egress, so they are less suitable for this use case.</blockquote><blockquote>✅ <strong>Bottom line:</strong> Scenario A demonstrates <strong>Cloudflare’s edge/serverless advantage</strong> for low-cost, bandwidth-heavy applications.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hikVFI1pPZyBURakwiXxfw.png" /></figure><p>💡 <strong>Key Takeaways:<br>Cloudflare</strong> → cheapest for <strong>edge/serverless + free egress</strong>, perfect for global lightweight API + media.<br><strong>Azure</strong> → technically possible via <strong>Functions + Datamart + CDN</strong>, but <strong>egress costs dominate</strong>.<br><strong>AWS</strong> → similar to Azure; serverless + CDN possible but expensive.<br><strong>Hetzner / DigitalOcean</strong> → need extra infrastructure for CDN; not ideal for Scenario A.</p><h4>Scenario B: Small API on VM (2 vCPU / 2 GB RAM, 1 TB traffic)</h4><ul><li><strong>Hetzner Cloud:</strong> ~$5/month (20 TB traffic included)</li><li><strong>DigitalOcean:</strong> ~$12/month (1 TB usually included)</li><li><strong>AWS EC2:</strong> ~$96/month (compute + egress)</li><li><strong>AWS Lightsail:</strong> $10/month (transfer included)</li><li><strong>Azure B1s VM:</strong> ~$10–12/month (750 free hours tier available)</li></ul><h4>Scenario C: Serverless API (50M requests/month)</h4><ul><li><strong>Cloudflare Workers:</strong> ~$25 (after free tier: $5 for 10M req, then $0.30 per 1M)</li><li><strong>AWS Lambda:</strong> ~$10 (after free tier: $0.20 per 1M req)</li><li><strong>Azure Functions:</strong> ~$10 (same pricing model as AWS)</li><li><strong>DigitalOcean Functions:</strong> ~$15–20 (based on execution time and memory)</li></ul><h4>Scenario D: Managed Kubernetes (3 nodes, 2 vCPU / 4 GB RAM each)</h4><ul><li><strong>Hetzner:</strong> ~€15/month self-managed (nodes only, no extra fee)</li><li><strong>DigitalOcean DOKS:</strong> ~$36/month ($12 per node, managed control plane included)</li><li><strong>AWS EKS:</strong> ~$72/month (EC2 + $0.10/hr per cluster control plane)</li><li><strong>Azure AKS:</strong> ~$36/month (nodes only, control plane free)</li><li><strong>Cloudflare:</strong> ❌ No Kubernetes</li></ul><h4>Scenario E: Managed Database (Postgres, 1 vCPU / 2 GB RAM, 20 GB storage)</h4><ul><li><strong>Hetzner:</strong> ~€4.90/month</li><li><strong>DigitalOcean:</strong> ~$15/month</li><li><strong>AWS RDS:</strong> ~$20–25/month (including storage + backups)</li><li><strong>Azure Database for PostgreSQL:</strong> ~$15–20/month</li><li><strong>Cloudflare D1:</strong> Extremely cheap (still beta, minimal cost for small workloads)</li></ul><h4>Scenario F: Storage (1 TB data + 1 TB outbound traffic)</h4><ul><li><strong>Hetzner Storage Box/Object:</strong> ~€4.90/month (traffic included)</li><li><strong>DigitalOcean Spaces:</strong> ~$20/month (250 GB + 1 TB included, then $0.02/GB storage + $0.01/GB bandwidth)</li><li><strong>AWS S3 + egress:</strong> ~$100/month (storage + bandwidth, $0.09/GB egress)</li><li><strong>Azure Blob Storage:</strong> ~$18–20/month (storage + bandwidth)</li><li><strong>Cloudflare R2:</strong> ~$15/month (storage only, <strong>egress free</strong>)</li></ul><h3>12. Which One Should You Choose?</h3><ul><li><strong>Hetzner</strong> → Best for <strong>cheap VMs, self-hosted Kubernetes, and bandwidth-heavy workloads</strong>.</li><li><strong>DigitalOcean</strong> → Best for <strong>simplicity, managed services, and predictable pricing</strong>.</li><li><strong>AWS</strong> → Best for <strong>enterprise-scale, advanced features, and compliance-heavy workloads</strong>.</li><li><strong>Azure</strong> → Best for <strong>enterprise apps, Microsoft ecosystem integration, and compliance</strong>.</li><li><strong>Cloudflare</strong> → Best for <strong>serverless, edge-based, and egress-heavy apps (APIs, media, CDN)</strong>.</li></ul><h3>Final Thoughts</h3><p>There’s no universal “cheapest” cloud — the right choice depends on your architecture, traffic patterns, and workload type. Here’s a breakdown of the top options:</p><ul><li><strong>Hetzner 🥇</strong> — Cheapest compute &amp; storage, with generous included bandwidth. Limited ecosystem, but perfect for <strong>cost-conscious startups</strong> or small VM-based workloads.</li><li><strong>DigitalOcean 💻</strong> — Affordable, user-friendly, with better PaaS &amp; managed Kubernetes. Great for <strong>developers and simplicity-focused teams</strong>.</li><li><strong>AWS 🌐</strong> — Most powerful and flexible ecosystem, enterprise-grade features and compliance. High costs, especially for egress-heavy workloads, but ideal for <strong>large-scale or complex architectures</strong>.</li><li><strong>Cloudflare ⚡</strong> — Innovative <strong>serverless + edge-first architecture</strong> with free egress. Perfect for <strong>modern APIs, static sites, and media-heavy applications</strong>.</li><li><strong>Azure 🏢</strong> — Strong in the <strong>Microsoft ecosystem</strong> with deep integrations, enterprise compliance, and hybrid-ready solutions. Azure Functions + Datamart (with CDN) is solid for <strong>serverless and analytics workloads</strong>, though egress costs can be higher than Cloudflare.</li></ul><p>✅ <strong>Bottom line:</strong> Choose the cloud that fits <strong>your workload type, scaling needs, and budget</strong>, not just the cheapest sticker price. Each provider has its strengths — Hetzner for cost, DigitalOcean for simplicity, AWS for enterprise, Cloudflare for modern serverless, and Azure for Microsoft-centric enterprise workloads.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4082c00446e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>