Ansible - Revision history

AliIybar: /* Templates */

2026-04-01T09:15:10Z

‎Templates

2026-04-01T09:14:07Z

‎Using template in playbook and variables

2026-04-01T09:13:10Z

2026-03-31T07:59:55Z

2026-03-30T11:55:35Z

‎Interactive prompts

2026-03-30T11:55:17Z

2026-03-30T11:11:10Z

2026-03-30T10:37:42Z

‎Vault

2026-03-30T10:23:54Z

‎Hosts

2026-03-30T10:19:48Z

@@ Line 105: / Line 105: @@
 = Templates =
-Create "templates" folder in the root.
+Create "templates" folder in the root. When we use them in playbook templates are relative to playbook path.
 Template files have the extension of .j2

@@ Line 145: / Line 145: @@
    tasks:
 </pre>
 or we can pass them from cli like
 = Key base Authentication =

← Older revision		Revision as of 09:13, 1 April 2026
Line 104:		Line 104:
	when: ansible_distribution == "Ubuntu" and ansible_distribution_version == "24.0"		when: ansible_distribution == "Ubuntu" and ansible_distribution_version == "24.0"

		+	= Templates =
		+	Create "templates" folder in the root.
		+
		+	Template files have the extension of .j2
		+
		+	Variables used in moustache format.
		+	== Example template for nginx site ==
		+	<pre>
		+	site_name = {{ site_name}}
		+	server {
		+	listen 80;
		+	server_name {{ site_name}}.{{ site_type}}.bookitfor.me.uk;
		+
		+	location / {
		+	proxy_pass http://localhost:{{ internal_port }};
		+	proxy_http_version 1.1;
		+
		+	proxy_set_header Upgrade \$http_upgrade;
		+	proxy_set_header Connection 'upgrade';
		+	proxy_set_header Host \$host;
		+
		+	proxy_set_header X-Real-IP \$remote_addr;
		+	proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
		+	proxy_set_header X-Forwarded-Proto \$scheme;
		+
		+	proxy_cache_bypass \$http_upgrade;
		+	}
		+	}
		+	</pre>
		+	== Using template in playbook and variables ==
		+	variables can be defined in playbook before tasks like
		+	<pre>
		+	- name : Site creation
		+	hosts: all
		+	become: true
		+	vars:
		+	site_name: somesite
		+	site_type: api
		+	internal_port: 3001
		+	tasks:
		+	</pre>
		+	or we can pass them from cli like

	= Key base Authentication =		= Key base Authentication =

@@ Line 190: / Line 190: @@
 == Pass vairables via CLI ==
   ansible-playbook playbook.yml -e "domain_name=example.com email=test@example.com"
 = Tips =

@@ Line 188: / Line 188: @@
      default: "example.com"
 </pre>
-== Pass vairables vis CLI ==
+== Pass vairables via CLI ==
   ansible-playbook playbook.yml -e "domain_name=example.com email=test@example.com"

@@ Line 159: / Line 159: @@
 logicmade ALL=(ALL) NOPASSWD: ALL
 </pre>
 = Tips =

← Older revision		Revision as of 11:11, 30 March 2026
Line 205:		Line 205:

	aws_access_key_id is a key in the vault.		aws_access_key_id is a key in the vault.
		+	=== Vault Password File ===
		+	Choose a location outside your repo, e.g.:
		+	<pre>
		+	mkdir -p ~/.ansible
		+	echo "MySuperSecretVaultPassword" > ~/.ansible/.vault_pass
		+	chmod 600 ~/.ansible/.vault_pass
		+	</pre>
		+
		+	Create vault with password file
		+	ansible-vault create playbooks/vault_aws.yml --vault-password-file ~/.ansible/.vault_pass
		+
		+	Run your playbook using the password file
		+	ansible-playbook -i inventory/hosts playbooks/install_aws.yml \
		+	--vault-password-file ~/.ansible/.vault_pass

@@ Line 165: / Line 165: @@
 * No blank lines
-* No special characters like (+)
+* No special characters in password like (+)
 * In playbook it's relative to playbook's folder.
 like :

@@ Line 41: / Line 41: @@
 [database_servers]
 .168.1.204
 </pre>
 Test it by

@@ Line 32: / Line 32: @@
 == Hosts ==
 Add / update servers to ./inventory/hosts file with either name or ip addresses
 Test it by
@@ Line 43: / Line 50: @@
 '''servers''' is the name of the group in hosts
 '''logicmade''' is the username
 == Playbooks ==
@@ Line 53: / Line 81: @@
 ansible-playbook ./playbooks/apt.yml --user logicmade --ask-pass --ask-become-pass -i ./inventory/hosts
 </pre>
 = Key base Authentication =