mash-playbook/examples/hosts

# To connect using a non-root user (and elevate to root with sudo later),
# replace `ansible_ssh_user=root` with something like this: `ansible_ssh_user=username become=true become_user=root`.
# If sudo requires a password, either add `become_password=PASSWORD_HERE` to the host line
# or tell Ansible to ask you for the password interactively by adding a `--ask-become-pass` (`-K`) flag to all `ansible-playbook` (or `just`) commands.
#
# For improved Ansible performance, SSH pipelining is enabled by default in `ansible.cfg`.
# If this causes SSH connection troubles, disable it by adding `ansible_ssh_pipelining=False`
# to the host line below or by adding `ansible_ssh_pipelining: False` to your variables file.
#
# If SSH is configured to listen to a non-standard port (i.e. something different than port 22), you need to add `ansible_port=<your configured SSH port>`.
#
# If you're running this Ansible playbook on the same server as the one you're installing to,
# consider adding an additional `ansible_connection=local` argument to the host line below.
#
# Ansible may fail to discover which Python interpreter to use on the host for some distros (like Ubuntu 20.04).
# You may sometimes need to explicitly add the argument `ansible_python_interpreter=/usr/bin/python3`
# to the host line below.

[mash_servers]
<your-domain> ansible_host=<your-server's external IP address> ansible_ssh_user=root
Initial commit 2023-03-15 09:58:12 +01:00			`# To connect using a non-root user (and elevate to root with sudo later),`
Revert "become -> ansible_become" This reverts commit d7d334240ce7f4171218dc4dcca4b2c18c55d69a. This is very confusing and messy.. but it's documented. `ansible_become_` variables actually take priority and override all `become_` variables set at the task level. As such, using `ansible_become=true ansible_become_user=root` in `inventory/hosts` causes issues because tasks that specify `become: OTHER_USER` will be forced to run as `root` due to `ansible_become_user`. 2024-03-26 10:59:05 +01:00			# replace `ansible_ssh_user=root` with something like this: `ansible_ssh_user=username become=true become_user=root`.
			# If sudo requires a password, either add `become_password=PASSWORD_HERE` to the host line
Add note about sudo passwords Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2774 2023-07-01 08:40:19 +02:00			# or tell Ansible to ask you for the password interactively by adding a `--ask-become-pass` (`-K`) flag to all `ansible-playbook` (or `just`) commands.
Initial commit 2023-03-15 09:58:12 +01:00			`#`
			# For improved Ansible performance, SSH pipelining is enabled by default in `ansible.cfg`.
			# If this causes SSH connection troubles, disable it by adding `ansible_ssh_pipelining=False`
			# to the host line below or by adding `ansible_ssh_pipelining: False` to your variables file.
			`#`
Add info regarding the ansible_port varible Since there's already a service (Gitea) which recommends that SSH is changed to be on a non-standard port, it makes sense to add information about how to configure the playbook/Ansible to connect to a non-standard port 2023-05-04 18:26:16 +02:00			# If SSH is configured to listen to a non-standard port (i.e. something different than port 22), you need to add `ansible_port=<your configured SSH port>`.
			`#`
Initial commit 2023-03-15 09:58:12 +01:00			`# If you're running this Ansible playbook on the same server as the one you're installing to,`
			# consider adding an additional `ansible_connection=local` argument to the host line below.
			`#`
			`# Ansible may fail to discover which Python interpreter to use on the host for some distros (like Ubuntu 20.04).`
			# You may sometimes need to explicitly add the argument `ansible_python_interpreter=/usr/bin/python3`
			`# to the host line below.`

			`[mash_servers]`
			`<your-domain> ansible_host=<your-server's external IP address> ansible_ssh_user=root`