-
Notifications
You must be signed in to change notification settings - Fork 4
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
Caching username and password and general usage #2
Comments
You can see my example project here at bradical/cascade-grunt-tests@f3bf53f |
I've avoided caching the credentials for security reasons. I could modify the code so that the options would include the ability to pass in authentication from the calling code. This would put the burden of storing the credentials back at the grunt level. Where I'm using it I make a single call with all of the files I want to send and that avoids having to reenter credentials multiple times. The other place I access Cascade I do store the credentials: https://github.com/jraller/cascade-access-tool |
Got it. That makes sense. Thanks! On Thu, Oct 15, 2015 at 11:30 AM Jason Aller [email protected]
|
I feel guilty that I did not check this out earlier but this very cool. Thanks for building.
I had a couple of questions. I noticed that when I run
grunt cascadeDeploy
it asks me for creds.Again, thanks for building. This is a really great example of how you can manage source code externally in Git and then push to Cascade with webservices.
The text was updated successfully, but these errors were encountered: