Created
February 29, 2016 20:10
-
-
Save krogsgard/98849daa360a23ace811 to your computer and use it in GitHub Desktop.
Having all plugins in Git is a pain. It makes life easier to manage just the plugins I personally maintain in Git.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| .DS_Store | |
| node_modules | |
| .sass-cache | |
| uploads | |
| debug.log | |
| .css.map | |
| themes/* | |
| !themes/poststatus/ | |
| plugins/* | |
| !plugins/poststatus-features/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Otherwise, my repo can easily get messed up with auto updates on live servers, or it's just cumbersome to have Git overflowing with third party plugin updates.
Additionally, commercial plugin licensing is a total pain for single site licenses, so updating is impossible from local if the license is active on live. So you end up doing all sorts of activation and license toggling in order to manage updates to commercial plugins. (Not to mention the annoyance of the license nagging on whichever environment the plugins are not activated)
Instead, I just put them on the live site and periodically deal with commercial plugin updates. If they are small updates, I just do it live, but for major versions, I can clone the site and swap the licensing, manage updates, test, and then repeat on live.
It's super annoying, but better than being locked into a setup where you have to be setup locally and deploy the update for any update at all. All in all, after years of managing updates in Git for third party plugins, I got sick of it.