fanforce-plugin-factory 0.9.7 → 0.10.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +8 -8
- data/README.md +12 -0
- data/lib/fanforce/plugin_factory/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
---
|
2
2
|
!binary "U0hBMQ==":
|
3
3
|
metadata.gz: !binary |-
|
4
|
-
|
4
|
+
ZTVmY2JmOTYyYWJiZWYyMzg4M2I3OTYwYzJkZmVmOWExMjVhYjYyYw==
|
5
5
|
data.tar.gz: !binary |-
|
6
|
-
|
6
|
+
MmM3YzA3ZDk4NjBkZjM3ZWZmMGE1ZTIxMjZmMWQ1NmQ2MTc0OTAwOQ==
|
7
7
|
!binary "U0hBNTEy":
|
8
8
|
metadata.gz: !binary |-
|
9
|
-
|
10
|
-
|
11
|
-
|
9
|
+
NWJiZWVjMjAyODVhZThiODE0NTc3NTVjOGIzN2M2YjgwODUzMjRmMzk2Y2Mz
|
10
|
+
ODYyYjE0NjVjMGVkOWRjZmNkNGQ3NWQ0NmNiMTQ1ODNiOWM2YTRkN2UyZDBj
|
11
|
+
YjI1ZjE4OGYzOGY5MjI0ZjQ5YWJlYmE0N2IxNmRjODdkY2FkMGI=
|
12
12
|
data.tar.gz: !binary |-
|
13
|
-
|
14
|
-
|
15
|
-
|
13
|
+
YjIyOWFlNDIwMjI1NzMyZTljNzAwMTVmYjgyMWRkMTYzNmJmYWY4MWFlMjI5
|
14
|
+
YTBjYzM1NjA2OWJjMWI5NWVkYWI3Y2JmZjUxZjU3NGE5NjNiNzhlM2EyOTg0
|
15
|
+
ZTVjMjZjYzc5NjIxZDhlYjI2ZDUwZTcxNDY2ZGY3MDU4ZTE2NzM=
|
data/README.md
CHANGED
@@ -215,4 +215,16 @@ FanforcePlugin.config do |config|
|
|
215
215
|
end
|
216
216
|
```
|
217
217
|
|
218
|
+
# Using Fanforce::Workers
|
219
|
+
|
220
|
+
FanforcePlugin includes the fanforce-workers gem by default and includes a convenience helper method. FanforcePlugin.enqueue
|
221
|
+
will prefix the name of your worker with the name of your plugin to ensure there are no conflicts across multiple plugins
|
222
|
+
or apps. This is the naming convention used by Fanforce Factory when creating and uploading Iron.io workers.
|
223
|
+
|
224
|
+
As an example, if you have a testing.worker file, you would use the following command:
|
225
|
+
|
226
|
+
```
|
227
|
+
FanforcePlugin.enqueue 'testing', {params_to_send: 'whatever'}
|
228
|
+
```
|
229
|
+
|
218
230
|
|