Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using with named volumes #2

Open
Akruidenberg opened this issue Apr 23, 2023 · 1 comment
Open

Using with named volumes #2

Akruidenberg opened this issue Apr 23, 2023 · 1 comment

Comments

@Akruidenberg
Copy link

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

@RynoM
Copy link
Owner

RynoM commented Apr 23, 2023

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! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants