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

Add ability to include or exclude paths #27

Closed
yoiang opened this issue Apr 3, 2018 · 7 comments
Closed

Add ability to include or exclude paths #27

yoiang opened this issue Apr 3, 2018 · 7 comments

Comments

@yoiang
Copy link
Member

yoiang commented Apr 3, 2018

If include is used then only collections and documents that match include and do not match exclude are backed up

@lewchuk
Copy link

lewchuk commented May 2, 2018

I'm thinking that supporting an excludePattern parameter might be a good way to solve this problem. The would let you be pretty exact in the exclusion. Given a setup like:

/organizations - collection
  /org-1 - document
    /messages - sub collection
    /backup
  /org-2
    /messages
    /backup
/other
  • Exclude top level collection: ^/other
  • Exclude sub collections of all documents: ^/organizations/[^/]*/backup
  • Exclude a particular document: ^/organizations/org-2

Thoughts?

@yoiang
Copy link
Member Author

yoiang commented May 4, 2018

excludePattern is part of what I was imagining! Supporting exclude and include patterns gives people a more concise way to achieve certain subsets. It also speaks to a wider range of ways to visualize one's backup for people who think easier one way vs another.

@yoiang
Copy link
Member Author

yoiang commented May 5, 2018

Closing thanks to @lewchuk 's contribution in #31 and in favor of the more concise issue #37

@yoiang yoiang closed this as completed May 5, 2018
@lewchuk
Copy link

lewchuk commented May 7, 2018

@yoiang What is the schedule for getting a new npm package version published? Is there anything I can do to help that process?

@yoiang
Copy link
Member Author

yoiang commented May 8, 2018

I was hoping to release when some dependency issues were resolved (#34), but it isn't clear when that is getting resolved.

Let me push up a new release!

@lewchuk
Copy link

lewchuk commented May 9, 2018

Thanks @yoiang!

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

No branches or pull requests

2 participants