IMHO the worst lack of built in app management, atm, Is the possibility to backup configuration. Or im so dumb that i miss It 
I use HOST path for all apps. Then I use the standard appliance to setup snapshots and replication normally.
I admit, this should be easier but it works.
Forgive me, I was probably unclear, but i was referring (example) to the yaml file when you use custom apps, or to the āapp templateā when you create them via GUI.
With Portainer, i have the snapshot on the volumes (absolutely good practive not use ix path for apps) plus the built in backup function
Inside /mnt/.ix-apps is a file called user_config.yaml
Does that contain app templates? I have no experience what they should look like, I used GUI to add two custom apps and those are in the file + portainer from the apps catalog.
1 Like
i checked and yep, seems like you say! Interesting that on that file there are setup like icon ecc that probably can be personalized
Personally I like Portainer. I install all my applications from Docker compose .yml files in portainer menu stacks.
I just have all my custom compose in github.
yeah, really good tip. Do you use some script to āautomateā the operation, or is just a manual work?
This works well, and then you can clone the directories etc.
If you do that, with perhaps env files for details, then it works better (in my experience) to use raw docker compose, and if youāre doing that, then Dockge is more or less the same.
Canāt use env files with the TrueNAS approach. It also wonāt work if youāre storing data in the stack directory.
And as mentioned, it does make it much harder to backup.
I can very simply replicate my āstacksā dataset.
The arrs, plex and other apps have backup features, I just have extra binds for those folders pointed to another dataset which gets pushed to google drive.
Just manual. Not like Iām making lots of changes to my compose apps once they are running the way I want them to!
1 Like