-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SFTP path and permissions problem #101
Comments
Have you tried adding a trailing slash on the remote path? Is the user with which you're deploying chrooted? Run dandelion with the |
What shell is the deployment user running on? bash? rssh? I've discovered an issue with deploying via SFTP when the deployment user is set to use rssh, but haven't gathered enough data to know if this is an issue with dandelion or Net::SCP. What has worked for me to address this problem is to change the deployment user to use a different shell, such as bash. sudo chsh -s /bin/bash [user] |
I can't reproduce this. I am able to use both a relative and absolute |
Was this ever resolved? I'm getting the exact same issue, also with a project in
Thanks |
Actually, I think setting |
@SteveEdson Not sure. Does Cyberduck or Forklift have an option to preserve permissions as well? It'd be nice to verify that is indeed the issue. |
Cyberduck seems to be able to change the permissions without any issues |
@SteveEdson OK, I'll play around with this a bit. What SFTP server software is the remote machine running? |
Thanks, it's just a standard CentOS box as far as I can tell |
I'm not familiar with CentOS but based on a quick search I'm guessing that means |
I use SFTP to dandelion deploy.
When the path (remote) is set to myapplication (path: myapplication) it works fine.
When the path (remote) is set to /var/www/myapp (path: /var/www/myapp) it fails with a permission error.
However, using Filezilla and SFTP there is no problem uploading to that directory.
The failure so far occurs on a file with "." preceeding the name - such as .gitkeep. I don't know if that has anything to do with it.
The text was updated successfully, but these errors were encountered: