postburner 1.0.0.pre.1 → 1.0.0.pre.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '04239ad84ef1d61fb0b3c4a354690feb9f5f5269ac98bdf2c59d860308f7b15b'
-  data.tar.gz: a127e7e32934cdc9daffd3ae7320f7153551f1b0b868745be00dfc9818c87398
+  metadata.gz: 5195def95321261f581896c066a199022239c6a2c9eb86504d0beb8ce176b111
+  data.tar.gz: cf51e2b5f1fd16938d61cc2daa626e08b3340cbe580cfcae1b42d560626fb643
 SHA512:
-  metadata.gz: df136f1ddf7d3cbac60c675ed139300af9a727e2e41fa1eee458e4ab891b69f2bf27b67adfb7af59b2731ced69f8431fdf0a7dabcf46397009ff013482729280
-  data.tar.gz: 4522be7fa74a7dc9cf807a0d7b3f9a0818c183d45eb295d66667dc7c29fea4a1f35a15271d45fdb8b0395d63b0e938a6db52e0195b9ab00b73b50cb446fed88e
+  metadata.gz: e8b2e7bbba0c0dc19ddcd5b6747a20aa0e59509fa05211e616b4eacc177bc9881fe2a873eeb407f29a3697cad280525f4dd71b2cfd412b484a876b23689c432c
+  data.tar.gz: 7f954cd5c0241e4b9af5a123ac6de7f3482fd4426a7e9f924975fc786b11b1fd48ba2e7d6942f575998ab9fb147e27e0efe0aeb4468e5fc09caa9555a009c527

data/lib/generators/postburner/install/install_generator.rb

@@ -6,6 +6,16 @@ class Postburner::InstallGenerator < Rails::Generators::Base
     install_migration! 'create_postburner_jobs'
   end
 
+  def copy_config_file
+    destination = "config/postburner.yml"
+
+    if File.exist?(File.join(destination_root, destination))
+      say_status "skip", destination, :yellow
+    else
+      template "config/postburner.yml", destination
+    end
+  end
+
   def self.next_migration_number(dirname)
     timestamp = Time.now.utc.strftime("%Y%m%d%H%M%S")
     stem = timestamp[0..-3]

data/lib/generators/postburner/install/templates/config/postburner.yml

@@ -0,0 +1,142 @@
+# Postburner Configuration Example
+#
+# Copy this file to config/postburner.yml and customize for your environment.
+#
+# ## Named Workers Configuration
+#
+# Postburner uses named worker configurations to support different deployment patterns:
+# - Single worker: bin/postburner (auto-selects the single worker)
+# - Multiple workers: bin/postburner --worker <name> (must specify which worker)
+#
+# Each worker can have different fork/thread settings and process different queues.
+# This enables running different queue groups in separate OS processes with distinct
+# concurrency profiles.
+#
+# ## Puma-Style Architecture
+#
+# - **forks: 0** = Single process with thread pool (development/staging)
+# - **forks: 1+** = Multiple processes with thread pools (production)
+#
+# Scale by adjusting forks and threads per worker:
+# - Development: forks=0, threads=1 (single-threaded, easiest debugging)
+# - Staging: forks=0, threads=10 (multi-threaded, moderate load)
+# - Production: forks=4, threads=10 (40 concurrent jobs per queue)
+#
+
+default: &default
+  # Beanstalkd connection URL
+  # Override with ENV['BEANSTALK_URL'] if set
+  beanstalk_url: <%= ENV['BEANSTALK_URL'] || 'beanstalk://localhost:11300' %>
+
+development:
+  <<: *default
+
+  workers:
+    default:
+      # Single-threaded, single process (simplest for debugging)
+      # Defaults: forks=0, threads=1, gc_limit=nil
+      queues:
+        - default
+        - mailers
+
+test:
+  <<: *default
+
+  workers:
+    default:
+      # Test mode uses inline strategies automatically
+      # Defaults: forks=0, threads=1, gc_limit=nil
+      queues:
+        - default
+
+staging:
+  <<: *default
+
+  workers:
+    default:
+      # Multi-threaded, single process (moderate concurrency)
+      default_threads: 10
+      default_gc_limit: 5000
+      queues:
+        - critical
+        - default
+        - mailers
+
+production:
+  <<: *default
+
+  # Example 1: Single worker processing all queues with same settings
+  # Run: bin/postburner
+  #
+  # workers:
+  #   default:
+  #     default_forks: 4
+  #     default_threads: 10
+  #     default_gc_limit: 5000
+  #     queues:
+  #       - critical
+  #       - default
+  #       - mailers
+  #       - imports
+
+  # Example 2: Multiple workers with different concurrency profiles
+  # Run separate processes:
+  #   bin/postburner --worker imports    (4 forks, 1 thread each)
+  #   bin/postburner --worker general    (2 forks, 100 threads each)
+  #
+  workers:
+    # Heavy, memory-intensive jobs - more processes, fewer threads
+    imports:
+      default_forks: 4
+      default_threads: 1
+      default_gc_limit: 500
+      queues:
+        - imports
+        - data_processing
+
+    # General jobs - fewer processes, many threads
+    general:
+      default_forks: 2
+      default_threads: 100
+      default_gc_limit: 5000
+      queues:
+        - default
+        - mailers
+        - notifications
+
+  # Example 3: Fine-grained control with multiple specialized workers
+  # Run separate processes:
+  #   bin/postburner --worker critical
+  #   bin/postburner --worker default
+  #   bin/postburner --worker mailers
+  #
+  # workers:
+  #   critical:
+  #     default_forks: 1
+  #     default_threads: 1
+  #     default_gc_limit: 100
+  #     queues:
+  #       - critical
+  #
+  #   default:
+  #     default_forks: 4
+  #     default_threads: 10
+  #     default_gc_limit: 5000
+  #     queues:
+  #       - default
+  #
+  #   mailers:
+  #     default_forks: 2
+  #     default_threads: 5
+  #     default_gc_limit: 2000
+  #     queues:
+  #       - mailers
+
+# Global Defaults (can be overridden per worker):
+#
+# default_queue: default           # Default queue name (optional)
+# default_priority: 65536          # Lower = higher priority (optional, 0 is highest)
+# default_ttr: 300                 # Time-to-run in seconds (optional)
+# default_threads: 1               # Thread count per fork (optional, defaults to 1)
+# default_forks: 0                 # Fork count (optional, defaults to 0 = single process)
+# default_gc_limit: nil            # Exit after N jobs for restart (optional, nil = no limit)

data/lib/postburner/active_job/adapter.rb

@@ -58,6 +58,19 @@ module ActiveJob
         end
       end
 
+      # Indicates whether the adapter supports enqueuing after transaction commit.
+      #
+      # Returns true because Postburner uses Beanstalkd (external queue),
+      # which means jobs are safely enqueued outside the database transaction.
+      # This allows Rails to automatically defer job enqueuing until after
+      # the current database transaction commits.
+      #
+      # @return [Boolean] Always returns true
+      #
+      def enqueue_after_transaction_commit?
+        true
+      end
+
       private
 
       # Checks if a job should be tracked in PostgreSQL.

data/lib/postburner/configuration.rb

@@ -63,7 +63,7 @@ module Postburner
     #   config = Postburner::Configuration.load_yaml('config/postburner.yml', 'production', 'imports')
     #
     def self.load_yaml(path, env = 'development', worker_name = nil)
-      yaml = YAML.load_file(path)
+      yaml = YAML.load_file(path, aliases: true)
       env_config = yaml[env.to_s] || yaml[env.to_sym]
 
       raise ArgumentError, "Environment '#{env}' not found in #{path}" unless env_config

data/lib/postburner/version.rb

@@ -1,3 +1,3 @@
 module Postburner
-  VERSION = '1.0.0.pre.1'
+  VERSION = '1.0.0.pre.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: postburner
 version: !ruby/object:Gem::Version
-  version: 1.0.0.pre.1
+  version: 1.0.0.pre.2
 platform: ruby
 authors:
 - Matt Smith
@@ -131,6 +131,7 @@ files:
 - config/routes.rb
 - lib/generators/postburner/install/USAGE
 - lib/generators/postburner/install/install_generator.rb
+- lib/generators/postburner/install/templates/config/postburner.yml
 - lib/generators/postburner/install/templates/migrations/create_postburner_jobs.rb.erb
 - lib/postburner.rb
 - lib/postburner/active_job/adapter.rb