Comments on: The New IronWorker Command Line Interface and .worker Files https://blog.iron.io/new-ironworker-command-line-interface/ Scalable serverless application tools to run background tasks with Docker containers and manage messaging queues with cloud elasticity and handheld customer support. Thu, 14 Jan 2021 07:14:35 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Travis Reeder https://blog.iron.io/new-ironworker-command-line-interface/#comment-56 Fri, 25 May 2012 21:08:18 +0000 http://ironio2.wpengine.com/?p=180#comment-56 Hi Gareth. Exactly, you can upload workers from your dev machine for instance, then you can queue them from anywhere, such as your production application, very easily using the API. See the API docs:

https://dev.iron.io/worker/reference/api/#queue_a_task

You can use any of our libraries in any language to queue, like in the example above in Ruby, you would just call: client.tasks.create(“hello”, “foo”=>”bar”).

]]> By: gareth https://blog.iron.io/new-ironworker-command-line-interface/#comment-55 Fri, 25 May 2012 03:42:01 +0000 http://ironio2.wpengine.com/?p=180#comment-55 Very nice. Worked with no problems.

I guess this means that another person with my token and project id could launch a worker from another machine without having the source code for the worker. They would need the CLI and a script or batch file that runs the iron_worker queue command. Does that make sense?

Thanks.

]]>