<?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 Hillary Chinedu Osagie on Medium]]></title>
        <description><![CDATA[Stories by Hillary Chinedu Osagie on Medium]]></description>
        <link>https://medium.com/@hillsdgreat?source=rss-12f7e49a4254------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*LSZOa3UAeB3XWzkY</url>
            <title>Stories by Hillary Chinedu Osagie on Medium</title>
            <link>https://medium.com/@hillsdgreat?source=rss-12f7e49a4254------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:29:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hillsdgreat/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[Dockerize a Static Website Using Docker]]></title>
            <link>https://medium.com/@hillsdgreat/dockerize-a-static-website-using-docker-57f6ef681c6f?source=rss-12f7e49a4254------2</link>
            <guid isPermaLink="false">https://medium.com/p/57f6ef681c6f</guid>
            <dc:creator><![CDATA[Hillary Chinedu Osagie]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 15:42:41 GMT</pubDate>
            <atom:updated>2026-10-10T15:42:41.064Z</atom:updated>
            <content:encoded><![CDATA[<p>Dockerize a Static Website Using Docker</p><p><em>A step-by-step guide using the CardioCare template from ThemeWagon</em></p><h3>Introduction</h3><p>In this project, I demonstrate how to containerize a static website using Docker. The website is CardioCare, an HTML and CSS template downloaded from ThemeWagon. The goal is to package the website and its assets into a Docker image, run it inside a container using Nginx, test it locally, and publish the image to Docker Hub.</p><p>This project covers Dockerfile creation, image building, container management, versioning, and publishing container images to a registry.</p><h3>Project workflow</h3><p>· Prepare the CardioCare website files.</p><p>· Create a Dockerfile</p><p>· Build the Docker image.</p><p>· Run and test the website in a container.</p><p>· Create a Docker Hub repository and push version 1.</p><p>· Modify the website, rebuild version 2, test it, and push it.</p><h3>Step 1: Prepare the CardioCare website</h3><p>I downloaded the CardioCare static website template from ThemeWagon, extracted it, and opened the project folder in Visual Studio Code. The template may include HTML, CSS, JavaScript, images, fonts, and other assets.</p><p>Before continuing, I checked that index.html is in the root of the project folder. Nginx needs to find the website entry page in its document root.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*M8Rl-6gR5lC0q2uRnc4b0w.png" /></figure><p>Note: The exact folders and HTML filenames depend on the version of the CardioCare template you downloaded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*gr9WD-bpD9t5_VuV2fVP2Q.png" /><figcaption><strong>FIGURE 1 — CardioCare project structure in VS Code</strong></figcaption></figure><h3>Step 2: Create the Dockerfile</h3><p>Inside the root of the cardiocare folder, I created a file named Dockerfile. Docker uses the instructions in this file to build the image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*jMnUhb7hspCIBBR5jXt4NA.png" /></figure><p>What each instruction does:</p><p>· FROM nginx:latest uses the Nginx image as the base image.</p><p>· WORKDIR sets the working directory inside the image.</p><p>· COPY copies the build-context files into Nginx’s default document root.</p><p>· EXPOSE 80 documents the port Nginx uses inside the container. It does not publish the port to your computer by itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Q-M0yfV0LxveBo8kYYSEvw.png" /><figcaption><strong>FIGURE 2 — Dockerfile in VS Code</strong></figcaption></figure><h3>Step 3: Build the Docker image</h3><p>Open a terminal in the root of the cardiocare project directory and check that Docker is available:</p><p>run <strong>docker — version</strong></p><p>Build the first image:</p><p><strong>docker build -t cardiocare:v1 .</strong></p><p>docker build builds the image; -t cardiocare:v1 names it cardiocare and gives it the v1 tag; the final dot tells Docker to use the current directory as the build context.</p><p>Verify that the image was created: Run the command <strong>docker images</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H4ItPSV6hi5Pn96CzJbWOQ.png" /><figcaption><strong>FIGURE 3 — Building the Docker image</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MHnhkpKrK-akRKiRhUGQlA.png" /><figcaption><strong>FIGURE 4 — Verifying the Docker image</strong></figcaption></figure><h3>Step 4: Run the Docker container</h3><p>Start a container from the image: run the command below</p><p><strong>docker run -d — name cardiocare-v1 -p 8080:80 cardiocare:v1</strong></p><p>The command runs the container in the background, names it cardiocare-v1, and maps port 8080 on your computer to port 80 inside the container.</p><p>Check that it is running by running : <strong>docker ps</strong></p><p>If you need to troubleshoot, inspect the container logs: <strong>run docker logs cardiocare-v1</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*-5KK1udxsxxmHnA8rnPNJQ.png" /><figcaption><strong>FIGURE 5 — Checking the running container</strong></figcaption></figure><h3>Step 5: Test the website in a browser</h3><p>Open a browser and navigate to:</p><p><a href="http://localhost:8080/">http://localhost:8080</a></p><p>Confirm that the CardioCare home page loads and that the styling, images, and other assets appear correctly. Where possible, test navigation links and other pages in the template as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*48O2QLoolqxie9B9_vjhPg.png" /><figcaption><strong>FIGURE 6 — CardioCare website running locally</strong></figcaption></figure><h3>Step 6: Create a Docker Hub repository</h3><p>After verifying the local website, I signed in at <a href="https://hub.docker.com/">https://hub.docker.com/</a> and created a repository named cardiocare. In the commands below, replace YOUR_DOCKERHUB_USERNAME with your actual Docker Hub username.</p><p>run docker login</p><p>Follow the authentication prompts to complete the login. Never include passwords or access tokens in screenshots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*2RcJdPc4FH8XujcSXtztvQ.png" /><figcaption><strong>FIGURE 7— CardioCare repository on Docker Hub</strong></figcaption></figure><h3>Step 7: Tag and push version 1</h3><p>Tag the local image with the Docker Hub repository name: run the command below</p><p><strong>docker tag cardiocare:v1 YOUR_DOCKERHUB_USERNAME/cardiocare:v1</strong></p><p>Push the image: run the command</p><p><strong>docker push YOUR_DOCKERHUB_USERNAME/cardiocare:v1</strong></p><p>After the push completes, refresh the repository page and confirm that the v1 tag is listed. The repository must be accessible to the account you are using.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*oesFZT3l992ZXsBFbrke2w.png" /><figcaption><strong>SCREENSHOT 8 — Tagging the Docker image</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*_chlRBII8gAI0tlmSs2EMg.png" /><figcaption><strong>SCREENSHOT 9 — Pushing version 1 to Docker Hub</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*p_v1m4eTFociqfGqGF_tag.png" /><figcaption><strong>SCREENSHOT 10 — Version 1 visible on Docker Hub</strong></figcaption></figure><h3>Step 8: Make a change to the website</h3><p>To demonstrate an update, I made a small change to the website, such as editing a home-page heading or adding a short introductory message. I saved the changed file in VS Code. The change should be visible in the browser after the new image is built and run. For this website I changed line 171 of my vs code from Expert Heart Care to Best and Experience Care and saved it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*84gJfQMC3mVe83GS41xz-Q.png" /><figcaption><strong>SCREENSHOT 11 — Updating the CardioCare website</strong></figcaption></figure><h3>Step 9: Build and test version 2</h3><p>Build a new image with the v2 tag:</p><p><strong>docker build -t cardiocare:v2 .</strong></p><p>Start a second container on port 8000:</p><p><strong>docker run -d — name cardiocare-v2 -p 8000:80 cardiocare:v2</strong></p><p>The first container uses host port 8080 and the second uses host port 8000, so they can run at the same time if both ports are available.</p><p>Open the updated website:</p><p><a href="http://localhost:8000/">http://localhost:8000</a></p><p>Confirm that the site loads and your recent change is visible. You can also run <strong>docker ps</strong> to inspect both containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*DRAnQmvxX77glr6hQrzpAg.png" /><figcaption><strong>SCREENSHOT 12 — Building CardioCare version 2</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ObbQVOZn5W01EpAd9SaceQ.png" /><figcaption><strong>SCREENSHOT 13 — Running the updated container</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*rhtXjKIU-dCwg_FvG3DhMw.png" /><figcaption><strong>SCREENSHOT 14 — Testing the updated website</strong></figcaption></figure><h3>Step 10: Push version 2 to Docker Hub</h3><p>Tag the updated image:</p><p><strong>docker tag cardiocare:v2 YOUR_DOCKERHUB_USERNAME/cardiocare:v2</strong></p><p>Push it to Docker Hub:</p><p><strong>docker push YOUR_DOCKERHUB_USERNAME/cardiocare:v2</strong></p><p>Refresh the repository page and confirm that both v1 and v2 tags are available.</p><p>See screenshot 18 for details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Pi6wYgDnuEOTGoPfjikqLg.png" /><figcaption><strong>SCREENSHOT 15 — Pushing version 2</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Y8Dbw4r7Wqh6avwgOjvBlQ.png" /><figcaption><strong>SCREENSHOT 16 — Both image versions on Docker Hub</strong></figcaption></figure><h3>Step 11: Final verification and cleanup</h3><p>Useful verification commands:</p><p>docker ps</p><p>docker images</p><p>When testing is complete, stop and remove the test containers:</p><p>docker stop cardiocare-v1 cardiocare-v2</p><p>docker rm cardiocare-v1 cardiocare-v2</p><p>These commands remove the containers but leave the local images available.</p><p>To pull and run the published v2 image on another machine, use:x</p><p>docker pull YOUR_DOCKERHUB_USERNAME/cardiocare:v2</p><p>docker run -d — name cardiocare-test -p 8080:80 YOUR_DOCKERHUB_USERNAME/cardiocare:v2</p><p>This assumes port 8080 is available and the Docker Hub repository is accessible.</p><h3>What I learned</h3><p>· Preparing a static website for containerization.</p><p>· Writing a Dockerfile using Nginx as the base image.</p><p>· Building and tagging Docker images.</p><p>· Running containers and mapping ports.</p><p>· Testing a website locally in a browser.</p><p>· Publishing images to Docker Hub.</p><p>· Rebuilding an image after application changes.</p><p>· Using version tags to distinguish releases.</p><p>· Managing and cleaning up Docker containers.</p><h3>Conclusion</h3><p>This project demonstrates how a static website downloaded from ThemeWagon can be packaged into a Docker image and served using Nginx. Containerizing CardioCare provides a portable way to run the website and offers practical experience publishing image versions to Docker Hub.</p><p>A useful next step is to automate the workflow so that changes to the website trigger an image build and publication process using CI/CD.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57f6ef681c6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Computing: A Double-Edged Sword Transforming Modern Business]]></title>
            <link>https://medium.com/@hillsdgreat/cloud-computing-a-double-edged-sword-transforming-modern-business-358e49ad58d1?source=rss-12f7e49a4254------2</link>
            <guid isPermaLink="false">https://medium.com/p/358e49ad58d1</guid>
            <dc:creator><![CDATA[Hillary Chinedu Osagie]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 20:24:06 GMT</pubDate>
            <atom:updated>2026-06-30T20:24:06.332Z</atom:updated>
            <content:encoded><![CDATA[<p>The cloud has revolutionized how organizations operate, innovate, and scale. But is it all sunshine above the clouds? Let’s explore both sides of this powerful technology.</p><h3>Introduction</h3><p>Cloud computing has become the backbone of today’s digital economy. From startups launching their first applications to multinational corporations running mission-critical workloads, businesses are increasingly relying on cloud services to drive growth and efficiency. The global shift towards cloud adoption has fundamentally changed how organizations store data, deploy applications, and manage IT infrastructure. However, while cloud computing offers numerous advantages, it also presents challenges that businesses must carefully consider.</p><h3>What is Cloud Computing?</h3><p>Cloud computing is the delivery of computing services — including servers, storage, databases, networking, software, analytics, and intelligence — over the internet. Instead of owning and maintaining physical data centers and servers, organizations can access these resources on demand from cloud providers such as Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*P_187DwlcT6mkVdTTbuqHQ.png" /></figure><p>As the diagram shows, the core shift is simple: instead of buying and maintaining hardware on-site, organizations reach over the internet to a provider who already has the servers, storage, and software running — and they pay only for what they use.</p><h3>The Advantages of Cloud Computing</h3><p>• <strong>Cost Efficiency</strong> — Lower upfront investment and predictable operational costs.</p><p>• <strong>Scalability and Flexibility</strong> — Businesses can grow without major infrastructure upgrades.</p><p>• <strong>Remote Accessibility</strong> — Improved collaboration, productivity, and workforce mobility.</p><p>• <strong>Enhanced Disaster Recovery</strong> — Reduced downtime and better business continuity.</p><p>• <strong>Improved Security Capabilities</strong> — Enterprise-grade security that many organizations would struggle to implement independently.</p><p>• <strong>Faster Innovation</strong> — Faster time-to-market and increased competitiveness.</p><h3>The Disadvantages of Cloud Computing</h3><p>• <strong>Dependence on Internet Connectivity</strong> — Service disruptions can impact business operations.</p><p>• <strong>Security and Privacy Concerns</strong> — Organizations must maintain strong governance and security practices.</p><p>• <strong>Vendor Lock-In</strong> — Reduced flexibility when changing providers.</p><p>• <strong>Unpredictable Costs</strong> — Cloud spending can exceed budgets if not managed effectively.</p><p>• <strong>Limited Control</strong> — Less direct control compared to on-premises environments.</p><ul><li><strong>Service Outages</strong> — Downtime can impact revenue, reputation, and customer experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*GhPg6Z8wkrtQ4oheMF8NxA.png" /></figure><p>Laid out side by side, the pattern becomes clear: nearly every advantage trades convenience and speed for a corresponding loss of control. That trade-off doesn’t make cloud computing risky by default — it just means the risks need to be managed as deliberately as the benefits are pursued.</p><h3>Finding the Right Balance</h3><p>Many organizations embrace Hybrid Cloud and Multi-Cloud approaches to balance flexibility, security, performance, and cost while minimizing risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*MJquQ6gu_fm97AZI5Bg4jA.png" /></figure><p>Rather than treating “cloud vs. on-premises” as an all-or-nothing decision, most mature organizations sit somewhere along this spectrum — keeping sensitive workloads closer to home while still taking advantage of the cloud’s scalability for everything else.</p><h3>Conclusion</h3><p>Cloud computing has transformed the modern business landscape by delivering scalability, agility, innovation, and cost savings. However, like any technology, it comes with challenges that require careful planning and management. The organizations that benefit most are those that understand both its strengths and limitations and use it strategically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=358e49ad58d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>