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

Allow to ignore files with rsync strategy #380

Closed
davidmpaz opened this issue Feb 20, 2022 · 4 comments
Closed

Allow to ignore files with rsync strategy #380

davidmpaz opened this issue Feb 20, 2022 · 4 comments

Comments

@davidmpaz
Copy link

Hi,

thanks for this awesome roles. May i suggest an improvement? When under ansistrano_deploy_via: "rsync", i have understood from sample application that one can delete some paths after they are synched.

Could we add some variable to modify rysnc filter at sync time? So those paths are not copied only to be deleted later on?

Thanks in advance and cheers,
David

@ricardclau
Copy link
Member

In order to do that you can add a .rsync-filter file to your repo so no extra variables are needed

@davidmpaz
Copy link
Author

Hi @ricardclau,

thanks for your message. In that case could we please document, at least minimal, how this should look like, for dummies like me.

For example, given my scenario, some questions arise for me now. I have a symfony project and all ansistrano related files are placed under an ansible directory in the root of the project.

  1. Shall i place the .rsync-filter file in the project root or one level down where i have my playbooks=

Thanks in advance for your help and ime,
David

@ricardclau
Copy link
Member

@davidmpaz
Copy link
Author

Hi, thanks for your answer. I will check that.

I definitely think the #293 should be addressed in the near future. I can contribute some Pull Request to it if necessary. I am starting to use this repo, this mean I still have that point of view, of dummy, which can be useful for document somethings useful for starting.

These kind of things are trivial, but for someone coming without being too much into the topic it is not so easy to get on track, then having such small details written somewhere, saves everybody's time.

Cheers,
David

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