> Hello, > Could I restrict acces to benstalk by username and password and create > one central benstalk server for my other machines?
Unfortunately you can't. A workaround is to wrap beanstalkd with something like stunnel or another SSL type wrapper, allowing you to do SSL based authentication, however it should be noted that once a user connects they'd be able to do anything to any tubes on that beanstalkd instance. If you need to break it up by class you'll need to run multiple instances of beanstalkd (one for each privilege class). Personally this is the one thing on my wishlist for beanstalkd, simple username/password support for server access and tube access, but it will significantly add to the complexity and potentially increase latency which would be bad. > Best regards, > Ernest. -Kurt -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
