From 28b32f4ec751f89e17652730b62e9fd184c2c548 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Oct 2024 22:38:54 +0000 Subject: [PATCH 1/2] [pre-commit.ci] pre-commit autoupdate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit updates: - [github.com/pre-commit/pre-commit-hooks.git: v3.4.0 → v5.0.0](https://github.com/pre-commit/pre-commit-hooks.git/compare/v3.4.0...v5.0.0) - [github.com/ansible/ansible-lint.git: v5.0.8 → v24.9.2](https://github.com/ansible/ansible-lint.git/compare/v5.0.8...v24.9.2) --- .pre-commit-config.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 452b1cd..446f25e 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -2,7 +2,7 @@ repos: - repo: https://github.com/pre-commit/pre-commit-hooks.git - rev: v3.4.0 + rev: v5.0.0 hooks: - id: end-of-file-fixer - id: trailing-whitespace @@ -15,7 +15,7 @@ repos: - id: check-added-large-files - repo: https://github.com/ansible/ansible-lint.git - rev: v5.0.8 + rev: v24.9.2 hooks: - id: ansible-lint files: \.(yaml|yml)$ From 66e4e973ae2b003dede4a5a43e525b2c4a5605ec Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Oct 2024 22:40:07 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 7210439..5309c01 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ Ansible Role Docker PHP -

+

This Ansible role install PHP On Ubuntu, CentOS Amazon-Linux With Docker.

@@ -51,7 +51,7 @@ -We eat, drink, sleep and most importantly love **DevOps**. DevOps always promotes automation and standardisation. While setting up various environments like local, dev, testing, production, etc. it is critical to maintain the same environment across. This can easily be achieved using automating the environment setup & installation with the help of ansible-playbooks. +We eat, drink, sleep and most importantly love **DevOps**. DevOps always promotes automation and standardisation. While setting up various environments like local, dev, testing, production, etc. it is critical to maintain the same environment across. This can easily be achieved using automating the environment setup & installation with the help of ansible-playbooks. Smaller roles are created for each environment elements; which also include tasks & tests. These roles can then be grouped together in [ansible-playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) to achieve the desired yet consistent results. @@ -59,7 +59,7 @@ Smaller roles are created for each environment elements; which also include task ## Prerequisites -This module has a few dependencies: +This module has a few dependencies: - [Ansible2.9](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) - [Python](https://www.python.org/downloads) @@ -118,7 +118,7 @@ Following things includes in this role: -## Feedback +## Feedback If you come accross a bug or have any feedback, please log it in our [issue tracker](https://github.com/clouddrove/ansible-role-docker-php/issues), or feel free to drop us an email at [hello@clouddrove.com](mailto:hello@clouddrove.com). If you have found it worth your time, go ahead and give us a ★ on [our GitHub](https://github.com/clouddrove/ansible-role-docker-php)!