POST-Deploying multiple jekyll sites at once

blog.bryanroessler.com/_config.yml

@@ -174,16 +174,11 @@ link-tags: true
 
 # Exclude these files from production site
 exclude:
-  - Gemfile
-  - Gemfile.lock
-  - node_modules
-  - vendor/bundle/
-  - vendor/cache/
-  - vendor/gems/
-  - vendor/ruby/
   - CHANGELOG.md
   - CNAME
   - Dockerfile
+  - Gemfile
+  - Gemfile.lock
   - LICENSE
   - README.md
   - Vagrantfile

blog.bryanroessler.com/_posts/2018-12-03-deploying-multiple-jekyll-sites.md

@@ -56,7 +56,7 @@ exit 0
 
 Although the process is straightforward, carrying out those steps repeatedly for multiple subdomains or websites can quickly become tedious.
 
-For larger websites, I prefer using nested git repositories to simplify website deployment. This strategy used to be poorly supported in git and most IDEs, but recently they've gained wider support. A nested git repository works just as one would expect: a nested git repository (what I refer to as a subgit) can contain its own settings (for instance, pointing at upstream branches) while residing within a parent git repository that can be used to backup and deploy *en masse*. This is very helpful because the subgit can be managed independently from other portions of the website. For example, upstream changes can be merged into the subgit site without disturbing the state of the other git repositories.
+For larger websites, I prefer using nested git repositories to simplify website deployment. This strategy used to be poorly supported in git and most IDEs, but recently they've gained wider support. A nested git repository works just as one would expect: a nested git repository (what I refer to as a subgit) can contain its own settings (for instance, pointing at upstream branches) while residing within a larger git repository that can be used to backup and deploy *en masse*. This is very helpful because the subgit can be managed independently from other portions of the website. For example, upstream changes can be merged into the subgit site without disturbing the state of the other git repositories.
 
 By combining the subgit strategy with some structured naming conventions it is possible to push, build, and deploy multiple subdomains or sites using a single git push from the client!