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 Ignore Section to Configuration #13

Open
waylonflinn opened this issue May 25, 2016 · 1 comment · May be fixed by #14
Open

Add Ignore Section to Configuration #13

waylonflinn opened this issue May 25, 2016 · 1 comment · May be fixed by #14

Comments

@waylonflinn
Copy link

waylonflinn commented May 25, 2016

When you don't want to delete things in the bucket, just because they don't exist (or look different) locally.

Sometimes you want a set of files to remain on the server even when they don't appear locally. Is there a way to do this with the current configuration file?

I'm imagining something like this:

{
    credentials:"aws-credentials.json",
    bucketName:"example.com",
    patterns:[
        "scripts/*.js",
        "stylesheets/default.css",
        "images/**/*.jpg",
        "index.html"
    ],
    ignores:[
        "users/**"
    ]
}
@waylonflinn waylonflinn changed the title Allow Ignore Section in Configuration Add Ignore Section to Configuration May 25, 2016
@waylonflinn
Copy link
Author

waylonflinn commented May 27, 2016

Working on a PR for this. New config renames patterns to include, and adds an exclude block. Name changes are designed to more closely match rsync.

Here's an example:

{
    credentials:"aws-credentials.json",
    bucketName:"example.com",
    include:[
        "scripts/*.js",
        "stylesheets/default.css",
        "images/**/*.jpg",
        "index.html"
    ],
    exclude:[
        "users/**"
    ]
}

@waylonflinn waylonflinn linked a pull request May 29, 2016 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant