utter 1.0.18 → 1.0.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +10 -2
  3. data/lib/utter.rb +4 -4
  4. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 7b762fc6e11a2ff38a3ad2a46370d9fbc5a9dca7
4
- data.tar.gz: 81ae0e4db12b5b7d4d94f1152261a14bc3a9a699
3
+ metadata.gz: 6b1aa0e270513fa263ba6e96191ceaf642f6cf7f
4
+ data.tar.gz: 708433676a0f1c6a453311b15408f80c390b426d
5
5
  SHA512:
6
- metadata.gz: 95505a0667884262fa13d624ff0982d6241f602e0e6456e8567c18dc1bdb928901717ded901da2dcf9d9c81f54efa42cf9fc5fa5b1ecce778db34438f2e36be7
7
- data.tar.gz: bebdce988e431f73e0e8b762b998dc41daaa7817d319cacc79023d87f1d71651205192018003b527bf7e05d9ba193f242daeb2414208ffa361192778c5c21b18
6
+ metadata.gz: 25bc2a622f588c5d62ccfa601547e424ad4a6cdb4b10caf08903be5128aa3eb81f70a89d9353ee94f486287ff358bcf01b604dbfb2aaa0ac48fee7de6eb73058
7
+ data.tar.gz: 7b5fa95903ef5026d24c56a7b504b015fc3cc2933738902c150b399d3277263a6e8b7585a009d2a1eb3287243cdf7626ba7687ef06bf9483e94aad026fef6239
data/README.md CHANGED
@@ -1,9 +1,18 @@
1
1
  What is Utter?
2
2
  ==============
3
- Utter is a Domain-specific Microservices Framework written in Ruby for building both regular and advanced Rule-based web APIs.
3
+ Utter is a Domain-specific Microservices Framework written in Ruby for building web APIs
4
4
 
5
5
  irc: #utter@freenode.net
6
6
 
7
+ FAQ: How I can package and release my domain/domain-extension/service?
8
+ ======================================================================
9
+ Either you go to the respective .gemspec file and run `bundle exec rake release`, or you can use `utter package`
10
+
11
+
12
+ FAQ: What kind of APIs I can build with Utter?
13
+ ==============================================
14
+ Utter allows you to build both regular and advanced Rule-based web APIs.
15
+
7
16
  FAQ: Why Utter Services can NOT talk to each other?
8
17
  ================================================
9
18
  Utter services are designed to be part of your versioned API, each service handles its own logging and provides its own monitoring mechanism.
@@ -11,7 +20,6 @@ if you found yourself needing to stack\interface to each others then the Utter s
11
20
 
12
21
  What is a Domain-specific Microservice?
13
22
  ========================================
14
-
15
23
  A domain is an area of knowledge such as an industry field or a subject of interest.
16
24
  Building an application often requires the utilization of knowledge from a number of different domains.
17
25
  Designing your "Application" on the premise that any authorized entity can utilize the knowledge of a specific domain via interacting with a domain-specific microservice that can do two things, consume messeges and produce messeges.
data/lib/utter.rb CHANGED
@@ -17,7 +17,7 @@ module Utter
17
17
  # MAJOR version when you make incompatible API changes,
18
18
  # MINOR version when you add functionality in a backwards-compatible manner, and
19
19
  # PATCH version when you make backwards-compatible bug fixes.
20
- VERSION = "1.0.18"
20
+ VERSION = "1.0.19"
21
21
 
22
22
  $log = Logger.new(STDOUT)
23
23
 
@@ -36,9 +36,9 @@ module Utter
36
36
  # BASIC FEATURE
37
37
  # Usage of non domain-specific stack inside a microservice would be like
38
38
  # Stack.new do
39
- # use Trace, "A opts hash", x
40
- # use Trace, "B opts hash", "B params hash"
41
- # use Trace, "C opts hash", "C params hash"
39
+ # use Trace::Ext, "A opts hash", x
40
+ # use Trace::Ext, "B opts hash", "B params hash"
41
+ # use Trace::Ext, "C opts hash", "C params hash"
42
42
  # end
43
43
  # Very helpful if you just want to build extenstions conforming to Mushin ducking interface of :initialize(app), :call(env)
44
44
  # Yet it is strongly encourged to require your own domain-specific frameworks generated via mushin inexample, and use only
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: utter
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.18
4
+ version: 1.0.19
5
5
  platform: ruby
6
6
  authors:
7
7
  - zotherstupidguy
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-10-06 00:00:00.000000000 Z
11
+ date: 2016-10-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: pry