fixing old urls to blog.iron.io

Author: emusabaev

_posts/2012-06-13-solutions-notifications.md

@@ -47,7 +47,7 @@ notification headers, preparing and sending the notification, and signaling
 exceptions and recording the status.
 
 For a detailed example using SendGrid, IronWorker, and ActionMailer, check
-out our [blog post](http://blog.iron.io/2012/06/powerful-email-infrastructure-with.html).
+out our [blog post](https://blog.iron.io/powerful-email-infrastructure-with).
 
 ### Preparing the Headers
 
@@ -86,7 +86,7 @@ are often not impressed with 9 hour delays between an event and receiving a
 notification of it. As your usage and user base grow, a single task that
 processes notifications one at a time will quickly become inadequate.
 
-As with the [transformation of a 9-hour job to a 9-minute job](http://blog.iron.io/2012/03/how-to-reduce-9-hour-job-into-10-minute.html),
+As with the [transformation of a 9-hour job to a 9-minute job](https://blog.iron.io/how-to-reduce-9-hour-job-into-10-minute),
 the solution to this lies in massive parallelisation. By queuing tens, hundreds,
 or thousands of tasks to manage your queue, you can process a staggering
 amount of notifications and emails in a brief time period. Many hands makes

mq/3/reference/push_queues/index.md

@@ -40,7 +40,7 @@ breadcrumbs:
 
 <h2 id="overview">Overview</h2>
 
-[Blog Post for Overview](http://blog.iron.io/2013/01/ironmq-push-queues-reliable-message.html). You should also review
+[Blog Post for Overview](https://blog.iron.io/ironmq-push-queues-reliable-message). You should also review
 the [MQ API for push queue related endpoints](http://dev.iron.io/mq/reference/api/).
 
 <h2 id="subscribers">Subscribers</h2>

search.json

@@ -142,7 +142,7 @@
 		"categories": [],
 		"summary": null,
 		"short": "Celery is a task queue for Python. Originally developed as part of the Django framework, it was split off into its own project and has quickly become the standard for task processing in Python. Celery supports multiple technologies for its queue broker including RabbitMQ, Redis, and IronMQ. There are many advantages to choosing IronMQ over the others. To name a",
-		"body": "Celery is a task queue for Python. Originally developed as part of the Django framework, it was split off into its own project and has quickly become the standard for task processing in Python. Celery supports multiple technologies for its queue broker including RabbitMQ, Redis, and IronMQ. There are many advantages to choosing IronMQ over the others. To name a few: Instant high availability No servers, maintenance, or scaling to worry about Greater job visibility with IronMQ dashboards For more information, visit Iron.io/celery Getting Started Celery was designed to easily change your broker which makes changing to IronMQ as easy as 1-2-3. Install iron_celery: pip install iron_celery add import iron_celery set BROKER_URL = 'ironmq://project_id:token@' We expand on these steps in the integration libary docs . Further Reading iron_celery Module: https://github.com/iron-io/iron_celery Getting Started Blog Post: http://blog.iron.io/2013/02/using-ironmq-as-celery-broker.html Getting Started Video (2 mins): Iron.io/celery Celery on Heroku: https://github.com/iron-io/heroku-iron-celery-demo "
+		"body": "Celery is a task queue for Python. Originally developed as part of the Django framework, it was split off into its own project and has quickly become the standard for task processing in Python. Celery supports multiple technologies for its queue broker including RabbitMQ, Redis, and IronMQ. There are many advantages to choosing IronMQ over the others. To name a few: Instant high availability No servers, maintenance, or scaling to worry about Greater job visibility with IronMQ dashboards For more information, visit Iron.io/celery Getting Started Celery was designed to easily change your broker which makes changing to IronMQ as easy as 1-2-3. Install iron_celery: pip install iron_celery add import iron_celery set BROKER_URL = 'ironmq://project_id:token@' We expand on these steps in the integration libary docs . Further Reading iron_celery Module: https://github.com/iron-io/iron_celery Getting Started Blog Post: https://blog.iron.io/using-ironmq-as-celery-broker Getting Started Video (2 mins): Iron.io/celery Celery on Heroku: https://github.com/iron-io/heroku-iron-celery-demo "
 	}, {
 		"title": "Delayed Job on IronMQ",
 		"url": "/mq/integrations/delayed_job/index.html",

worker/cli/index.md

@@ -82,7 +82,7 @@ iron worker upload --zip $WORKER.zip --name $WORKER_NAME $IMAGE $COMMAND
 Where `$WORKER` is replaced by the name of your packaged worker zip and `$COMMAND` is the command you want executed, the same
 one you used with `docker run`.
 
-Sometimes, you want to limit the number of parallel workers for any given task, to prevent external resources like databases or APIs from crashing under the weight of your workers' requests. We have a [max_concurrency](http://blog.iron.io/2012/08/ironworkers-most-requested-feature-is.html) feature that lets you do just this. To use it, simply use the `--max-concurrency` option when uploading a worker, with the maximum number of workers that can be run in parallel:
+Sometimes, you want to limit the number of parallel workers for any given task, to prevent external resources like databases or APIs from crashing under the weight of your workers' requests. We have a [max_concurrency](https://blog.iron.io/ironworkers-most-requested-feature-is) feature that lets you do just this. To use it, simply use the `--max-concurrency` option when uploading a worker, with the maximum number of workers that can be run in parallel:
 
 ```sh
 iron worker upload --max-concurrency 10 ...

worker/examples/index.md

@@ -19,7 +19,7 @@ git clone https://github.com/iron-io/dockerworker.git
 ```
 
 <div class="alert">
-<p>Check out our Post on Top 10 Use Cases for IronWorker <a href="http://blog.iron.io/2014/02/top-10-uses-of-ironworker.html">Here!</a></p>
+<p>Check out our Post on Top 10 Use Cases for IronWorker <a href="https://blog.iron.io/top-10-uses-of-ironworker">Here!</a></p>
 </div>
 
 

worker/iron_casts/index.md

@@ -8,12 +8,12 @@ breadcrumbs:
 
 This page lists past IronCasts series. The screencasts are intended to be short and focused on some of the most commonly asked questions.
 
-## [IronCast Series 1 - Introduction to IronWorker](http://blog.iron.io/search/label/Introduction%20to%20IronWorker)
+## [IronCast Series 1 - Introduction to IronWorker](https://blog.iron.io/ironcast-1-introduction-to-ironworker)
 
 In a series of four IronCasts, we will provide a high-level introduction to using IronWorker. IronWorker is an easy-to-use scalable task queue that gives cloud developers a simple way to offload front-end tasks, run scheduled jobs, and process tasks in the background and at scale.
 
 These videocasts will cover core concepts including:
-- [Deploying a worker](http://blog.iron.io/2013/09/ironcast-1-introduction-to-ironworker.html)
+- Deploying a worker
 - Writing worker files to declare dependencies
 - Test and prototype workers rapidly locally
 - Connecting to a cloud development database

worker/languages/ruby/index.md

@@ -252,5 +252,5 @@ Your workers should be independent, discrete parts of an application, a mini-app
 framework usage in workers, in general, is frowned upon.
 
 
-Check out [this blog post](http://blog.iron.io/2012/06/powerful-email-infrastructure-with.html)
+Check out [this blog post](https://blog.iron.io/powerful-email-infrastructure-with)
 for step-by-step instructions on including and using the Rails stack including some models, ActionMailers, etc.

worker/reference/cli/index.md

@@ -58,7 +58,7 @@ The same applies to the `IRON_TOKEN` environment variable.
 Where `$WORKER` is replaced by the name of your packaged worker zip and `$COMMAND` is the command you want executed, the same
 one you used with `docker run`.
 
-Sometimes, you want to limit the number of parallel workers for any given task, to prevent external resources like databases or APIs from crashing under the weight of your workers' requests. We have a [max_concurrency](http://blog.iron.io/2012/08/ironworkers-most-requested-feature-is.html) feature that lets you do just this. To use it, simply use the `--max-concurrency` option when uploading a worker, with the maximum number of workers that can be run in parallel:
+Sometimes, you want to limit the number of parallel workers for any given task, to prevent external resources like databases or APIs from crashing under the weight of your workers' requests. We have a [max_concurrency](https://blog.iron.io/ironworkers-most-requested-feature-is) feature that lets you do just this. To use it, simply use the `--max-concurrency` option when uploading a worker, with the maximum number of workers that can be run in parallel:
 
 ```sh
 iron worker upload --max-concurrency 10 ...

worker/scheduling/index.md

@@ -36,8 +36,8 @@ See <a href="/worker/reference/api/#schedule_a_task">Scheduling API reference</a
 		<p>Many Tasks To Run in Future - If you have lots of the same individual tasks to run in the future (sending emails to users, for example), we suggest <strong>not</strong> creating individual scheduled tasks (or queuing lots of tasks with delays). It's better to create a scheduled task that repeats on a regular basis. This scheduled task should then query a data base or datastore for the users to email (or actions to take). It can then spin up one or more sub-tasks to execute the work (creating one task per action or better yet, allocating a certain number of data slices to each task to better amortize the setup cost of a task).</p>
 		<p>Here are a few posts on the topic:</p>
 		<ul>
-			<li><a href="http://blog.iron.io/2011/06/worker-patterns-creating-task-level.html">Pattern: Creating Task-Level Workers at Runtime</a></li>
-			<li><a href="http://blog.iron.io/2011/07/anti-pattern-lots-of-scheduled-jobs.html">Anti-Pattern: Lots of Scheduled Jobs</a></li>
+			<li><a href="https://blog.iron.io/worker-patterns-creating-task-level">Pattern: Creating Task-Level Workers at Runtime</a></li>
+			<li><a href="https://blog.iron.io/anti-pattern-lots-of-scheduled-jobs">Anti-Pattern: Lots of Scheduled Jobs</a></li>
 		</ul>
 	</li>
 

worker/turnkey/index.md

@@ -15,7 +15,7 @@ The basic usage for all of these is:
 1. iron_worker upload http://github.com/PATH_TO_WORKER_FILE
 2. Queue up tasks for the worker or schedule it.
 
-That's it!  Super easy, super powerful. [See this blog post on shareable workers for more background.](http://blog.iron.io/2012/11/sharable-open-source-workers-for.html)
+That's it!  Super easy, super powerful. [See this blog post on shareable workers for more background.](https://blog.iron.io/sharable-open-source-workers-for)
 
 ## Turnkey Worker List