Composite GitHub Action (Linux runner) for deploying repository content to remote server. Fast and customizable deployment with proxy support. Deploy only changed files or do full sync/mirror of repository content.
The Unlicense
62
stars
14
forks
source link
Change ".deploy-revision" path & delta synchronisation problem #40
I have a question about upload synchronization. Indeed, I have an sFTP that looks like “/public_html” and “/private”. I don't have permission to create folders/files on the “/” root.
When I use your action, it creates a “.deploy-revision” even in “full” synchronization. The problem is that “.deploy-revision” tries to create itself at the root, so it would be interesting to be able to change the path of this file.
Additionally, if I use the delta synchronization action for the first time on a fresh SFTP, I encounter an error indicating that it is unable to "touch .deploy-revision". As a result, I am forced to set the synchronization to "full", which creates the file and allows the upload (I must admit that I do not understand why this is not done automatically in "delta").
That's all from me, thank you again for this action! Have a great day!
Hey,
I have a question about upload synchronization. Indeed, I have an sFTP that looks like “/public_html” and “/private”. I don't have permission to create folders/files on the “/” root.
When I use your action, it creates a “.deploy-revision” even in “full” synchronization. The problem is that “.deploy-revision” tries to create itself at the root, so it would be interesting to be able to change the path of this file.
Additionally, if I use the delta synchronization action for the first time on a fresh SFTP, I encounter an error indicating that it is unable to "touch .deploy-revision". As a result, I am forced to set the synchronization to "full", which creates the file and allows the upload (I must admit that I do not understand why this is not done automatically in "delta").
That's all from me, thank you again for this action! Have a great day!