Dependency & Asset Check ins

The goal of this page is to help shed light on the .gitignore file in Drywall and how you should modify it for your project. Specifically during your deployments.

Overview

The Drywall project is a boilerplate, not a deployed application. So when we develop for Drywall [the boilerplate code] we ignore (don't check-in to git) the config.js file, external node_modules and the minified css/js assets.

Update Your .gitignore

Unless you're contributing to Drywall itself, you should clear your .gitignore file. Start with an empty slate and only ignore stuff necessary for your project.

Be sure to commit dependencies and minified public assets to your code base. This stuff is part of your app now. Also, it will make your deployments faster/better/stronger.

Why Should I Check-in These Files?

https://docs.npmjs.com/misc/faq#should-i-check-my-node_modules-folder-into-git

Check node_modules into git for things you deploy, such as websites and apps.

Do not check node_modules into git for libraries and modules intended to be reused.

Use npm to manage dependencies in your dev environment, but not in your deployment scripts.

Further Reading

• Checkout Mikeal Rogers' post on the subject; node_modules in git
• On Stack Overflow; Should I check in node_modules to git when creating a node.js app on Heroku?
• Addy Osmani's post; Checking in front-end dependencies

Use the Force

I hope this was helpful. If you have questions or think this page should be expanded please contribute by opening an issue or updating this page.