provision:website root instead of deployer

[zvxas]

• Deployer version: dev
• Deployment OS: ubuntu 20.04 lts

Problem with "provision:website" task, remote_user gets set to deployer:

set('remote_user', 'deployer');

but $publicPath is still /root/test. Caddyfile gets put to /root/test/Caddyfile, caddy can't read that file and it fails to restart.
In deploy.php I set "deploy_path" to "~/test".
Setting deploy_path to "/home/deploy/test" instead everything works fine.

What's the expected behaviour? I suppose everything should be done through deployer, NOT root?

[antonmedv]

This is strange. Yes, website should be done via deployer user. Can you show output of dep config command?

[rabol]

task provision:website
[compudesign.vps.webdock.cloud] error in website.php on line 73:
[compudesign.vps.webdock.cloud] run cd /root/cdesign && (if grep -q 'import /root/cdesign/Caddyfile' /etc/caddy/Caddyfile; then echo +precise; fi)
[compudesign.vps.webdock.cloud] err root@compudesign.vps.webdock.cloud: Permission denied (publickey).
[compudesign.vps.webdock.cloud] exit code -1 (Unknown error)
ERROR: Task provision:website failed!

[rabol]

line 72 in website.php looks like this:

set('remote_user', 'root');

not sure why, but that could be the issue ?

[antonmedv]

The problem is: why deploy path is /root/test