Base option ignored during deploy

[trst]

I am trialing using phploy for our deployment process and everything's a dream so far (thank you for your hard work!). The only trouble I'm having is with the 'base' option which appears to be ignored during deploy.

My company keeps their applications in large mono-repos, and in the particular test example I'm using, a WordPress install is included inside of a folder (cleverly named, 'wordpress/'). I set base = 'wordpress/' in the config, yet it begins uploading from the parent working directory (where the composer files are located).

I'll include the config file below which I generated using the phploy --init command.

Any thoughts on where I should be looking for the solution?

[staging]
    scheme = ftp
    host = HOST
    path = public_html/some-folder
    user = 'USERNAME'
    pass = 'PASSWORD'
    base = 'wordpress/'

[Liingon]

@trst Have you downloaded PHPloy from github or did you use composer? If I remember correctly this should be fixed already, but Packagist is not updated so composer doesn't get the latest changes.

[trst]

Thanks for the info. I haven’t tried from github yet but is there any update on composer updates? I have no problem going to the source repo but a few of teammates are a little less confidence navigating the file tree, setting executables, etc. They do have some experience with composer so that’s why I ask.

…

On Oct 21, 2019, 6:42 AM -0600, Jesper Ekstrand ***@***.***>, wrote: @trst Have you downloaded PHPloy from github or did you use composer? If I remember correctly this should be fixed already, but Packagist is not updated so composer doesn't get the latest changes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Jelmerkeij]

I'm having the same problem and I can confirm it works when I use the Github repo but not with Composer.

When will Composer be updated? Sorry, I do not have any knowledge on how/when packagist gets their updates. But the version number in Github and Packagist (both version 4.9.1) seem the same so I wonder why this is.

Thanks!

[Liingon]

@banago Could you make please update the package on Packagist? It would be nice to be able to get the latest changes with composer.