- Delete deprecated CLAUDE.md - Create root-level AGENTS.md for AI assistant guidance - Create SDD constitution in .specify/memory/constitution.md - Align documentation with PARA structure (docs/product/project-brief.md, docs/tech/stack.md, docs/plans/) - Add standardized YAML frontmatter to all documentation files - Update README.md with saTway branding and structure
66 lines
2.0 KiB
Markdown
66 lines
2.0 KiB
Markdown
---
|
|
description: >-
|
|
Infrastructure-as-Code and maintenance repository for Michael Wegener's
|
|
primary workstation at satware AG (Pfeddersheim location).
|
|
tags:
|
|
- workstation
|
|
- ansible
|
|
- infrastructure-as-code
|
|
- linux
|
|
- automation
|
|
last_updated: '2026-03-09'
|
|
---
|
|
|
|
# saTway® Infrastructure - mw-pfeddersheim-workstation
|
|
|
|
This repository manages the configuration, software stack, and maintenance scripts for Michael Wegener's primary workstation. It ensures a reproducible, secure, and optimized environment following **satware AG** best practices.
|
|
|
|
## 🚀 Quick Start
|
|
|
|
To apply the current configuration or run maintenance:
|
|
|
|
```bash
|
|
# 1. Verify configuration with a dry run
|
|
ansible-playbook ansible/workstation.yml --check
|
|
|
|
# 2. Apply configuration locally
|
|
ansible-playbook ansible/workstation.yml
|
|
|
|
# 3. Run automated maintenance
|
|
bash scripts/maintenance.sh
|
|
```
|
|
|
|
## 📂 Project Structure
|
|
|
|
| Directory | Purpose |
|
|
|-----------|---------|
|
|
| `ansible/` | Configuration-as-Code (Roles: `common`, `dev-tools`, `maintenance`) |
|
|
| `config/` | System configuration templates (`.j2`) |
|
|
| `docs/` | PARA-structured documentation (`product`, `adr`, `learnings`, `tech`) |
|
|
| `scripts/` | Maintenance and automation scripts |
|
|
|
|
## 🛠 Software Stack
|
|
|
|
- **Languages**: Node.js 22 LTS, Python 3.12+, PHP 8.4
|
|
- **Automation**: Ansible, Docker
|
|
- **Environment**: Manjaro/Arch Linux, Bash
|
|
|
|
## 📜 Core Principles
|
|
|
|
- **Baby Steps™**: All changes are small, atomic, and verifiable.
|
|
- **Spec-Driven Development**: Intent-first development with explicit documentation.
|
|
- **Zero-Trust**: Secrets are managed via `ansible-vault` or environment variables; never committed raw.
|
|
|
|
## 📄 Documentation
|
|
|
|
Comprehensive documentation is available in the `docs/` directory:
|
|
- [Project Brief](docs/product/project-brief.md)
|
|
- [Setup Guide](docs/tech/setup.md)
|
|
- [Software Stack](docs/tech/stack.md)
|
|
- [Software Audit](docs/tech/current-software-audit.md)
|
|
- [Decision Records](docs/adr/0001-use-ansible-for-configuration.md)
|
|
|
|
---
|
|
|
|
© 2026 satware AG. All rights reserved.
|