After completing the tasks, collect all files, source code, configuration files, screenshots, reports, and other evidence related to your completed tasks in one properly organized folder.
Please follow the submission process below carefully.
1️⃣ Create One Main Submission Folder
Create a folder using the following naming format:
2️⃣ Create Separate Folders for Each Task
Inside the main folder, create separate folders for all 8 tasks:
3️⃣ Put All Relevant Evidence Inside Each Task Folder
- Source code files
- Dockerfiles
- Docker Compose files
- GitHub Actions workflow files
- Configuration files
- Terminal/command screenshots
- Application screenshots
- Cloud deployment screenshots
- Monitoring and logging screenshots
- Task-specific documentation
- Any other evidence requested for that task
4️⃣ Add a Final Internship Report
Inside the main folder, create a final PDF report containing:
- Your name and internship details
- Tasks completed
- Technologies/tools used
- Project descriptions
- Problems encountered and solutions
- GitHub repository links
- Deployment details
- Monitoring approach
- Final project screenshots
- Key learning outcomes
5️⃣ Share the Complete Folder
Upload the complete main folder to Google Drive or another suitable cloud-storage service.
Set the folder sharing permission so that the internship team can access the submitted files.
Share the folder with:
6️⃣ Submit the Folder Link
Copy the shareable folder link and submit the link through the designated internship task submission form/portal.
Make sure the submitted folder can be accessed by the internship evaluation team. If you use restricted sharing, specifically add hr@corporatewebsol.com as a viewer/editor according to the instructions provided by the team.
7️⃣ Final Folder Checklist
- ☐ All 8 task folders created
- ☐ Required files added to each task folder
- ☐ Screenshots added
- ☐ Source code added
- ☐ GitHub links included
- ☐ Final PDF report added
- ☐ Folder shared with HR
- ☐ Access permission checked
- ☐ Final folder link copied
- ☐ Folder link submitted through the internship portal
Never upload passwords, private SSH keys, API keys, access tokens, database passwords, cloud credentials, or other confidential authentication information to the submission folder or GitHub. Replace sensitive values with placeholders before submission.
Submit one organized folder containing your complete Task Portal 5 work. Do not send individual files separately unless specifically requested by the internship team.
Learn how to administer a Linux-based server, manage users and permissions, inspect running services, configure processes, and troubleshoot basic server-level issues.
- Create a dedicated DevOps user and configure appropriate permissions.
- Create a project directory with controlled ownership.
- Configure file and directory permissions using chmod and chown.
- Install and inspect a server package such as Nginx.
- Start, stop, restart, and enable a Linux service.
- Check CPU, memory, disk, and process utilization.
- Identify a running process and terminate it safely.
- Inspect system logs using journalctl.
- Screenshot of created Linux user.
- Screenshot showing permissions and ownership.
- Screenshot of Nginx service status.
- System resource monitoring screenshot.
- Brief explanation of the commands performed.
Practice a professional Git workflow involving branches, commits, remote repositories, pull operations, merge conflicts, and version tracking.
- Create a local DevOps project repository.
- Create meaningful commits using Git.
- Create a feature branch.
- Make changes and push the branch to GitHub.
- Merge the feature branch into the main branch.
- Simulate and resolve a basic merge conflict.
- Inspect Git history and changed files.
- Add a professional README.md file.
- GitHub repository link.
- Screenshot of branches.
- Screenshot of commit history.
- Evidence of successful merge.
- README explaining the project.
Understand how Docker containers are created, configured, networked, and deployed for a simple web application.
- Create a simple HTML or Node.js web application.
- Create a Dockerfile for the application.
- Build a custom Docker image.
- Run the application inside a container.
- Map the container port to the host.
- Inspect container logs and running containers.
- Create a custom Docker network.
- Stop, restart, and remove containers.
- Dockerfile.
- Application source code.
- Screenshot of Docker image.
- Screenshot of running container.
- Browser screenshot showing the application.
- GitHub repository containing the Docker project.
Learn how Docker Compose can be used to deploy and manage multiple interconnected services as a single application stack.
- Create a web application with a backend service.
- Add a database container such as MySQL or PostgreSQL.
- Create a docker-compose.yml file.
- Configure environment variables.
- Configure service dependencies.
- Create a persistent database volume.
- Create an internal Docker network.
- Start and stop the complete application stack.
- docker-compose.yml file.
- Application architecture diagram.
- Screenshot of all running services.
- Database connection evidence.
- GitHub repository link.
Build a basic Continuous Integration and Continuous Deployment pipeline that automatically tests and builds an application whenever code is pushed.
- Create a GitHub Actions workflow.
- Trigger the workflow when code is pushed to main.
- Configure an Ubuntu runner.
- Checkout the repository.
- Install application dependencies.
- Run automated tests or validation.
- Build a Docker image.
- Store build information as a workflow artifact.
- .github/workflows workflow file.
- Screenshot showing successful GitHub Actions run.
- Screenshot of build stages.
- Repository link.
- Short explanation of CI/CD workflow.
Deploy a containerized application on a cloud Linux server and configure Nginx as a reverse proxy to route public traffic to the application.
- Provision a Linux cloud VM using AWS, Azure, GCP, or another provider.
- Connect to the server using SSH.
- Install Docker and Nginx.
- Deploy the application container.
- Configure firewall/security-group rules.
- Configure Nginx as a reverse proxy.
- Test the application through the server IP/domain.
- Check Nginx access and error logs.
- Cloud server details screenshot with sensitive credentials hidden.
- SSH connection evidence.
- Running Docker container screenshot.
- Nginx configuration file.
- Live application URL or server-IP evidence.
Implement basic infrastructure monitoring and application log analysis to identify resource usage, failures, and service availability.
- Monitor CPU, RAM, disk, and network utilization.
- Collect application logs.
- Inspect Docker container logs.
- Identify HTTP 4xx and 5xx responses.
- Configure a basic health-check endpoint.
- Monitor whether the application is available.
- Document one simulated application failure.
- Restart the failed service and document the recovery process.
- System monitoring screenshots.
- Docker statistics screenshot.
- Application log sample.
- Health-check result.
- Failure and recovery report.
- Short monitoring architecture diagram.
Combine the skills learned in this portal to create a complete mini DevOps deployment workflow from source-code commit to containerized deployment and monitoring.
- Create or select a small web application.
- Push the project to GitHub.
- Create a feature branch and implement a change.
- Create a production-ready Dockerfile.
- Create Docker Compose configuration if multiple services are used.
- Configure a GitHub Actions CI pipeline.
- Build the Docker image automatically.
- Deploy the application to a Linux cloud server.
- Configure Nginx as a reverse proxy.
- Implement basic application/server monitoring.
- Document the complete deployment process.
- Project Overview
- Technology Stack
- Git Repository Structure
- Docker Architecture
- CI/CD Workflow
- Cloud Deployment Architecture
- Nginx Reverse Proxy Configuration
- Monitoring & Logging Approach
- Problems Encountered
- Solutions Implemented
- Final Application URL
- Future Improvements
- GitHub repository URL.
- Dockerfile and configuration files.
- Successful CI/CD pipeline screenshot.
- Cloud deployment screenshot.
- Live application URL.
- Nginx configuration evidence.
- Monitoring/logging evidence.
- Complete DevOps Deployment Report in PDF.
- Architecture diagram.
- Final project demonstration screenshots.
After completing the tasks, collect all files, source code, configuration files, screenshots, reports, and other evidence related to your completed tasks in one properly organized folder.
Please follow the submission process below carefully.
1️⃣ Create One Main Submission Folder
Create a folder using the following naming format:
2️⃣ Create Separate Folders for Each Task
Inside the main folder, create separate folders for all 8 tasks:
3️⃣ Put All Relevant Evidence Inside Each Task Folder
- Source code files
- Dockerfiles
- Docker Compose files
- GitHub Actions workflow files
- Configuration files
- Terminal/command screenshots
- Application screenshots
- Cloud deployment screenshots
- Monitoring and logging screenshots
- Task-specific documentation
- Any other evidence requested for that task
4️⃣ Add a Final Internship Report
Inside the main folder, create a final PDF report containing:
- Your name and internship details
- Tasks completed
- Technologies/tools used
- Project descriptions
- Problems encountered and solutions
- GitHub repository links
- Deployment details
- Monitoring approach
- Final project screenshots
- Key learning outcomes
5️⃣ Share the Complete Folder
Upload the complete main folder to Google Drive or another suitable cloud-storage service.
Set the folder sharing permission so that the internship team can access the submitted files.
Share the folder with:
6️⃣ Submit the Folder Link
Copy the shareable folder link and submit the link through the designated internship task submission form/portal.
Make sure the submitted folder can be accessed by the internship evaluation team. If you use restricted sharing, specifically add hr@corporatewebsol.com as a viewer/editor according to the instructions provided by the team.
7️⃣ Final Folder Checklist
- ☐ All 8 task folders created
- ☐ Required files added to each task folder
- ☐ Screenshots added
- ☐ Source code added
- ☐ GitHub links included
- ☐ Final PDF report added
- ☐ Folder shared with HR
- ☐ Access permission checked
- ☐ Final folder link copied
- ☐ Folder link submitted through the internship portal
Never upload passwords, private SSH keys, API keys, access tokens, database passwords, cloud credentials, or other confidential authentication information to the submission folder or GitHub. Replace sensitive values with placeholders before submission.
Submit one organized folder containing your complete Task Portal 5 work. Do not send individual files separately unless specifically requested by the internship team.