Dockerize

[Sreyeesh]

---

🚀 Why Dockerize the Project?

1. Portability: Run your portfolio in any environment with Docker installed.
2. Consistency: Eliminates "it works on my machine" issues.
3. Deployment: Simplifies deployment workflows and makes it easy to package for testing or sharing.
4. DevOps Experience: Demonstrates your ability to containerize projects effectively.

---

📝 Issue Description: Dockerize the Linux Terminal Portfolio

Title: Dockerize PortfolioFlow for Easy Deployment

Description:
To improve deployment consistency and portability, the Linux terminal-inspired portfolio (PortfolioFlow) will be dockerized. This will allow the project to run seamlessly across any system using Docker.

Tasks:

1. Create a Dockerfile to build and serve the portfolio.
   • Use a lightweight base image like nginx or node (for static hosting).
2. Add commands to expose the appropriate port (e.g., 8080).
3. Test the Dockerized portfolio locally using:

   docker build -t portfolioflow .  
   docker run -p 8080:80 portfolioflow  

4. Update the README with instructions for running the project with Docker.

---

🚀 How to Write the Dockerfile (Example)

Here’s a simple Dockerfile for static hosting using nginx:

# Use nginx to serve the static files
FROM nginx:alpine

# Copy portfolio files to the default nginx html directory
COPY ./ /usr/share/nginx/html

# Expose port 80
EXPOSE 80

# Start nginx
CMD ["nginx", "-g", "daemon off;"]

---

Benefits of Adding This as an Issue

1. It adds clear value to your project.
2. It demonstrates Docker skills, which are key in DevOps workflows.
3. You can show this off in your GitHub Projects and add it to your portfolio’s help or documentation.