https://stackoverflow.com/questions/65287915/how-to-unlimit-php-deployer-composer-memory
@hershkoy change this
set('composer', 'php -d memory_limit=-1 /usr/local/bin/composer');to this
set('bin/composer', 'php -d memory_limit=-1 /usr/local/bin/composer');In Process.php line 1203:
[Symfony\Component\Process\Exception\ProcessTimedOutException]
The process "ssh -A -o ControlMaster=auto -o ControlPersist=60 -o ControlPath=/home/ubuntu/.ssh/deployer_root@123.456.234.123:2222 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@123.456.234.123 'bash -s; printf "[exit_code:%s]" $?;'" exceeded the timeout of 300 seconds.COMPOSER_PROCESS_TIMEOUT=600
set('default_timeout', 1500);
@X-Tender for the custom file I'd try debugging this portion of the code https://github.com/deployphp/deployer/blob/master/bin/dep#L38 .. tbh I'm not sure how it works without trying to run it myself, but I don't have a project with the lastest deployer on hand, so can't test myself ..
When I run it localy on my mac it works via --file undo.php or --file "undo.php" but not in the gitlab env.
Is it possible to use deployer programmatically within the php context? So e.g. hosts configuration can be done dynamically?
I want to use deployer as part of a dynamic multi host php application.
1 reply
2 replies
is_dir(): open_basedir restriction in effect. File(/var/www/site/releases/3/storage/logs) is not within the allowed path(s): (/var/www/site/current/:/usr/lib/php/:/tmp/)site/current but you might want to add just /var/www/site
Hey folks :) I might be looking in a wrong place, but we're having this strange issue. So we have a fairly low-cost dev server, it's a $10 droplet on DigitalOcean. Whenever we run a build (yarn prod) it gets stuck at 95% or 98% emitting. The issue is resolved whenever we add a second core, however I was wondering whether there's some sort of internal timeout in Webpack or Laravel Mix that should be considered? It's difficult to debug, since it could either be CircleCI, or PHP Deployer or Yarn or Webpack or even Mix that's enforcing this, but that's all I have. It timeouts after about 10ish minutes with Error code -1 and causes the entire deploy/build to fail. Thx for any suggestions
Here's pretty much all I can give you in terms of error log - https://privatebin.net/?c99519e31b2de20b#867NEfj9yyHe5R4FzVLquTnu1UsynqFyttKwFgWTiVGe
the stuff inbetween has some sensitive stuff like project name etc. I'm not allowed to disclose :/
It's fine when run locally or when executed on more powerful machine, I'm just trying to figure out where the bottleneck is :) Any help appreciated and thanks!
Hello @all,
I need help to fix my deployer issue,
$ dep deploy production -vv
[localhost] > git rev-parse --abbrev-ref HEAD
✈︎ Deploying HEAD on production.toneart-shop
• done on [production]
➤ Executing task deploy:prepare
[production] > echo $0
➤ Executing task deploy:failed
• done on [production]
✔ Ok [0ms]
➤ Executing task deploy:unlock
[production] > rm -f /var/www/share/websites/toneart-shop.de/.dep/deploy.lock
In Client.php line 103:
[Deployer\Exception\RuntimeException (-1)]
The command "rm -f /var/www/share/websites/toneart-shop.de/.dep/deploy.lock
" failed.
Exit Code: -1 (Unknown error)
Host Name: production
================
Deployer\inventory()
Hi
I'm trying to follow the doc: https://deployer.org/docs/how-to-deploy-laravel.html
but it fails immediately - more or less
My setup:
host webdock.io where I a have a vps
I have a user that can log in with password
I have specified the user in the deploy.php
locally I'm using homestead as dev environment
so if i start the deployment from homestead it simply stops after 10-15 seconds with error code 128
if I run from a terminal
it ask for password, try to connect to github and then fails with code 128
so what am I missing?