3843cab643
* update Gemfile to rails 5 and ruby 2.3.0 * fiddle with javascripts and add sprockets manifest file * update config directory for rails 5 * fix some errors with controllers/serializers * fix travis and rspec * new serializers renamed to serializers * module Api::V1 * reusable embedding code * add index/collections/paging. overriding most of snorlax now |:) * raml api documentation + rspec tests to verify schemas/examples * add sorting by ?sort and searching by ?q. Add pagination Link headers * api v1 => v2 * fill out synapse api * alphabetize map policy * fix page thing * fill out maps api * formParameters => properties, and fiddle with map api * more raml 1.0 stuff i'm learning about * deprecate v1 api * rails 5 uses ApplicationRecord class for app-wide model config * Update topic spec for api v2 * workaround for user_preference.rb issue * get ready for token api docs. also TODO is mapping api docs * spec out mapping api * map/mapping/synapse spec, plus other bugs * awesome, token specs/apis are done * add sanity checks to the api tests * more cleanup * devise fix * fix starred map error
48 lines
2 KiB
Ruby
48 lines
2 KiB
Ruby
# Puma can serve each request in a thread from an internal thread pool.
|
|
# The `threads` method setting takes two numbers a minimum and maximum.
|
|
# Any libraries that use thread pools should be configured to match
|
|
# the maximum value specified for Puma. Default is set to 5 threads for minimum
|
|
# and maximum, this matches the default thread size of Active Record.
|
|
#
|
|
threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }.to_i
|
|
threads threads_count, threads_count
|
|
|
|
# Specifies the `port` that Puma will listen on to receive requests, default is 3000.
|
|
#
|
|
port ENV.fetch("PORT") { 3000 }
|
|
|
|
# Specifies the `environment` that Puma will run in.
|
|
#
|
|
environment ENV.fetch("RAILS_ENV") { "development" }
|
|
|
|
# Specifies the number of `workers` to boot in clustered mode.
|
|
# Workers are forked webserver processes. If using threads and workers together
|
|
# the concurrency of the application would be max `threads` * `workers`.
|
|
# Workers do not work on JRuby or Windows (both of which do not support
|
|
# processes).
|
|
#
|
|
# workers ENV.fetch("WEB_CONCURRENCY") { 2 }
|
|
|
|
# Use the `preload_app!` method when specifying a `workers` number.
|
|
# This directive tells Puma to first boot the application and load code
|
|
# before forking the application. This takes advantage of Copy On Write
|
|
# process behavior so workers use less memory. If you use this option
|
|
# you need to make sure to reconnect any threads in the `on_worker_boot`
|
|
# block.
|
|
#
|
|
# preload_app!
|
|
|
|
# The code in the `on_worker_boot` will be called if you are using
|
|
# clustered mode by specifying a number of `workers`. After each worker
|
|
# process is booted this block will be run, if you are using `preload_app!`
|
|
# option you will want to use this block to reconnect to any threads
|
|
# or connections that may have been created at application boot, Ruby
|
|
# cannot share connections between processes.
|
|
#
|
|
# on_worker_boot do
|
|
# ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
|
|
# end
|
|
|
|
# Allow puma to be restarted by `rails restart` command.
|
|
plugin :tmp_restart
|