Agentless configuration management and provisioning over plain SSH, described in readable YAML. This walkthrough covers the mental model and the configuration you will actually touch.
Ansible configures servers and orchestrates deploys using idempotent 'playbooks' - YAML that describes desired state and runs over SSH with no agent to install on the targets.
The configuration that matters
A playbook that installs and enables nginx idempotently.
- hosts: web
become: true
tasks:
- name: Install nginx
ansible.builtin.package:
name: nginx
state: present
- name: Ensure nginx is running and enabled
ansible.builtin.service:
name: nginx
state: started
enabled: true
- name: Deploy site config
ansible.builtin.template:
src: site.conf.j2
dest: /etc/nginx/conf.d/site.conf
notify: reload nginx
handlers:
- name: reload nginx
ansible.builtin.service: { name: nginx, state: reloaded }Principles to hold onto
- Prefer modules over raw shell; add changed_when/creates to shell tasks
- Structure logic into roles and use group_vars/host_vars
- Encrypt secrets with Ansible Vault and keep the key out of the repo
Everyday commands
ansible-playbook -i inventory.ini site.yml --check # dry run
ansible-playbook -i inventory.ini site.yml --diff
ansible-vault encrypt group_vars/prod/secrets.ymlWant senior help putting Ansible to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.