kevinveenbirkenbachandClaude Opus 5
4986e80dd4
The Production block never set one. inventory provision writes only
ansible_connection for a local host, so DOMAIN_PRIMARY stayed at the
group_vars default of infinito.localhost and the deployment served a zone its
own resolver knows nothing about. CoreDNS templates answers for
INFINITO_DOMAIN_RE and nothing else, so every lookup of the deployment's own
name came back NXDOMAIN.
Mastodon is where that surfaced. tootctl accounts create validates the address
through EmailMxValidator, which resolves MX and then, for the domain itself,
A and AAAA. All six queries returned NXDOMAIN in run 33574056480, the
validator recorded email :unreachable, and the admin account was never created.
Only the guide rows were affected: the matrix rows write
DOMAIN_PRIMARY: "{{ lookup('env', 'INFINITO_DOMAIN') }}" into their host_vars
and resolve fine.
The template now carries DOMAIN=<your-domain> in both the host and the
container form and threads it into --vars, with the container form passing it
through the docker run boundary as well. The two guide runners substitute it
the way they already substitute the SSH key, so the replay deploys under
INFINITO_DOMAIN like every other CI deploy. compose_deploy.sh moves its env
load ahead of the substitutions to have the value; host_deploy.sh had no env
load at all.
A production reader is asked for a domain now instead of silently inheriting
infinito.localhost, which no real deployment wants either. The shipped default
keeps its value: sys-svc-nss documents that *.localhost resolves through the
myhostname NSS module without any zone, and host-side tasks lean on it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
5.7 KiB
MariaDB
Description
The Docker MariaDB Role offers an easy and efficient way to deploy a MariaDB server inside a Docker container. Manage your data securely and effectively, making it ideal for production or local development.
Overview
This Ansible role facilitates the deployment of a MariaDB server using Docker. It is designed to ensure ease of installation and configuration, with the flexibility to adapt to different environments.
Cosmos
The diagram places MariaDB in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph deps [Dependencies]
dep_svc_bkp_volume_2_local["svc-bkp-volume-2-local 💻"]
dep_svc_net_tor["svc-net-tor 🐳🐝"]
end
subgraph role [svc-db-mariadb 🐳🐝]
svc_mariadb["mariadb"]
svc_tor["tor"]
svc_container_backup["container_backup"]
end
subgraph dependents [Dependents]
dpt_web_app_akaunting["web-app-akaunting 🐳🐝"]
dpt_web_app_erpnext["web-app-erpnext 🐳🐝"]
dpt_web_app_espocrm["web-app-espocrm 🐳🐝"]
dpt_web_app_friendica["web-app-friendica 🐳🐝"]
dpt_web_app_gitea["web-app-gitea 🐳🐝"]
dpt_web_app_joomla["web-app-joomla 🐳🐝"]
dpt_web_app_mailu["web-app-mailu 🐳🐝"]
dpt_web_app_matomo["web-app-matomo 🐳🐝"]
dpt_web_app_mediawiki["web-app-mediawiki 🐳🐝"]
dpt_web_app_moodle["web-app-moodle 🐳🐝"]
dpt_web_app_nextcloud["web-app-nextcloud 🐳🐝"]
dpt_web_app_phpmyadmin["web-app-phpmyadmin 🐳🐝"]
dpt_more["..."]
end
dep_svc_bkp_volume_2_local -. "0..1" .-> svc_container_backup
dep_svc_net_tor -. "0..1" .-> svc_tor
svc_mariadb -- "1:1" --> dpt_more
svc_mariadb -. "0..1" .-> dpt_web_app_akaunting
svc_mariadb -. "0..1" .-> dpt_web_app_erpnext
svc_mariadb -. "0..1" .-> dpt_web_app_espocrm
svc_mariadb -. "0..1" .-> dpt_web_app_friendica
svc_mariadb -. "0..1" .-> dpt_web_app_gitea
svc_mariadb -. "0..1" .-> dpt_web_app_joomla
svc_mariadb -. "0..1" .-> dpt_web_app_mailu
svc_mariadb -. "0..1" .-> dpt_web_app_matomo
svc_mariadb -. "0..1" .-> dpt_web_app_mediawiki
svc_mariadb -. "0..1" .-> dpt_web_app_moodle
svc_mariadb -. "0..1" .-> dpt_web_app_nextcloud
svc_mariadb -. "0..1" .-> dpt_web_app_phpmyadmin
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Features
- Dockerized MariaDB: Leverages Docker for MariaDB deployment, ensuring consistency across different environments.
- Customizable Settings: Allows customization of the MariaDB instance through various Ansible variables.
- Network Configuration: Includes setup of a dedicated Docker network for MariaDB.
- Idempotent Design: Ensures that repeat runs of the playbook do not result in unwanted changes.
- Security Focused: Implements best practices for securing the MariaDB root password.
Quick Setup
Development
Clone, set up the workstation, and deploy MariaDB onto the local stack:
git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=svc-db-mariadb full_cycle=false
Production
Run the published image to provision the inventory and deploy MariaDB to a managed server (the mounted volume persists the inventory):
APP=svc-db-mariadb
HOST=<your-server>
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
docker run --rm -it \
-v "$PWD/inventories:/etc/infinito.nexus/inventories" \
-e APP="$APP" -e HOST="$HOST" -e DOMAIN="$DOMAIN" -e TLS_MODE="$TLS_MODE" -e SSH_PUBLIC_KEY="$SSH_PUBLIC_KEY" \
ghcr.io/infinito-nexus/core/debian bash -c '
INVENTORY=/etc/infinito.nexus/inventories/production
infinito administration inventory provision "$INVENTORY" \
--inventory-file "$INVENTORY/devices.yml" \
--host "$HOST" \
--include "$APP" \
--vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}" &&
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
--password-file "$INVENTORY/.password" \
--diff -vv'
Prerequisites
Before using this role, ensure you have the following:
- Ansible installed on the control machine.
- Docker installed on the target host(s).
- Access to the target host(s) via SSH.
Configuration
Configure the role by setting the required variables. These can be set in the playbook or in a separate variable file:
central_mariadb_root_password: The root password for the MariaDB server.database_name: The name of the initial database to create.database_username: The username for the database user.database_password: The password for the database user.
Contributing
Contributions to this project are welcome. Please submit issues and pull requests with your suggestions.
Further Resources
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).