DebOps alternatives and similar software solutions
Based on the "Complete solutions" category.
Alternatively, view debops alternatives based on common mentions on social networks and blogs.
9.2 6.6 L3 DebOps VS Mail-in-a-BoxMail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
9.0 8.7 DebOps VS docker-mailserverA fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) using Docker. [Moved to: https://github.com/docker-mailserver/docker-mailserver]
2.6 8.6 DebOps VS AnsiMailFullstack, security focused mailserver based on OpenSMTPD for OpenBSD using ansible
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of DebOps or a related project?
Your Debian-based data center in a box
The DebOps project provides a set of general-purpose Ansible roles that can be used to manage Debian or Ubuntu hosts. In addition, a default set of Ansible playbooks can be used to apply the provided roles in a controlled way, using Ansible inventory groups.
The roles are written with a high customization in mind, which can be done using Ansible inventory. This way the role and playbook code can be shared between multiple environments, with different configuration in to each one.
Services can be managed on a single host, or spread between multiple hosts. DebOps provides support for different SQL and NoSQL databases, web servers, programming languages and specialized applications useful in a data center environment or in a cluster. The project can also be used to deploy virtualization environments using KVM/libvirt, Docker or LXC technologies to manage virtual machines and/or containers.
You can find out more about DebOps features on the project's documentation page.
Start a Docker container which acts as an Ansible Controller host with DebOps support, based on Debian Buster:
docker run -it --rm debops/debops cd src/controller ; debops run common --diff
Or, create a Vagrant VM which acts as an Ansible Controller host:
git clone https://github.com/debops/debops cd debops && vagrant up && vagrant ssh cd src/controller ; debops run common --diff
You can use configuration in the
src/controller subdirectory to try out
DebOps against the container/VM, or create your own DebOps project directory
debops project init command.
More quick start tips can be found in the DebOps quick start guide.
You can install the DebOps Python package, which includes the DebOps roles and playbooks, as well as additional scripts which can be used to setup separate project directories and run Ansible in a convenient way. To install the Python package with Ansible and other required dependencies, run the command:
pip install --user debops[ansible]
Alternatively, DebOps roles are available on Ansible Galaxy
as an Ansible Collection which can be installed using the
ansible-galaxy collection install debops.debops
Read the installation instructions in the DebOps documentation for more details about required software and dependencies.
Ansible uses SSH to connect to and manage the hosts. DebOps enforces the SSH security by disabling password authentication, therefore using SSH keys to connect to the hosts is strongly recommended. This can be changed using the inventory variables.
During initial deployments you might find that the firewall created by DebOps blocked you from accessing the hosts. Because of that it's advisable to have an out-of-band console access to the host which can be used to login and troubleshoot the connection.
Create a new environment within a DebOps "project directory", add some hosts in the Ansible inventory and run the default DebOps playbook against them to configure them:
# Create a new environment debops project init ~/src/projects/my-environment cd ~/src/projects/my-environment # Modify the 'ansible/inventory/hosts' file to suit your needs, for example # uncomment the local host to configure it with DebOps # Run the full playbook against all hosts in the inventory debops run site # Run the common playbook against specific host in the inventory debops run common -l <hostname>
You should read the Getting Started with DebOps guide for a more in-depth explanation of how the project can be used to manage multiple hosts via Ansible.
Create a fork of this repository and clone it to your workstation. Create a development DebOps environment and symlink the forked repository in it. Now you can create new playbooks/roles in the forked repository and see their results in the development environment.
git clone [email protected]:<username>/debops ~/src/github.com/<username>/debops cd ~/src/github.com/<username>/debops git remote add upstream https://github.com/debops/debops.git debops project init ~/src/projects/debops-devel cd ~/src/projects/debops-devel ln -s ~/src/github.com/<username>/debops debops
You can pull latest changes to the project from the upstream repository:
cd ~/src/github.com/<username>/debops git checkout master git fetch upstream git rebase upstream/master
Read the development guide file for more details about the DebOps development process.
DebOps development is done via a distributed development model. New features and changes are prepared in a fork of the official repository and are published to the original repository via GitHub pull requests. PRs are reviewed by the DebOps developer team and if accepted, are merged in the main repository.
git commits are preferred to ensure authenticity.
Read the contributing guide file for more details about how to contribute to DebOps.
Some files included with the DebOps project use a different license.
The licenses are marked in these files using the SPDX license identifiers
and can be found in the
LICENSES/ subdirectory. They are also included in the
project tarballs, Ansible Collections and Python packages. The project uses the
REUSE Specification and its associated tool to check and
verify copyright and license information in all files.
*Note that all licence references and agreements mentioned in the DebOps README section above are relevant to that project's source code only.