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

Excluding static files? #3

Open
artob opened this issue Sep 15, 2010 · 2 comments
Open

Excluding static files? #3

artob opened this issue Sep 15, 2010 · 2 comments

Comments

@artob
Copy link

artob commented Sep 15, 2010

Is there a way to exclude certain static files being synced, using wildcard matching for example?

An issue I've been seeing is that if I e.g. edit my robots.txt, my editor will leave a robots.txt~ backup file lying around; as I'm sure you know, this is a fairly common convention in shell-based editors. Unfortunately, that backup file then gets copied to .html/robots.txt~ when I do a markdoc build. Not that it's a huge problem, but it is a little annoying.

If the build process ignored ~ files, that'd solve the specific issue above. But even more useful (if wishes were horses) would be the ability to exclude patterns of files, including then "*~". This would come very handy in repositories where the static files are located directly on the top level, meaning that some extraneous non-static files get copied in the build process as well, particularly README.md and Rakefile in my typical use cases.

I bet you've already thought of this, and I have just overlooked it in the documentation ;-)

@zacharyvoase
Copy link
Owner

I’ve figured out the perfect solution; it’ll be landing in the code shortly. See the documentation for rsync’s --cvs-exclude option here. It’ll be on by default, with the option to switch it off in your markdoc config.

All editor backup files will be ignored, and you’ll be able to use .cvsignore files to exclude specific files/patterns.

@artob
Copy link
Author

artob commented Sep 17, 2010

All right, sounds perfect - thank you, and looking forward to it :-)

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