You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mq-onpremise/getting_started/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: IronMQ On-Premise Installation
2
+
title: IronMQ On-Premise Getting Started
3
3
summary: "IronMQ On-Premise requires some knowledge of deployment and server management. If you do not possess these skills please schedule a consultation with our team"
4
4
layout: default
5
5
section: mq-onpremise
@@ -63,7 +63,7 @@ is to create a persistent data volume container that is mounted where you
63
63
would like to store data. Here is a brief example, see Docker docs for details:
64
64
65
65
```
66
-
// create the data container, mounted on host at /mnt/data
66
+
// create the data container, mounted on host at /mnt/data
67
67
// note: ironmq and ironauth both store their data at /ironmq/data in container by default
68
68
$ docker run -name irondata -v /mnt/data:/ironmq/data busybox true
Copy file name to clipboardExpand all lines: mq-onpremise/integrations/amazon_sqs/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: IronMQ On-Premise Installation
2
+
title: IronMQ On-Premise SQS Instructions
3
3
summary: "We allow our customers to make seamless transitions to IronMQ by allowing them to utilitze the power of IronMQ without having to write a line of extra code"
Copy file name to clipboardExpand all lines: mq/reference/beanstalk/index.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
title: Beanstalk Interface
2
+
title: Beanstalk Reference Guide
3
3
layout: default
4
4
section: mq
5
5
breadcrumbs:
6
6
- ['Reference', '/reference']
7
7
- ['Beanstalk Interface', '/beanstalk']
8
8
---
9
9
10
-
You can use any of the [Beanstalkd clients](https://github.com/kr/beanstalkd/wiki/client-libraries) with IronMQ. The list of supported languages is extensive and so there is sure to one for your language of choice.
10
+
You can use any of the [Beanstalkd clients](https://github.com/kr/beanstalkd/wiki/client-libraries) with IronMQ. The list of supported languages is extensive and so there is sure to one for your language of choice.
11
11
12
12
<sectionid="toc">
13
13
<h3>Table of Contents</h3>
@@ -17,7 +17,7 @@ You can use any of the [Beanstalkd clients](https://github.com/kr/beanstalkd/wik
Copy file name to clipboardExpand all lines: worker/languages/nodejs/index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Writing Workers in Node.js
2
+
title: IronWorkers in Node.js
3
3
layout: default
4
4
section: worker
5
5
breadcrumbs:
@@ -109,7 +109,7 @@ runtime "node"
109
109
exec"hello_worker.js"# replace with your file
110
110
```
111
111
112
-
_To change your worker's version, you may place `stack "node-0.10"` (e.x.) in your .worker file, for more see [.worker syntax](/worker/reference/dotworker/#syntax_reference)._
112
+
_To change your worker's version, you may place `stack "node-0.10"` (e.x.) in your .worker file, for more see [.worker syntax](/worker/reference/dotworker/#syntax_reference)._
113
113
114
114
<h3id="upload_your_worker">Upload Your Worker</h3>
115
115
@@ -203,7 +203,7 @@ statusCode: 200
203
203
```
204
204
205
205
206
-
**Note**: Please make sure to check out our official [node client library](/worker/libraries)
206
+
**Note**: Please make sure to check out our official [node client library](/worker/libraries)
Copy file name to clipboardExpand all lines: worker/languages/python/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Writing Workers in Python
2
+
title: IronWorkers in Python
3
3
layout: default
4
4
section: worker
5
5
breadcrumbs:
@@ -172,7 +172,7 @@ for i in range(len(sys.argv)):
172
172
173
173
<h3id="exit_example">Ensuring your script exits with the right exit code</h3>
174
174
175
-
It is important in some cases to declare a explicit exit code to give our systems a indication if your worker has completed sucessfully or failed. this also prevents instances where your worker may just hang or wait.
175
+
It is important in some cases to declare a explicit exit code to give our systems a indication if your worker has completed sucessfully or failed. this also prevents instances where your worker may just hang or wait.
0 commit comments