Skip to content
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

[Feature Request] Prompt for 'password' #15

Closed
cfoellmann opened this issue Dec 24, 2014 · 10 comments
Closed

[Feature Request] Prompt for 'password' #15

cfoellmann opened this issue Dec 24, 2014 · 10 comments

Comments

@cfoellmann
Copy link

I would love to use this but it just doesn't work on Windows. My alternative is to run it on the vagrant box (VVV) via ssh. Should be easy, right? NO

A prompt for the password after username would be sooo great.

@stephenharris
Copy link
Owner

Yup the next version will ask for a password. When I first created this I already had the SVN password on my computer, so I never got prompted for it, after I started using a new laptop I found that the task was unable to run because the prompt for a password was being blocked.

As for Windows, I've not got a Windows machine so I'm not able to test it at all but open to pull requests if you're able to offer solution. (Would the issue be related to this issue at all?)

@cfoellmann
Copy link
Author

It doesn't run windows because the execs don't work. I gave up on that.
VVV is always on so I have a Linux machine available but the issue with the password makes it unusable, too.

Would using git svn be a good idea? With that you would be able to the credentials properly

@stephenharris
Copy link
Owner

I've given up on git svn. In any case, my typical set up is using git repo is for development, and svn just for deployment.

I'm about to add the --force-interactive option, and I'm currently working on #2 at the moment.

@atimmer
Copy link

atimmer commented Apr 29, 2015

Any progress on this? Can I help in some way?

@unfulvio
Copy link
Contributor

+1

@stephenharris
Copy link
Owner

Sorry, being meaning to do this for a while. This is (should be) fixed on the develop branch of this repo. If anyone is able to check that out and test it, and verify it works, then I'd be happy to release it.

You would just need to check out the repo and replace the contents of your node_modules/grunt-wp-deploy directory the contents of the repo.

@unfulvio
Copy link
Contributor

thanks @stephenharris this works great for me

@unfulvio
Copy link
Contributor

note: if someone doesn't get it working following 4f981ea as @stephenharris suggested, it's likely you need to update svn to 1.8

@stephenharris
Copy link
Owner

Thanks @Nekojira I'll aim to get this properly released on npm this weekend.

@unfulvio
Copy link
Contributor

Great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants