Infrastructure for status.forgejo.dev https://status.forgejo.dev
Find a file
2024-05-25 12:56:05 +02:00
inventory Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
roles Adds monitors for CI + S3 services 2024-05-25 12:56:05 +02:00
vars Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
.ansible-lint Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
.gitignore Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
ansible.cfg Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
playbook.yaml Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
README.md Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
ssh.yaml Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00
uptime-kuma.yaml Adds a first draft for status.forgejo.dev 2024-05-25 12:49:50 +02:00

status.forgejo.dev DevOps

Automation to create/configure the infrastructure for all services related to status.forgejo.dev.

Prerequisites

This project depends on an existing monitoring server available at status.1uhosting.de.

Setup (client/workstation)

  • Install all dependencies:
  • Copy vars/uptime-kuma.yml.example to vars/uptime-kuma.yml
    • Replace the dummy values with the real ones

Ansible

Ansible is used to configure the VMs and create/configure all necessary services.

  • To create/configure/update all services on the VMs, simply run:
    • $ export ANSIBLE_CONFIG=./ansible.cfg
    • $ ansible-playbook playbook.yaml

Limit Ansible to specific hosts only

  • To create/configure/update all services only on ony specific VM, run:
    • $ export ANSIBLE_CONFIG=./ansible.cfg
    • $ ansible-playbook playbook.yaml --limit status

Ansible Lint

  • Installation: $ pip3 install ansible-lint
  • Usage: $ ansible-lint --offline -p ./*.yml