Exclude vendor folder by default

[benbalter]

Travis CI recently changed the way it vendors gems (with the --development flag), which causes the default build to fail due to conflicts with Jekyll core living in ./vendor/, and thus being processed by Jekyll. Have to imagine putting Gems in vendor is a pretty standard practice, and is only going to become more common place as Jekyll popularity and maturity continues to evolve. (example)

In the vein of sane defaults, and the implied promise that things should Work Out of the Box ™️, let's just add vendor to the exclude list. Alternatively, or in addition, giving that templematic post a real date, or prefixing some folders with _ may also work, although be less ideal.

[parkr]

This is great! Only question is what happens if my site contains a vendor folder on purpose? How do we communicate this new default?

[benbalter]

@parkr RULE WITH AN IRON FIST. NO MERCY.

Nah. Was thinking the same thing after I posted. Perhaps minimized the chances by being more explicit? gem/ruby or gen/bundle or whatever the sub folder(s) normally are?

[parkr]

Is this if you do bundle install --standalone?

[benbalter]

or --deployment or --path /vendor/gems

[parkr]

Would you mind adding a feature test for this to ignore the vendor/gems or whatever? :)

[mattr-]

🤘 👍 🆒

[routelastresort]

Noticed this with Travis, but also heroku: http://markcampbell.me/jekyll/heroku/2013/05/18/how-to-set-up-jekyll-on-heroku.html 👍

[parkr]

We could also add this to our docs somewhere?

[parkr]

Still interested in seeing this happen?

[parkr]

#1847 points us in the right direction for clearing up this mess.

At any rate, will close this as mojombo:master no longer exists.