lusnoc 0.1.2.16875 → 0.9.0.44532
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +7 -8
- data/lib/lusnoc/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 05d4b47c5281bbcf7adc5cff1e398bd4ce37e2e8953b6a09e143404777c016dc
|
|
4
|
+
data.tar.gz: 6a7afa4d21df7cd7b19cd56290ef35d58befa6013fa2f713973da2059e74297d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 34da3a07c4705381614e65b9baf6b5d6f7200abb9912ad68baa1debb043fd9b4cbb32f3c3eed37cd50cee2b1a1b7243fb8794b0be8eb1f0cb7279ab0ce889a5f
|
|
7
|
+
data.tar.gz: b3ae1f8dae1f35c346378e3c53075807346c157cbe50c7f8cb200e47cb00f7c845db92f8a43a2e83c6423188a620a6dafc9978781d82cd4cc531127173b56553
|
data/README.md
CHANGED
|
@@ -4,14 +4,13 @@
|
|
|
4
4
|
[](https://rubygems.org/gems/lusnoc/versions)
|
|
5
5
|
[](http://www.rubydoc.info/gems/lusnoc)
|
|
6
6
|
|
|
7
|
-
[](https://lysander.x.rnds.pro/api/v1/badges/lusnoc_vulnerable.html)
|
|
7
|
+
[](https://lysander.rnds.pro/api/v1/badges/lusnoc_coverage.html)
|
|
8
|
+
[](https://lysander.rnds.pro/api/v1/badges/lusnoc_quality.html)
|
|
9
|
+
[](https://lysander.rnds.pro/api/v1/badges/lusnoc_outdated.html)
|
|
10
|
+
[](https://lysander.rnds.pro/api/v1/badges/lusnoc_vulnerable.html)
|
|
12
11
|
|
|
13
12
|
Lusnoc is reliable gem to deal with [Consul](https://www.consul.io). It is designed to be simple and work without dark background magic.
|
|
14
|
-
It is inspired by [consul-mutex](https://github.com/
|
|
13
|
+
It is inspired by [consul-mutex](https://github.com/kinnalru/consul-mutex)(which has hard background magic).
|
|
15
14
|
|
|
16
15
|
## FAQ
|
|
17
16
|
|
|
@@ -19,7 +18,7 @@ It is inspired by [consul-mutex](https://github.com/discourse/consul-mutex)(whic
|
|
|
19
18
|
|
|
20
19
|
Lusnoc allows you to interact with Consul to provide distributed locks(mutex) to your application.
|
|
21
20
|
|
|
22
|
-
#### What's the difference between lusnoc and [consul-mutex](https://github.com/
|
|
21
|
+
#### What's the difference between lusnoc and [consul-mutex](https://github.com/kinnalru/consul-mutex) or [diplomat](https://github.com/WeAreFarmGeek/diplomat)
|
|
23
22
|
* consul-mutex starts background thread and ***the block of code that you pass to #synchronize runs on a separate thread, and can be killed without warning if the mutex determines that it no longer holds the lock.***
|
|
24
23
|
* diplomat provides the basic session/locks functionality but no automated control over it
|
|
25
24
|
|
|
@@ -44,7 +43,7 @@ TTL will be used in session creation on `#synchronize`:
|
|
|
44
43
|
puts "We are exclusively owns resource"
|
|
45
44
|
end
|
|
46
45
|
```
|
|
47
|
-
If mutex cannot be acquired within given timeout Lusnoc::TimeoutError is raised.
|
|
46
|
+
If mutex cannot be acquired within given timeout `Lusnoc::TimeoutError` is raised.
|
|
48
47
|
By default, the "value" of the lock resource will be the hostname of the
|
|
49
48
|
machine that it's running on (so you know who has the lock). If, for some
|
|
50
49
|
reason, you'd like to set the value to something else, you can do that, too:
|
data/lib/lusnoc/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: lusnoc
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.9.0.44532
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Samoilenko Yuri
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2021-01-13 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|