sourcebroker / deployer-extended Goto Github PK
View Code? Open in Web Editor NEWGeneral helper tasks for deployments based on deployer.
License: MIT License
General helper tasks for deployments based on deployer.
License: MIT License
Getting the following error in git bash as well as other consoles.
[Symfony\Component\Process\Exception\ProcessFailedException]
The command "if [ -d .git ]; then echo 'true'; fi" failed.
Exit Code: 1(General error)
Working directory: C:\Laragon\www\deploytest
Output:
================
Error Output:
================
However, running the exact same command in a simple shell script works properly.
Any idea what might cause this?
Thanks!
Hello!
I use your deployer-extended-typo3 package which, in turn, uses this calls cache:clear_php_http
.
In some instances I don't want this to be called - if the site is behind a http auth or if it doesn't have a live URL yet, however the only way I can disable it is by overwriting the whole function with
task('cache:clear_php_http', function () {
});
In the times I don't want it, I don't want to have to redeclare the whole deploy
task to just remove it, so t would be really nice if there could be an option to disable this function or it not throw an error if public_urls
is missing.
Thanks, as always, for all the work!
Complete deployer-extended-typo3 setup works nicely, but only if we remove deploy:check_composer_install
.
# Working run without deploy:check_composer_install
➜ git:(master) ddev exec dep deploy staging
✈︎ Deploying master on staging
✔ Executing task deploy:check_lock
✔ Executing task deploy:check_branch_local
✔ Executing task deploy:check_branch
✔ Executing task deploy:prepare
✔ Executing task deploy:lock
✔ Executing task deploy:release
✔ Executing task deploy:update_code
✔ Executing task deploy:shared
✔ Executing task deploy:writable
✔ Executing task deploy:vendors
✔ Executing task deploy:clear_paths
✔ Executing task db:backup
✔ Executing task buffer:start
✔ Executing task db:truncate
✔ Executing task typo3cms:database:updateschema
✔ Executing task deploy:symlink
✔ Executing task cache:clear_php_cli
✔ Executing task cache:clear_php_http
✔ Executing task buffer:stop
✔ Executing task deploy:unlock
✔ Executing task cleanup
✔ Executing task deploy:extend_log
Successfully deployed!
# Breaking run with deploy:check_composer_install
➜ git:(master) ✗ ddev exec dep deploy staging
✈︎ Deploying master on staging
✔ Executing task deploy:check_lock
➤ Executing task deploy:check_composer_install
✔ Executing task deploy:failed
✔ Executing task deploy:unlock
✔ Executing task deploy:unlock
✔ Executing task deploy:unlock
In deploy_check_composer_install.php line 10:
A composer.lock changes has been detected but you did not run "composer install". Please run composer install, then check if everything is working on your instance and do deploy after.
deploy [-p|--parallel] [-l|--limit LIMIT] [--no-hooks] [--log LOG] [--roles ROLES] [--hosts HOSTS] [-o|--option OPTION] [--] [<stage>]
Failed to execute command dep deploy staging: exit status 1
Local composer --dry-run
output:
# ddev
➜ git:(master) ddev composer install --dry-run
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
# local without ddev (not really preferred way to work)
➜ git:(master) composer install --dry-run
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
We are using composer 2.0.7.
Any idea?
If I have deployer as a dependency of my project and I run it with php vendor/bin/dep db:pull live
these custom recipes are not loaded because function_exists('\Deployer\set')
in src/Autoload.php
returns false...
How it's supposed to work in such situation?
You reference "current" as the folder where the new files are. This fails in a deployer 4.3.1 installation, because the folder is called "release".
PR #13
If you run a deployment, Deployer is checking the deploy.php file in the branch you currently checked out in local GIT. Other branches could have other definition for set branch, which is used for the instance to be deployed.
One could mistakenly deploy a branch which should not be used for this instance currently, because of this. Especially if the one who is about to deploy doesnt know about this (temporary) different branch which is used currently on target instance / machine, he wouldnt doubt to deploy from the branch he was used to use for the target instance.
My suggestion is that on deployment a new task checks which branch is checked out on target server (instance to be deployed to) right now and if it doesnt match the branch which is about to be deployed, give interactive feedback if this is a desired action.
Smth like: "Attention, you are going to deploy branch XY while on the target instance currently branch Z is active. You want to continue?"
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.