I'd add this on the host definition
host('stagin.example.com')
->stage(STAGE_STAGING)
->set('repository', 'repository1');
host('prod.example.com')
->stage(STAGE_PRODUCTION)
->set('repository', 'repository2');unless, of course, you are deploying to the same host, which I don't know why you would ..
Hey everyone. I've recently started using Deployer and I was quite happy how simple it was to set up and everything was so smooth. Something I thought about from the beginning is how does deployer know the credentials to connect to my host server? In the host configuration, I only set the IP and user.. how does it go with validating the connection? I'm asking because now for some reason I'm getting a: "Permission denied (publickey)" error. Not sure what happened.. but how can I point to the public key I have on my local computer? Thanks in advance
I still can't figure this one out. I feel like the documentation is missing some info regarding this. I don't understand if the error is related with connecting to GIT or my server, but dep ssh gives the same error. I would still like to know how deployer gets the permission to connect with server, I can't find this anywhere on the docs. Please if anyone can help, I would appreciate it a lot.
I'm on an EC2 instance, just in-case anyone is wondering :)
@safazi To deploy to a host that has a jump host in between, I would highly recommend that you setup the ssh jump in your
~/.ssh/config file and use ssh keys. Once this has been done, so that from the command line you can type ssh Host and be sitting at a command prompt of the machine to deploy to, you should be ready to go. Note in ~/.ssh/config on the Host line you can specify one or more names that you can use to ssh in. Host is different than HostName in ~/.ssh/config. For the jump host setup look at the ProxyJump and ProxyCommand lines. Depending on the versions of Open ssh you may or may not be able to use ProxyJump. If not use ProxyCommand and netcat. Something like this: ProxyCommand ssh hostnameoripaddress netcat -w 120 %h %p.
Hi everyone, are the releases down? https://deployer.org/releases/v6.8.0/deployer.phar is not working anymore.
In fact, all inks on https://deployer.org/download/ aren't working anymore
No travis-ci tests!
i created one locally, then uploaded it to my server, and gave it access to my github private repo, but I probably need to do some more configuration work, because even when manually 'git clone'ing, I get an unauthorized
can one have multiple deployment keys on a server for github, and do they have to be created on the server itself?
oh, i just needed to follow this tutorial: https://snipe.net/2013/04/11/multiple-github-deploy-keys-single-server/
Hello everyone, help solve the problem.
My server doesn't update paths for a long time
"\/var\/www\/user\/data\/www\/site\/backend\/releases\/11\/app\/Http\/Controllers"
"\/var\/www\/user\/data\/www\/site\/backend\/current" => "\/var\/www\/user\/data\/www\/site\/backend\/releases\/16\/app\/Http\/Controllers"
the server always sees the earliest version of the remote version
opcache_reset();
- vendor/bin/dep deploy ${CI_ENVIRONMENT_NAME} -f undo.php --tag=$CI_COMMIT_REF_NAME .. also tried --file=undo.php
Also got this errors :/
I asked on stackoverflow a question about an issue that I have with deployer. If anyone has an idea how to fix, I would appreciate some help:
https://stackoverflow.com/questions/65287915/how-to-unlimit-php-deployer-composer-memory
https://stackoverflow.com/questions/65287915/how-to-unlimit-php-deployer-composer-memory
@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 ..
@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');
I have another issue, btw:
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.
Not sure if it is related to deployer or composer or ssh
I am check setting
COMPOSER_PROCESS_TIMEOUT=600
I had this issue with the shared dirrectory, there is a lot files, so I aded this ti the deploy.php file
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.
.. i hope so .. let me check again :D