mission_control-jobs 1.0.1 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 12e13fd449713b2cab7915721776a561c533d47e3e88e9a6ca52d3b889204aa2
-  data.tar.gz: 3549e331263b4e6bd2ff7ab86903caafce60da891ebfc13dedcbaa21c77a350a
+  metadata.gz: 2bba1e3be2d257eea8a3956ca3f6b8c9e6708f2fc81fe23290953ac66ecd79b0
+  data.tar.gz: c470df35a98c7f0f90163540dca2d3c8bd9ca14128ae283731c0e920fdae140e
 SHA512:
-  metadata.gz: 0f59744479a144daf0de7009b9dd3fbf2634becc242dbb24919a2129a3916999b9c0aabb6ec6ba736da19f80ff225f56422c8f8a465c3febb11df1708fefdf67
-  data.tar.gz: 22f66b38214a110c9019714c3a091b750801f2898dfb10b2dff960b5d1afdb83e09321c92e4197eed295aeee2e9fdf02076026024157985e953977fef46e122f
+  metadata.gz: 8a6068c3fa2f86d32f07fb458b644efb9e8e0661f1feb65e26bf41d4051bca594ab29d15819b9ab94051451015b1d051bf33b7152797c87ec1952a074f968b2c
+  data.tar.gz: 972eb81ce61459dcdd2e881ce88a5bf69da431f1b2a17ed6e10a3bf8572222f27b111035747c46492fc459b485542b5dfd072cfb04c4ae1dca6a0cbc5b73bc0c

data/README.md

@@ -54,8 +54,6 @@ For example, if you're using the Dockerfile generated by Rails with an API-only
 RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile
 ```
 
-*Note: Legacy CSS bundlers `sass-rails` and `sassc-rails` may fail to compile some of the CSS vendored into this library from [Bulma](https://github.com/jgthms/bulma), which was created in [Dart SASS](https://sass-lang.com/dart-sass/). You will therefore need to upgrade to `dartsass-rails` or some library that relies on it, like `cssbundling-rails`.*
-
 ### Authentication
 
 Mission Control comes with **HTTP basic authentication enabled and closed** by default. Credentials are stored in [Rails's credentials](https://edgeguides.rubyonrails.org/security.html#custom-credentials) like this:
@@ -76,6 +74,15 @@ To set them up for different environments you can use the `RAILS_ENV` environmen
 RAILS_ENV=production bin/rails mission_control:jobs:authentication:configure
 ```
 
+User and password can also be configured by hand like this:
+
+```ruby
+Rails.application.configure do
+  MissionControl::Jobs.http_basic_auth_user = "dev"
+  MissionControl::Jobs.http_basic_auth_password = "secret"
+end
+```
+
 #### Custom authentication
 
 You can provide your own authentication mechanism, for example, if you have a certain type of admin user in your app that can access Mission Control. To make this easier, you can specify a different controller as the base class for Mission Control's controllers. By default, Mission Control's controllers will extend the host app's `ApplicationController`, but you can change this easily:
@@ -158,19 +165,19 @@ SERVERS_BY_APP.each do |app, servers|
     end
 
     # Default:
-    # 
+    #
     # @return Array<String, ActiveJob::QueueAdapters::Base)
     # An array where:
     # * the String represents the symbolic name for this server within the UI
     # * ActiveJob::QueueAdapters::Base adapter instance used to access this Application Server/Service
-    [ server, queue_adapter ] 
-    
+    [ server, queue_adapter ]
+
     # Optional return formats:
-    # 
+    #
     # @return Array<String, Array<ActiveJob::QueueAdapters::Base>>
-    # * This is equivalent, and behaves identically to, the format the default format above. 
+    # * This is equivalent, and behaves identically to, the format the default format above.
     # [ server, [ queue_adapter ]]  # without optional backtrace cleaner
-    # 
+    #
     # @return Array<String, Array<ActiveJob::QueueAdapters::Base, ActiveSupport::BacktraceCleaner>>
     # * This format adds an optional ActiveSupport::BacktraceCleaner to override the system wide
     #   backtrace cleaner for *this* Application Server/Service.
@@ -246,7 +253,7 @@ Available job servers:
 
 And then:
 ```
->> connect_to "hey:solid_queue"
+>> connect_to hey:solid_queue
 Connected to hey:solid_queue
 ```