Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

Client transport options should be configurable #52

Open
agis opened this issue Apr 24, 2018 · 1 comment
Open

Client transport options should be configurable #52

agis opened this issue Apr 24, 2018 · 1 comment
Labels
Milestone

Comments

@agis
Copy link
Contributor

agis commented Apr 24, 2018

The user should be able to specify for example flags passed to rsync and also the source directories.

This was referenced Apr 24, 2018
@agis agis added this to the 1.0 milestone Apr 26, 2018
@agis agis removed the idea label Apr 26, 2018
@agis
Copy link
Contributor Author

agis commented Apr 26, 2018

I think this should be provided for cases where more control over how the transports are used is required. An idea that just popped to mind:

$ mistry build --project foo --transport-command "rsync -avP --delete $source /tmp/foobar"

This way, the user gets full control over the command that's going to be called. The $source part is a variable that we'll parse and substitute with the actual source (eg. mistry.myapp.com:/var/lib/mistry/data/foo/ready/12332).

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

No branches or pull requests

1 participant