Ansible/Roles - Revision history

Admin: /* Database Role Directory Layout */

2018-12-08T18:46:32Z

Database Role Directory Layout

← Older revision		Revision as of 18:46, 8 December 2018
Line 172:		Line 172:

	====Database Role Directory Layout====		====Database Role Directory Layout====

			{{Main\|Ansible/Directory Layout}}

			{{Main\|Ansible/Directory Layout/Details}}

	The directory defining how this role works for the playbook will have the following directory structure:		The directory defining how this role works for the playbook will have the following directory structure:
Line 189:		Line 193:
	templates/		templates/
	</pre>		</pre>

			(As mentioned on the [[Ansible/Directory_Layout/Details#Creating_the_directory_structure]] page, you can also use the <code><nowiki>ansible-galaxy init -p <path-to-roles-directory> <name-of-role></nowiki></code> command to create this directory structure for each role.)

	The directories and the files they contain play the following roles:		The directories and the files they contain play the following roles:

2018-12-08T18:42:12Z

Example Playbook: Multiple Hosts

← Older revision		Revision as of 18:42, 8 December 2018
Line 160:		Line 160:
	- www.192.168.33.10.xip.io		- www.192.168.33.10.xip.io
	</pre>		</pre>

			==Roles==

			Roles are used to organize and divide up the various tasks, variables, and files for a given play.

	===Database role===		===Database role===

2018-12-08T18:41:11Z

Example Playbook: Multiple Hosts

← Older revision		Revision as of 18:41, 8 December 2018
Line 148:		Line 148:
	database_user: "{{ mezzanine_proj_name }}"		database_user: "{{ mezzanine_proj_name }}"

	- name: deploy ~~mezzanine~~ on vagrant		- name: deploy web frontend on vagrant
	hosts: web		hosts: web
	vars_files:		vars_files:
Line 160:		Line 160:
	- www.192.168.33.10.xip.io		- www.192.168.33.10.xip.io
	</pre>		</pre>





	===Database role===		===Database role===

2018-12-08T18:40:01Z

Example Playbook: Multiple Hosts

← Older revision		Revision as of 18:40, 8 December 2018
Line 136:		Line 136:

	<pre>		<pre>
			---
			# site.yml

	- name: deploy postgres on vagrant		- name: deploy postgres on vagrant
	hosts: db		hosts: db

2018-12-08T18:39:30Z

Example Playbook: Single Host with Pre and Post Tasks

← Older revision		Revision as of 18:39, 8 December 2018
Line 99:		Line 99:

	<pre>		<pre>
			---
			# site.yml

	- name: deploy mezzanine on vagrant		- name: deploy mezzanine on vagrant
	hosts: web		hosts: web

2018-12-08T18:39:04Z

Example Playbook: Single Host

2018-12-08T18:38:53Z

Example Playbook: Single Host

← Older revision		Revision as of 18:38, 8 December 2018
Line 76:		Line 76:

	<pre>		<pre>
			---
			# site.yml

	- name: deploy webapp on vagrant		- name: deploy webapp on vagrant
	hosts: web		hosts: web

2018-12-08T04:45:55Z

Database Role Directory Layout

← Older revision		Revision as of 04:45, 8 December 2018
Line 162:		Line 162:
	These should go in <code>playbooks/roles/database/</code>.		These should go in <code>playbooks/roles/database/</code>.

	===Database Role Directory Layout===		====Database Role Directory Layout====


	The directory defining how this role works for the playbook will have the following directory structure:		The directory defining how this role works for the playbook will have the following directory structure:
Line 170:		Line 169:
	playbooks/		playbooks/
	roles/		roles/
	~~mezzanine~~/		database/
	defaults/		defaults/
	main.yml		main.yml
Line 179:		Line 178:
	tasks/		tasks/
	main.yml		main.yml
	~~django.yml~~
	~~nginx.yml~~
	templates/		templates/
	~~gunicorn.conf.py.j2~~
	~~local_settings.py.filters.j2~~
	~~local_settings.py.j2~~
	~~nginx.conf.j2~~
	~~supervisor.conf.j2~~
	</pre>		</pre>

Line 196:		Line 188:
	* tasks - defines any tasks run as part of this role (can be divided into multiple files/multiple tasks)		* tasks - defines any tasks run as part of this role (can be divided into multiple files/multiple tasks)
	* templates - defines Jinja templates used for substituting variables into files		* templates - defines Jinja templates used for substituting variables into files




	====Tasks File====		====Tasks File====

2018-12-08T04:45:25Z

Database role

@@ Line 162: / Line 162: @@
 These should go in <code>playbooks/roles/database/</code>.
-The [[Ansible/Directory Layout]] article gives much more detail on the directory structure that should be in place for a playbook; only a single role is covered here.
+===Database Role Directory Layout===
 ====Tasks File====

2018-12-08T04:44:59Z

Files

← Older revision		Revision as of 04:44, 8 December 2018
Line 287:		Line 287:
	All files related to this role should go in <code>playbooks/roles/mezzanine/</code>.		All files related to this role should go in <code>playbooks/roles/mezzanine/</code>.

	====~~Files~~====		====Webapp Role Directory Layout====

			The directory defining how this role works for the playbook will have the following directory structure:

	<pre>		<pre>