at the moment we have to put the following at the top of any beanstalk API scripts:
Beanstalk::API::Base.setup(
:domain => "subdomain",
:login => "username",
:password => "password"
)
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)
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)