Committing front-end libraries to git – good practices

I bought popular theme from ThemeForest and I want to use it laravel project. I imported it and it works, but I’m not sure how I’m suppose to handle version control and overall structure.

The whole theme with libraries is about ~200MB and I’m not sure if I’m supposed to just put it in public folder, try to make it work in resources, should I import all JS libraries or only those I use or even if should I commit it to git or make some subrepository and commit there.

  • Restructuring Files in Git Repository
  • Why does git store objects in directories with the first two characters of the hash?
  • Command for viewing overall git status regardless of location in directory
  • SVN: Checkout/export only the directory structure
  • Where is the Git Repository Path created?
  • Git repository structure and modularity
  • What are some good practices to follow?

  • Git - 'Saving' debug statements before removing from code
  • Setting up Git repo with other Git repo with Submodule? (WordPress development)
  • Gitolite local working copy for Apache DocumentRoot
  • Squash commit message in master branch
  • how to ignore .gitignore action when cloning?
  • How can I undo a merge which does not produce a merge commit?
  • 2 Solutions collect form web for “Committing front-end libraries to git – good practices”

    Don’t commit frontend libraries.Instead you can use Bower and only commit the bower.json file and you can do a bower install on your server.

    PS- all this is only possible if you have a dedicated hosting.

    Don’t commit frontend libraries. I adding libraries to .gitignore or just using Bower and only commit the bower.json file.

    Git Baby is a git and github fan, let's start git clone.