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: dylancyclone.github.io/…/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
picnicolas@slrpnk.net 20 hours ago
Awesome improvements! Really nice work. I’ll definitely be switching at some point when I have a reason to mess with it. Thanks for all the extra work you’ve done to improve the fork and gift the project to the commons.