Any reason to not have full Docker Compose solution without scripts? (for testing, etc.)

[laimison]

Hey,

What would be the main blocker to implement Docker Compose instead of having install and full-install.sh scripts? So solution will be suitable to test on Mac and Windows laptops, also suitable with orchestration tools as soon as they are fully dockerised. I'm more interested whether it's possible (could be not user friendliest option), but fact whether it's Docker limitation faced or not that I can't think of.

I can see these reasons listed officially at https://help.ubnt.com/hc/en-us/articles/115012196527-UNMS-v1-Installation-Guide:

proper operation - what kind of operations? smooth backups - assume that don't need backup, just wanted to run it or sort out differently upgrades - assume that don't need upgrade, just wanted to run it

Many thanks for this product

[radekskrivan]

Hello @laimison. The current solution is using the installation script in order to create correct docker-compose.yml for UNMS in accordance with the needs of each individual server and user requirements defined by optional install tags (custom certificate, ports, proxy). There are many different edge case scenarios covered within the script (like port availability, free disc space, memory, docker configuration, platform limitations) so that users do not need to deal with them. Plus the script also allows upgrading the UNMS easily from UI.