chore: remove yabeda-rails

Gemfile

@@ -107,8 +107,6 @@ gem 'warden'
 gem 'webrick', require: false
 gem 'yabeda-graphql'
 gem 'yabeda-prometheus'
-gem 'yabeda-puma-plugin'
-gem 'yabeda-rails'
 gem 'yabeda-sidekiq'
 gem 'zipline'
 gem 'zxcvbn-ruby', require: 'zxcvbn'

Gemfile.lock

@@ -866,15 +866,6 @@ GEM
       prometheus-client (>= 3.0, < 5.0)
       rack
       yabeda (~> 0.10)
-    yabeda-puma-plugin (0.7.1)
-      json
-      puma
-      yabeda (~> 0.5)
-    yabeda-rails (0.9.0)
-      activesupport
-      anyway_config (>= 1.3, < 3)
-      railties
-      yabeda (~> 0.8)
     yabeda-sidekiq (0.12.0)
       anyway_config (>= 1.3, < 3)
       sidekiq
@@ -1037,8 +1028,6 @@ DEPENDENCIES
   webrick
   yabeda-graphql
   yabeda-prometheus
-  yabeda-puma-plugin
-  yabeda-rails
   yabeda-sidekiq
   zipline
   zxcvbn-ruby

config/env.example.optional

@@ -244,7 +244,7 @@ REDIS_SIDEKIQ_PASSWORD='sentinel_and_redis_password'
 REDIS_SIDEKIQ_USERNAME='sentinel_and_redis_username'
 
 # configuration for prometheus metrics web server on /metrics
-# launched with sidekiq and puma
+# launched with sidekiq
 # adjust according to your prometheus probe, 127.0.0.1 or your local/admin net address
 # it's advised to avoid 0.0.0.0 or if you do, please configure ACL elsewhere (webserver, reverse proxy, ...)
 PROMETHEUS_EXPORTER_BIND="127.0.0.1"

config/initializers/prometheus_metrics.rb

@@ -1,3 +0,0 @@
-if ENV['PROMETHEUS_EXPORTER_ENABLED'] == 'enabled' && !Sidekiq.server?
-  Prometheus::Client.config.data_store = Prometheus::Client::DataStores::DirectFileStore.new(dir: Rails.root.join('tmp', 'prometheus'))
-end

config/puma.rb

@@ -45,4 +45,3 @@ end
 plugin :tmp_restart
 
 activate_control_app
-plugin :yabeda