Hi Bas, 1. The queue.sh script is deployed via Capistrano, as part of the source code of each website, just like many websites have a cron.sh script. 2. I'm not entirely sure what you mean. The first time the worker is executed is when it's started by the init-script. There's an AWS SQS queue into which jobs are posted by various web applications. The queue.sh script sets a umask and starts a php command that subscribes to the queue for jobs that it can handle. If it does, it processes the job using code from the website's framework, writes the result, acknowledges success to the queue and goes back to polling. The php command should keep run like a daemon, one for each website, restarting if it dies and starting and stopping with the system. I'm not sure yet how to deal with restarting it when the website code is updated though.
Good point about reloading Upstart. Could I put those Service, Exec and File resources all into the same Define, using the define's title to make each resource unique? I do feel my design could be simplified but am not seeing how. Thanks, Martijn -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/dcdc962e-727b-463d-b221-829091c1c306%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.