archives/pleroma-ansible-playbook
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2023-05-06. You can view files and clone it, but cannot push or open issues or pull requests.
pleroma-ansible-playbook/examples/site.yml

35 lines
615 B
YAML
Raw Normal View History

change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
---
- name: Initialising the site playbook.
hosts: all
roles:
- init
tags:
- always
- name: Installing and configuring PostgreSQL for Pleroma.
hosts: pleroma_database
become: yes
become_method: sudo
roles:
fix: update ansible role names - pleroma-postgres renamed to pleroma-database. - pleroma-nginx renamed to pleroma-proxy. - site.yml in examples is updated to reflect the change. resolves dananglin/pleroma-ansible-playbook#12
2020-03-21 17:22:59 +00:00
- pleroma-database
change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
tags:
fix: update ansible role names - pleroma-postgres renamed to pleroma-database. - pleroma-nginx renamed to pleroma-proxy. - site.yml in examples is updated to reflect the change. resolves dananglin/pleroma-ansible-playbook#12
2020-03-21 17:22:59 +00:00
- pleroma-database
change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
- name: Installing and configuring the Pleroma backend.
hosts: pleroma_backend
become: yes
become_method: sudo
roles:
refactor: changed pleroma-backend to pleroma-main
2020-02-27 17:58:58 +00:00
- pleroma-main
change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
tags:
refactor: changed pleroma-backend to pleroma-main
2020-02-27 17:58:58 +00:00
- pleroma-main
change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
- name: Installing and configuring Nginx for Pleroma.
hosts: pleroma_webserver
become: yes
become_method: sudo
roles:
fix: update ansible role names - pleroma-postgres renamed to pleroma-database. - pleroma-nginx renamed to pleroma-proxy. - site.yml in examples is updated to reflect the change. resolves dananglin/pleroma-ansible-playbook#12
2020-03-21 17:22:59 +00:00
- pleroma-proxy
change: add a site playbook to the project. This merge request changes the project from a single role project to a single playbook project with multiple plays and roles. The single playbook has multiple plays with each having its own role to install and configure the different components to run Pleroma. (postgres database, pleroma backend and nginx). Certain playbooks can be executed by specifying the relevant tags. This change is the first of many changes to start supporting installations on both single and multiple hosts. This change includes also includes: - inventory file. - host_vars directory for users to add their variables. - an init playbook to merge the default and the user defined config for Pleroma. - users can now specify whether to validate certs when performing acme challenges (default: true). - more task templating.
2019-10-24 22:51:53 +01:00
tags:
fix: update ansible role names - pleroma-postgres renamed to pleroma-database. - pleroma-nginx renamed to pleroma-proxy. - site.yml in examples is updated to reflect the change. resolves dananglin/pleroma-ansible-playbook#12
2020-03-21 17:22:59 +00:00
- pleroma-proxy
Reference in a new issue Copy permalink