You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for what looks like an awesome program.
I would love to see a one-stop docker compose setup file with no other command line steps needed, just deploy the yaml and then straight into the web-ui (ie, the image lives in a docker repo that can be pulled in direct without a manual cloning step). This would make it easier to install directly onto NAS setups that support docker-compose, but don't provide a terminal or limit its use.
Edit: I found a workaround for my use case since my NAS does support Portainer, which has a github repository option. But I'll leave this here in case anyone else has a need not so easily resolved.
The text was updated successfully, but these errors were encountered:
Just an addendum - while Portainer gave some limited success, it wasn't possible for me to add an override docker-compose file because the volume locations are abstracted away from where I can get to them, and just environment variables wouldn't let me do the things I wanted to either because they only cover selected variables (I would have liked to modify the timezone and the volume locations to ones I created to resolve the abstraction issue - out of the box, I can't access the consume folder and can only web upload).
Hi, thanks for what looks like an awesome program.
I would love to see a one-stop docker compose setup file with no other command line steps needed, just deploy the yaml and then straight into the web-ui (ie, the image lives in a docker repo that can be pulled in direct without a manual cloning step). This would make it easier to install directly onto NAS setups that support docker-compose, but don't provide a terminal or limit its use.
Edit: I found a workaround for my use case since my NAS does support Portainer, which has a github repository option. But I'll leave this here in case anyone else has a need not so easily resolved.
The text was updated successfully, but these errors were encountered: