Ansible Anon Relay Configuration

Aider configuration for an Ansible playbook project that deploys Anyone Network anonymous relay infrastructure. This configuration enforces best practices for Ansible development including linting, idempotent task design, and comprehensive documentation.

What This Configuration Does

This Aider configuration is optimized for developing and maintaining Ansible playbooks with a focus on:

Configuration Details

Model Settings

Linting & Quality

Context Files

Always loaded for AI context:

Ansible-Specific Guidelines

The configuration enforces these patterns:

1. **Idempotency**: All tasks must be safely re-runnable

2. **Variable Namespacing**: Use `anon_` prefix for project variables

3. **Native Modules**: Prefer Ansible modules over shell commands

4. **Error Handling**: Implement block/rescue patterns

5. **Documentation**: Document all variables in `defaults/main.yml`

6. **Multi-distro Support**: Test on Ubuntu, Debian, and Fedora

7. **Secrets Management**: Use Ansible Vault for sensitive data

Usage Instructions

Basic Usage

Start Aider with the configured settings:

```bash

aider

```

The configuration file (`.aider.conf.yml`) will be automatically loaded.

Edit Specific Files

Work on specific playbook components:

```bash

aider site.yml roles/docker_setup/tasks/main.yml

```

With Additional Context

Load extra context files:

```bash

aider --read group_vars/all.yml roles/relay/tasks/main.yml

```

Lint and Commit Workflow

1. Make changes to your Ansible files through Aider

2. Aider automatically runs `ansible-lint` on changed files

3. If linting passes, changes are committed with descriptive messages

4. If linting fails, fix issues before commit

Testing Changes

Validate playbook syntax:

```bash

ansible-playbook site.yml --syntax-check

```

Run lint manually:

```bash

ansible-lint --profile=production

```

Project-Specific Workflow

When working on this Ansible project:

1. **Read Documentation First**: Check AGENTS.md and CLAUDE.md for standards

2. **Ensure Idempotency**: All tasks must handle repeated runs gracefully

3. **Test Thoroughly**: Run syntax checks and linting before committing

4. **Document Changes**: Update CHANGELOG.md with notable modifications

5. **Multi-distro Testing**: Verify compatibility with Ubuntu, Debian, and Fedora

Example Scenarios

Adding a New Role

```bash

aider --read AGENTS.md "Create a new role for configuring UFW firewall with default deny incoming, allow outgoing, and allow SSH on port 22"

```

Refactoring Existing Tasks

```bash

aider roles/docker_setup/tasks/main.yml "Refactor to use community.docker collection instead of shell commands"

```

Debugging Playbook Issues

```bash

aider --read site.yml --read inventory.ini "The docker role fails on Fedora hosts, fix compatibility issues"

```

Configuration Customization

You can override settings by editing `.aider.conf.yml` or using command-line flags:

Important Notes

Best Practices

1. Always review diffs before accepting changes

2. Test playbooks in a non-production environment first

3. Use Ansible Vault for secrets, never commit plaintext credentials

4. Keep roles focused and reusable

5. Document all non-obvious decisions in comments

6. Use tags for selective playbook execution

7. Implement check mode support (`--check`) in custom modules