deploy-tools
deploy-tools copied to clipboard
INN
Deployment tools for INN's WordPress sites
https://github.com/INN/deploy-tools/blob/f07675ab5de3b0284a4a0d594a20bad8d36a522c/fablib/wp/__init__.py#L268-L277 - [ ] add `env.path` to this get Sample code for this is: https://github.com/INN/deploy-tools/blob/f07675ab5de3b0284a4a0d594a20bad8d36a522c/fablib/wp/maintenance.py#L64 This issue does not affect deploying, and the deploy correctly detects the deployed commit. This...
https://linux.die.net/man/3/libcurl-errors says 3 is: > CURLE_URL_MALFORMAT (3) > The URL was not properly formatted. ``` $ fab staging branch:master verbose deploy [inndev.sftp.wpengine.com] Executing task 'branch' On master [inndev.sftp.wpengine.com] Executing task...
WPE has prod and staging, and also now a "development" environment. What's necessary to deploy there?
https://github.com/INN/deploy-tools/blob/master/fablib/wp/tests.py#L120 installs `WP_VERSION` of the tests, but `WP_VERSION` is set to 3.9.1: https://github.com/INN/deploy-tools/blob/master/fablib/wp/tests.py#L17
This would help to lessen the occurrence of this message: > Fatal error: local() encountered an error (return code 128) while executing 'git tag -af rollback 58896257c1036e46cd7e857f24334df8648b6ad0 -m "rollback tag"'
## Changes - creates a separate paragraph beginning with merging staging to master - minor text updates
This is only really a problem when deploying submodules for the first time, but the workaround is painfully slow. ``` $ fab production master verbose deploy [localhost] Executing task 'production'...
warning: empty strings as pathspecs will be made invalid in upcoming releases. please use . instead if you meant to match all paths This is a warning from `git`: https://github.com/git/git/commit/d426430e6ec2a05bf0a4ee88c319dd607290850...
This is a proposal to, after we transition to Valet for local development, do the following: - [ ] remove example `Vagrantfile` - [ ] remove commands relating to `dev`...