Ansible playbooks for Digital Ocean host
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Amritanshu Agrawal f26261fb99 Updated the gitea playbook for ssh passthrough. Still not fully there though. 10 months ago
bifrost Bifrost deployed using ansible 2 years ago
bitwarden Updated bitwarden 11 months ago
brewman New: 2 years ago
gitea Updated the gitea playbook for ssh passthrough. Still not fully there though. 10 months ago
grav New: 2 years ago
mongodb Mongodb 2 years ago
nextcloud Added: Readme 2 years ago
postgres Fix: 2 years ago
rabbitmq New: 2 years ago
redis Redis will only listen on the and not remote connections. 11 months ago
snibox New: 2 years ago
trilium Added: Readme 2 years ago
wekan Wekan deployed using ansible 2 years ago
.gitignore Initial rough commit to save the code before cleanup 2 years ago Added: Readme 2 years ago

DO Community - Ansible Playbooks

A collection of minimalist Ansible playbooks for automating server setups, based on DigitalOcean's Community guides.

*the Initial Server Setup should be your starting point for fresh servers.

Playbook Structure

The playbooks contained in this repository were created for educational purposes, and should serve as a base for you to create your own playbooks and roles.

Although we opt to not use roles, our playbooks follow a distinctive structure to facilitate reuse while keeping them mostly self-contained and straightforward.

For instance, this is how the lemp playbook is structured:

├── files
│   ├── info.php.j2
│   └── nginx.conf.j2
├── vars
│   └── default.yml
├── playbook.yml
  • files/: directory containing templates and other files required by the playbook.
  • vars/: directory to save variable files. A default.yml var file is included by default.
  • playbook.yml: the playbook file.
  • instructions and links related to this playbook.

Getting Started

To set up your Ansible environment, please follow our guide on How to Install and Configure Ansible on Ubuntu 18.04.

Connection Test

From your local machine or Ansible control node, run:

ansible all -m ping -u remote_user

If you're able to get a "pong" reply back from your node(s), your setup works as expected and you'll be able to run both ad-hoc commands and playbooks on your nodes, using Ansible.


The following guides cover how to use the playbooks you'll find in this repository.

Initial Server Setup

Once you have executed the initial server setup, you can choose from any of the available server setup playbooks:

Web Servers

Applications & CMSs

Containers & K8s