-
Notifications
You must be signed in to change notification settings - Fork 18
[RFC] Update node + dependencies #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
EvanK
wants to merge
71
commits into
master
Choose a base branch
from
89-update-dependencies
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
* SO MANY generator changes * dependency checking now supports regex-style version checks * on end, runs npm install rather than bower * rewrote existing prompt checks that relied on bower.json * for fetching wordpress, invokes postinstall rather than bootstrapping a bower.json * replaced hand-cobbled wp version checking with modified semver wrapper * Rewrote postinstall for npm * Removed templates for bower.json and .bowerrc * Added template for package.json * Added wp version to ansible group vars
* Updated travis yml * Removed bower * Updated to latest ansible (2+) * Updated ansible playbooks * Removed bower * Updated lookup plugin * Updated node install to 4.x * Removed apache 2.2 tasks (no longer needed for travis testing) * Updated capistrano * Updated README and other docs
Conflicts: package.json
Conflicts: bin/import lib/ansible/lookup_plugins/nested_dict.py lib/yeoman/index.js lib/yeoman/templates/README.md package.json
* updated postinstall to drop admzip and use yauzl instead * updated generator, fixed: * npm install (needed to be under `install` block) * prompting updated (to use promise-style from yeoman 1.8+) * updated package.json for publishing (local testing for now with sinopia) Also worth noting that this will require an updated node to 4.x and yeoman to 1.8
Fixes another SNI failure when the remote has an older python
EvanK
added a commit
to evolution/wordpress-example
that referenced
this pull request
Nov 6, 2016
55991d1 to
1ffa75c
Compare
This will globally install bower on the remote server, but only do a bower install on deploy _when a bower.json_ is found as part of the deploying project.
Note: we're skipping 2.0 in the CI environment because Travis' trusty image comes bundled with python 2.7.6, which lacks baked-in SNI support
1f2cefa to
573866c
Compare
Effectively the same as the `within` notation, but this is more explicit and easier to understand, IMHO
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A more comprehensive list of changes done and TBD:
sudodirectives withbecome