Skip to content

provision:website root instead of deployer #3130

@zvxas

Description

@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?

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions