RynoM/self-hosted-deployment

Using with named volumes

Opened this issue · 1 comments

I´m using named volumes instead of binded mounts. Is it possible to use named volumes instead of binded?

RynoM commented

If you only want to use the deploy.yaml workflow, then i'm pretty sure theres not much difference. I've also been thinking about how this should work with the idea of the backup.yaml workflow, where you want changes made from within the UI of different sevices to be accessible to the actions runner (so it can be committed/pushed). Maybe services where you'd want to do this for should share a named volume (with the runner)? I want to play with this a bit, later, but if you have an idea let me know! :)