Cloud-1: Automated Web Application Deployment

Welcome to Cloud-1, an automated deployment project designed to deploy web applications on remote servers effortlessly. This README provides an overview of the project's key aspects and steps.

Contents

1. Introduction
2. Platform Choice
3. Mandatory Part
4. Focus Points
5. Submission and Peer-Evaluation
6. Using Ansible
7. Docker and Docker Compose
8. FAQs
9. Contributing
10. License

Introduction

Cloud-1 is inspired by the subject "Inception." The primary objective is to deploy your web application and the necessary Docker infrastructure on a remote server provided by a cloud provider. In this version, each process will have its container, and automation is crucial for deployment. We recommend using Ansible for automation.

Platform Choice

While Scaleway is recommended as a cloud provider, you're free to use other providers that offer equivalent services. Be aware of billing when using external providers, as you are responsible for any costs incurred.

Mandatory Part

• Automated deployment using a tool of your choice (Ansible recommended).
• Deploy a complete web server running services such as WordPress, PHPmyadmin, and a database.
• Ensure data persistence, automated restart, and secure public access.
• Deploy services in separate containers with inter-container communication.
• Use docker-compose.yml and enable TLS where possible.
• Implement URL redirection based on requested URLs.

Focus Points

• Responsible resource management to avoid unnecessary costs.
• Attention to server and service sizes to optimize resource usage.
• Be cautious with third-party services to prevent unexpected charges.
• Protect sensitive information (keys, identifiers) in public repositories.

Submission and Peer-Evaluation

Submit your project via your Git repository. Only content within your repository will be evaluated. Focus on functionality rather than aesthetics.

How Ansible Works

Ansible is an open-source automation tool that simplifies configuration management, application deployment, and task automation. It operates by defining tasks in simple YAML files known as "playbooks." Ansible playbooks describe a set of steps to be executed on target servers.

Here's a brief overview of how Ansible works:

1. Inventory: Define a list of target servers in an Ansible inventory file.

2. Playbooks: Create Ansible playbooks that contain a list of tasks to be performed on target servers.

3. Execution: Execute the playbooks using the ansible-playbook command. Ansible connects to target servers via SSH and runs the defined tasks.

4. Modules: Ansible modules are used within tasks to perform actions like package installation, service management, and file manipulation.

5. Idempotent: Ansible ensures that playbooks are idempotent, meaning they can be run multiple times without changing the target system if no changes are necessary.

For detailed Ansible documentation and examples, refer to the official Ansible documentation (opens in a new tab).

Docker and Docker Compose

How Docker Works

Docker is a platform designed to develop, ship, and run applications inside lightweight, portable containers. Containers are isolated environments that package an application and its dependencies, ensuring consistency and reproducibility across different systems.

Key Concepts

• Images: Docker uses images as the building blocks of containers. An image is a read-only template containing everything needed to run an application, including code, libraries, and system tools.

• Containers: Containers are instances of Docker images. They run in isolated environments, making them predictable and secure. Containers can be created, started, stopped, and deleted, allowing for easy management of applications.

• Dockerfile: To create Docker images, developers use Dockerfiles—a set of instructions that define an image's contents and behavior. Dockerfiles include commands for copying files, installing software, and configuring the environment.

• Registry: Docker images can be stored and shared via container registries like Docker Hub or private registries. These registries host images that can be easily pulled and run on different systems.

Benefits of Docker

• Consistency: Docker ensures that an application behaves the same way across different environments, from development to production.

• Isolation: Containers provide process and file system isolation, preventing conflicts between applications running on the same host.

• Efficiency: Docker's lightweight containers use fewer resources than traditional virtual machines, enabling efficient resource utilization.

How Docker Compose Works

Docker Compose is a tool for defining and running multi-container Docker applications. It allows you to manage complex applications composed of multiple services, each defined in a separate container.

Key Concepts

• docker-compose.yml: Docker Compose relies on a YAML file called docker-compose.yml to define services, networks, volumes, and other configuration details for your application.

• Services: Each service in the docker-compose.yml file represents a container that runs a specific component of your application. For example, you might have separate services for your web application, database, and caching system.

• Networks: Docker Compose automatically creates a network for your application, ensuring that containers can communicate with each other. You can also define custom networks for more advanced configurations.

• Volumes: Volumes allow you to persist data between container restarts. They can be used to store databases, configuration files, or other data that needs to be preserved.

Benefits of Docker Compose

• Simplified Development: Docker Compose simplifies the setup of multi-container applications, making it easier for developers to work on different parts of the application independently.

• Easy Reproduction: With a docker-compose.yml file, you can reproduce the entire application environment on any system, ensuring consistency across development, testing, and production.

• Scalability: Docker Compose is a valuable tool for orchestrating containers, making it possible to scale services as needed for load balancing and high availability.