Files
mw-pfeddersheim-workstation/README.md
T
ja 72274e0d39 feat(ansible): increase swap to 16GB and apply memory optimizations
- Resized swap file from 4GB to 16GB.
- Configured zswap pool (30%) and THP (madvise) via GRUB.
- Tuned kernel parameters for proactive reclaim and NVMe write-back.
- Integrated systemd-oomd for user slice monitoring.
- Updated documentation and changelog.
2026-03-17 19:02:01 +01:00

2.3 KiB

description, tags, last_updated
description tags last_updated
Infrastructure-as-Code and maintenance repository for Michael Wegener's primary workstation at satware AG (Pfeddersheim location).
workstation
ansible
infrastructure-as-code
linux
automation
2026-03-17

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:

# 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

# 4. Run daily routine (Morning/EOD)
bash scripts/daily-routine.sh morning-full
bash scripts/daily-routine.sh eod

📊 Current Status (2026-03-17)

  • System Health: Healthy (Load: 0.40, Disk: 84% used, Memory: 19% used, Swap: 16GB)
  • Active Containers: 6 running (with memory limits)
  • Network: Tailscale active

📂 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:


© 2026 satware AG. All rights reserved.