• 1 Post
  • 2 Comments
Joined 4 days ago
cake
Cake day: November 13th, 2025

help-circle
  • This is definitely inspired by ansible-nas! I’d also used it for awhile, and made my own fork to add/fix things since the project has gone a little dormant. I started making so many changes though that I started fresh and it turned it into a whole project of it’s own. You can see a list of differences here: https://dylancyclone.github.io/ansible-homelab-orchestration/guides/introduction/

    Or copy-pasted:
    • Does not require root to run
    • Runs containers with minimum privileges (no root unless absolutely necessary)
    • Allow any application to have it’s name, image name and version overridden (in case of version pinning or running forks)
    • Does not modify existing system settings/configuration
    • Separates DNS access from external access (for example, access portainer.example.com on local network without exposing it to the internet)
    • Notifies the user of breaking changes in an application’s ansible role before updating them
    • Everything is optional, doesn’t install anything except what’s configured by the user
    • Cleans up networks and containers more gracefully after disabling applications, and ensure nothing is left dangling
    • Supports more OSs than just Ubuntu
    • Includes suite of tests to ensure clean code and functionality
      • All created containers and networks are removed when stopping applications
      • Ensures all applications have consistent variable names and settings
      • Ensures all applications properly implement DNS and external access settings
      • Ensures no port conflicts between applications
      • etc