carioca 2.0.12 → 2.1.0

data/README.md

@@ -22,8 +22,8 @@ Carioca 2: is a complete rewrite who provide a full IoC/DI light Container and a
 <noscript><a href="https://liberapay.com/ruydiaz/donate"><img alt="Donate using Liberapay" src="https://liberapay.com/assets/widgets/donate.svg"></a></noscript>
 
 
-![Sc4ry logo](assets/images/logo_carioca.png) 
-_Container And Registry with Inversion Of Control for your Applications__
+![Carioca logo](assets/images/logo_carioca_full_small.png) 
+_Container And Registry with Inversion Of Control for your Applications_
 
 
 ## Installation
@@ -32,11 +32,28 @@ Install it yourself as:
 
     $ gem install carioca
 
+## Principe 
+
+![Carioca synoptic](assets/images/description_carioca.png)
+
 ## Usage
 
 
 ### Basic usage
 
+
+
+#### Principe
+
+![Carioca synoptic](assets/images/description_container_carioca.png)
+
+* Carioca come with a Container Class Template
+  * the Container automatically inject :logger, :i18n and a :configuration service (explain in detail after) 
+  * the Container provide a class method macro :inject 
+    *  this macro give a way to use other services defined in the registry file (service could be register inline, presented after)  
+
+### Beginning usecase new gem
+
 Create you own gem :
 
     $ bundle gem yourgem
@@ -53,7 +70,7 @@ and after :
     $ bundle add carioca
     $ mkdir -p config/locales
 
-Edit the Rakefil, and add the following line :
+Edit the Rakefile, and add the following line :
 
 ```ruby
 require "carioca/rake/manage"
@@ -156,7 +173,7 @@ yourgem_cmd = Yourgem::YourgemCMD::new
 yourgem_cmd.test
 ```
 
-After this, don't forget to stage new files, and you could build & install the gem before running your new command for the first time :
+**Note** : After this, don't forget to stage new files, and you could build & install the gem before running your new command for the first time :
 
     $ git add config/ exe/
     $ rake install && yourgem_cmd
@@ -178,6 +195,10 @@ After this, don't forget to stage new files, and you could build & install the g
     D, [2022-03-07T01:06:20.338381 #21513] DEBUG -- Carioca: Starting service uuid
     W, [2022-03-07T01:06:20.353142 #21513]  WARN -- Sample::YourGemCMD: Give me an UUID : 574cc860-7fd8-013a-2323-1e00870a7189
 
+  
+
+## Builtins services
+
 You could see, somme interesting things : 
 * Carioca have an internationalisation service (this service will be explain in detail after): 
   * default configured on :en locale
@@ -185,12 +206,544 @@ You could see, somme interesting things :
 * Carioca have a builtin logger service using regular Logger from Stdlib (also explain in detail in this document)
   * default logging on STDOUT, but could be redirect in the configure bloc
 * Carioca give us some usefull traces in debug   
-* Carioca come with a Container Class Template
-  * the Container automatically inject :logger, :i18n and a :configuration service (explain in detail after) 
-  * the Container provide a class method macro :inject 
-    *  this macro give a way to use other services defined in the registry file (service could be register inline, presented after)   
+* Carioca provide a complete solution to manage CLI output.  
+
+### Description Registry 
+
+
+![Carioca synoptic](assets/images/description_registry_carioca.png)
+
+### Description of services
+
+![Carioca synoptic](assets/images/description_services_carioca.png)
+
+### Generic Usage 
+
+#### Usage with the Carioca::Container template class
+
+Considering an existing service named : my_service with a unique method named a_method
+
+```ruby
+
+# frozen_string_literal: true
+
+require 'carioca'
+
+class MyObject < Carioca::Container
+
+    inject service: my_service
+
+    def initialize
+      my_service.a_method
+    end
+
+   
+
+    my_service.a_method
+
+  end
+
+end
+
+```
+the mAcro inject is already mixed in Carioca::Container
+
+**Note** : Service cloud be used on class method wrapping and instance mecthode. 
+
+#### Usage without Carioca::Container heritage
+
+Considering an existing service named : my_service with a unique method named a_method
+
+```ruby
+
+require 'carioca'
+
+class MyObject 
+
+    extend Carioca::Injector
+    inject service: my_service
+
+    def initialize
+      my_service.a_method
+    end
+
+    my_service.a_method
+
+  end
+
+end
+
+```
+
+### Service I18n
+
+the I18n is loaded by default with Carioca::Container, and loaded as dependency when using others builtin services.
+It's a fondation service for Carioca.
+
+For this exemple, we show you an explicit inject of I18n
+
+**Note** : I18n povide internationalisation for Carioca itself AND for self made services and more  
+
+**Note** : You could create all your locales files for any languages speciif to your application :
+- in $PWD/config/locales/*.yml
+- in $GEMPATH/config/locales/*.yml
+
+**Note** : If you create locales in other languages than :en or :fr (atcually the 2 supported by Carioca), for internals output (Carioca itself logs, outputs or debugs), carioca fallback on default locales defined in configuration (default :en).
+
+
+Considering a locale file en.yml in config/locales/ like :
+
+```yaml
+
+en:
+  sample:
+    string: "Display %{myvar}"
+ 
+
+```
+
+with the current code :
+
+```ruby
+
+require 'carioca'
+
+class MyObject 
+
+    extend Carioca::Injector
+    inject service: I18n
+
+    def initialize
+      puts i18n.t('sample.string', myvar: 'test')
+    end
+
+  end
+
+end
+
+``` 
+
+output  :
+
+   Display test
+
+### Service Logger 
+
+**Note** : Logger depends on service I18n
+#### Logging simply 
+
+```ruby
+
+require 'carioca'
+
+class MyObject 
+
+    extend Carioca::Injector
+    inject service: logger
+
+    def initialize
+      logger.info(self.to_s) { "my log" }
+    end
+
+  end
+
+end
+
+```
+
+
+#### Changing log strategy 
+
+
+```ruby
+require 'rubygems'
+require 'carioca'
+
+Carioca::Registry.configure do |spec|
+  spec.debug = false
+  spec.log_file = '/tmp/test_carioca.log' # a different log path (default STDOUT)
+  spec.log_level = :debug # log level base  (default :info)
+  spec.log_target = '::Logger::new(STDOUT)' # to change completly the log object 
+end
+```
+
+
+for more information on ruby Stdlib Logger, see :
+https://ruby-doc.org/3.2.2/stdlibs/logger/Logger.html
+
+
+**Note** : you could totally subsitute Logger with your own logger, by the configuration, or the logger of an other service. 
+BUT it's necessary to be compatible with standard Logger facilities :
+
+```ruby
+logger.debug('Maximal debugging info')
+logger.info('Non-error information')
+logger.warn('Non-error warning')
+logger.error('Non-fatal error')
+logger.fatal('Fatal error')
+logger.unknown('Most severe')
+```
+
+**Note** : the output service, detailled after could work in dual mode STDXXX + logger service. 
+
+### Service Configuration  
+
+
+#### Configuration 
+
+Configuration made with  Registry.configure :
+
+```ruby
+Carioca::Registry.configure do |spec|
+  spec.config_file = './config/settings.yml'
+  spec.config_root = :myappli
+  spec.environment = :development
+end
+```
+
+* config_file : path to the configuraion file (YAML format) 
+* config_root : Root of the YAML structure
+* environment : current evt used for override default values
+
+#### Configuration file format
+
+**Note** :This file is corresponding with the presented configuration 
+
+```yaml
+---
+:myappli:
+  :production: {}
+  :staging:
+    :onstaging: staging
+  :test: {}
+  :development:
+    :ondev: test
+    :treeA:
+      :trunk1:
+        :branch1: leaf1
+      :trunk2:
+        :branch3: leaf3
+        :branch4: leaf4
+        :branch5: [ "val1","val2","val3" ] 
+  :default:
+    :default_value: 'value'
+    :treeA:
+      :trunk1:
+        :branch2: leaf2
+      :trunk2:
+        :branch5: ["value"]
+```
+
+#### Access to Configuration 
+
+```ruby
+config = Carioca::Registry.get.get_service name: :configuration
+pp config.settings
+```
+
+**Note** : You could access it as usuallly, with inject, from Carioca::Container fork or mixin of Carioca::Injector in your own class.
+
+output :
+
+```
+{:default_value=>"value",
+ :treeA=>
+  {:trunk1=>{:branch2=>"leaf2", :branch1=>"leaf1"},
+   :trunk2=>
+    {:branch5=>["value", "val1", "val2", "val3"],
+     :branch3=>"leaf3",
+     :branch4=>"leaf4"}},
+ :ondev=>"test"}
+ ```
+
+**Note** : you could see the result configuration is a merge of :development path ovec :default
+
+
+#### R/W on runtime
+
+**Note** : you could override value in runtime
+
+```ruby
+config = Carioca::Registry.get.get_service name: :configuration
+config.settings.newkey = 'value'
+```
+
+
+
+#### Princpe 
+
+![Carioca synoptic](assets/images/description_configuration_carioca.png)
+
+
+### Service Output 
+
+
+#### Configuration 
+
+Configuration made with Registry.configure :
+
+```ruby
+Carioca::Registry.configure do |spec|
+  spec.debug = false
+  spec.log_file = '/tmp/test.rge'
+  spec.log_level = :debug
+  spec.output_mode = :dual
+  spec.output_emoji = true
+  spec.output_colors = true
+  spec.output_target = STDOUT
+
+end
+```
+
+* output_mode : choose if you want to display to output_target OR/AND Logs, mode are : :mono, dual, log
+* output_emoji : display levels or alias as UTF8 EMOJI
+* output_colors : display output in colors
+* output_target : change output STDOUT or SDTERR
+
+**Note** : all of this have R/W accessors on output service 
+
+#### Usage 
+
+
+This example show a test script for displaying all type of output 
+
+```ruby
+output = Carioca::Registry.get.get_service name: :output
+
+cycle = %i[unknown fatal error ko warn info item arrow scheduling trigger sending calling receive
+               ok success debug flat]
+    cycle.each do |verb|
+      output.send verb, verb.to_s
+    end
+    output.color = false
+    cycle.each do |verb|
+      output.send verb, verb.to_s
+    end
+    output.emoji = false
+    cycle.each do |verb|
+      output.send verb, verb.to_s
+    end
+    output.color = true
+    cycle.each do |verb|
+      output.send verb, verb.to_s
+    end
+
+```
+**Note** : list of ordered levels or alias : **unknown fatal error ko warn info item arrow scheduling trigger sending calling receive ok success debug flat**
+
+Output : 
+
+* Without colors nor Emojies
+
+![Carioca output](assets/images/carioca_output_no_emoji_no_colors.PNG)
+
+* Without colors but with Emojies
+
+![Carioca output](assets/images/carioca_output_emoji_no_colors.PNG)
+
+* With colors but no Emojies
+
+![Carioca output](assets/images/carioca_output_no_emoji_colors.PNG)
+
+* With colors and Emojies
+
+![Carioca output](assets/images/carioca_output_emoji_colors)
+
+### Service Debug
+
+
+For this example, we use a internal service defined programmaticalu on runtime, (we see it more in detail in the chapter dedicated to the registry)
+At the beginning of you code, just add : 
+
+```ruby
+class MyService
+  extend Carioca::Injector
+  inject service: :logger
+
+  def initialize
+    logger.warn(self.class.to_s) { 'Init service' }
+  end
+
+  def hello
+    logger.info(self.class.to_s) { 'Hello World' }
+  end
+
+  def method_test(_titi, tutu:)
+    @tutu = tutu
+    yield if block_given?
+    "result #{@tutu}"
+  end
+end
+
+spec = {
+  service: 'MyService::new',
+  type: :internal
+}
+
+Carioca::Registry.init.add service: :myservice, definition: spec
+
+```
+
+With a configuration like :
+
+
+```ruby
+Carioca::Registry.configure do |spec|
+  spec.debug = true
+  spec.log_level = :debug
+  spec.output_emoji = true
+  spec.output_colors = false
+  spec.debugger_tracer = :output
+end
+
+```
+
+
+To help debug with services, Carioca come with a proxy class debugger :
+
+```ruby
+config = Carioca::Registry.get.get_service name: :debugger
+proxy = debugger.get service: :myservice
+    proxy.method_test 'param', tutu: 'keyword' do
+      puts 'titi'
+    end
+```
+
+output : 
+
+```
+🐛 BEGIN CALL for service #<MyService:0x00005635ed283290>
+🐛 Method called: method_test
+🐛 args : param
+🐛 keywords : {:tutu=>"keyword"}
+🐛 block given
+titi
+🐛 => method returned: result keyword
+🐛 END CALL
+```
+
+## Carioca Configuration
+
+Carioca use a bloc given mapping object of to configure like :
+
+```ruby
+Carioca::Registry.configure do |spec|
+  spec.xxxxx = <SOMETHING>
+ ...
+end
+
+```
+### list of accessors over the spec object :
+
+```ruby
+attr_accessor :filename, :name, :builtins, :log_target, :default_locale, :locales_load_path, :debugger_tracer,
+                  :config_file, :config_root, :environment, :supported_environments, :output_mode, :log_level, :output_target
+attr_writer :init_from_file, :output_colors, :output_emoji
+attr_reader :log_file, :locales_availables, :debug
+
+```
+
+### Publique usage (with default values and possibles values)
+
+```ruby
+Carioca::Registry.configure do |spec|
+
+  spec.filename = './config/carioca.registry' # the carioca registry of services configuration
+  spec.name = 'Carioca' # the name of the application
+  spec.debug = false # activate debug, display debug Carioca message
+  spec.init_from_file = true # use the registry file to init services : (spec.filename)
+  spec.log_file = '' # path to a log file for carioca logger service
+  spec.config_file = './config/settings.yml' # path to the YAMl COnfiguration file for :configuration Carioca service 
+  spec.config_root = :carioca # the config root in the YAMl COnfiguration file for :configuration Carioca service
+  spec.environment = :development # the current environment running with Carioca
+  spec.default_locale = :en # the default locales Carioca fot I18n Carioca Service
+  spec.log_level = :info # the current log level (see logger ) for Carioca in :debug,:info,:warn,:error,:fatal,:unknown
+  spec.output_mode = :mono # the current output mode in :mono, :dual, :log (see Carioca Service Output)
+  spec.output_emoji = true # the current output status for emoji (see Carioca Service Output)
+  spec.output_target = STDOUT # the current output target STDOUT or STDERR (see Carioca Service Output)
+  spec.output_colors = true # the current output status for colors (see Carioca Service Output)
+  spec.locales_load_path << Dir["#{File.expand_path('./config/locales')}/*.yml"]
+  spec.debugger_tracer = :output # the Debbugger service output in #log , :output
+
+end
+```
+## Registry access and methods
+
+### Init or getting Registry 
+
+Carioca::Registry is a Singleton Object
+
+You cloud init or get it by #get, #instance or #init, like :
+
+```ruby
+registry = Carioca::Registry.init
+registry = Carioca::Registry.instance
+registry = Carioca::Registry.get 
+```
+
+### Direct access to Registry and getting service Without Injector or Carioca::Container
+
+Example : for output service
+
+```ruby
+output = Carioca::Registry.get.get_service name: :output 
+```
+
+
+### Adding a service programatically 
+
+To add a service, you could insert it in the registry file (before run) or adding it programatically
+
+```ruby
+class MyService
+  extend Carioca::Injector
+  inject service: :logger
+
+  def initialize
+    logger.warn(self.class.to_s) { 'Init service' }
+  end
+
+  def hello
+    logger.info(self.class.to_s) { 'Hello World' }
+  end
+
+  def method_test(_titi, tutu:)
+    @tutu = tutu
+    yield if block_given?
+    "result #{@tutu}"
+  end
+end
+
+spec = {
+  service: 'MyService::new',
+  type: :internal
+}
+
+Carioca::Registry.init.add service: :myservice, definition: spec
+
+```
+
+
+### Decription of type of Service 
+
+
+```ruby
+SERVICES_MANDATORY_SPECS = { type: Symbol, service: String }.freeze
+SERVICES_FULL_LIST_SPECS = SERVICES_MANDATORY_SPECS.merge({ depends: Array, description: String,
+                                                                resource: String })
+```
+
+
+* :type must be : :gem, :file, :stdlib all engage requirement of the resource field, tje last :internal is usable if the code is internal in your application.
+
+* :service : is the Ruby code to access to Class for class methods service usage or object instance
+  example : MYCLASS or MyClass::new(params)
+
+* :resource is respectively a name of a gem, an absolut path of a ruby file, the name of a Ruby Stdlib correspondingly to :type 
+* depends : is a list of requiered services for this service. (all services in depends are load before getting the wanted service (from builtin and in registry file or added at runtime ).
+* Description is not mandatory 
+
 
-## A step further 
 
 
 ## Development

data/Rakefile

@@ -44,3 +44,8 @@ namespace :yardoc do
   end
 end
 task clobber: 'yardoc:clobber'
+
+desc "Run CVE security audit over bundle"
+task :audit do
+  system('bundle audit')
+end

data/VERSION

@@ -1 +1 @@
-2.0.12
+2.1.0

data/carioca.gemspec

@@ -41,6 +41,8 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'rubocop', '~> 1.32'
   spec.add_development_dependency 'yard', '~> 0.9.27'
   spec.add_development_dependency 'yard-rspec', '~> 0.1'
+  spec.add_development_dependency "bundle-audit", "~> 0.1.0"
   spec.metadata['rubygems_mfa_required'] = 'false'
   spec.add_dependency 'version', '~> 1.1'
+  spec.add_runtime_dependency 'ps-ruby','~> 0.0.4'
 end

data/config/locales/en.yml

@@ -21,3 +21,37 @@ en:
   output: 
     load:
       context: "Output service initialized in mode : %{confset}"
+  finisher:
+    messages: 
+      not_root: "This operation need to be run as root (use sudo or rvmsudo)"
+      options_incompatibility: "Options incompatibility"
+      service_dependence_missing: "Appifier Service dependence missing"
+      config_required: "Specific configuration required"
+      setup_error: "Setup terminated unsuccessfully"
+      setup_success: "Setup terminated successfully"
+      sanitycheck_error: "Sanitycheck terminated unsuccessfully"
+      sanitycheck_success: "Sanitycheck terminated successfully"
+      configuration_error: "Configuration Error"
+      success_exit: "Operation sucessfull"
+      error_exit: "Operation failure" 
+      interrupt: "User operation interrupted"
+      not_found: "Object not found"
+      already_exist: "Object already exist"
+      status_ok: "Status OK"
+      status_ko: "Status KO"
+    bad_usage: "Case must be a return or an exit"
+  setup:
+    error: "Setup operation failed"
+    execute:
+      start: "Begining setup :"
+    install: "Installation of file %{file}"
+    mkdir: "Creation of folder %{path}"
+    ln: "Creation of symlink %{target} -> %{source}"
+  sanitycheck:
+    error: "Sanitycheck stop on Configuration error"
+    success: "Sanitycheck finish without errors"
+    failure: "Sanitycheck finish with errors"
+    run:
+      start: "Begining sanitycheck :"
+      ok: "Testcase %{testcase} on %{name} is ok"
+      ko: "Testcase %{testcase} on %{name} is ok, problem(s) : %{pbm}"