You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be good if this could be abstracted out, so that the gem reads the credentials from a file (say ~/.beanstalk) and inserts it automatically
this could be extended if the .beanstalk file could contain multiple auth credentials with something like
Beanstalk::API::Base.setup(
:account => "<an account tag assigned by user>",
)
where the beanstalk file has some kind of structure (maybe yaml) to store domain, user and pass pairs
this would help improve the security of deploy scripts and also allows users to put scripts in version control without exposing auth credentials of a specific user and also allows each user to run api tasks as there user (eg deploys etc)
The text was updated successfully, but these errors were encountered:
We plan to support better authentication method soon, like OAuth or similar, so using login/password for API access soon will become obsolete. In the meantime I'm afraid you will need to store/retrieve the passwords manually with a custom script.
at the moment we have to put the following at the top of any beanstalk API scripts:
it would be good if this could be abstracted out, so that the gem reads the credentials from a file (say ~/.beanstalk) and inserts it automatically
this could be extended if the .beanstalk file could contain multiple auth credentials with something like
where the beanstalk file has some kind of structure (maybe yaml) to store domain, user and pass pairs
this would help improve the security of deploy scripts and also allows users to put scripts in version control without exposing auth credentials of a specific user and also allows each user to run api tasks as there user (eg deploys etc)
The text was updated successfully, but these errors were encountered: