Topbit Technicals - Comments

Topbit: Doing the work elsewhere - Sidebar - running the worker

nospam@example.com (Topbit) — Wed, 28 Oct 2009 20:56:39 +0000

Multiple workers running is not a problem – Beanstalkd will keep the jobs separate even if multiple ones are reserved.

You can run more than one worker at a time, by either putting them into the background with nohup, or running them in the foreground in ‘screen’. I’ve yet to find a good way to to autostart/run one or more workers though.

Jon: Doing the work elsewhere - Sidebar - running the worker

nospam@example.com (Jon) — Wed, 28 Oct 2009 19:47:29 +0000

Is there any way to run more the 1 worker (bash script) at a time?

Alfred: Doing the work elsewhere - Sidebar - running the worker

nospam@example.com (Alfred) — Fri, 26 Jun 2009 01:13:32 +0100

Hi,

What kind of beanstalk client library do you use or have you written your own? Is it in PHP space or a C extension? Hehe I guess I will wait for your next post

alfred: Doing the work elsewhere - Asynchronous Message Queues

nospam@example.com (alfred) — Mon, 22 Jun 2009 22:28:55 +0100

Hi,

Good post. I am also playing with beanstakd and I am waiting for the rest of your posts.

Greetings,
Alfred Westerveld

Mark Sailes: svn checkouts vs exports for live versions

nospam@example.com (Mark Sailes) — Sun, 16 Mar 2008 21:31:16 +0000

Although example shown was using Windows (my desktop) there is no reason why this can’t be used on Linux or as we do HP-UX.

We are lucky enough to be able to turn off web server in groups via the load balancer when we do updates. But of course using ln -s is another great method too.

Our main website is over 300mb with over 6000 files, and with a large cluster of machines its just not cool to use an export. Although a combination of the two ideas would not be a terrible idea either. Why not have two working copies, do a switch on the offline to update it. Then swap the link across. I might try it :D