Adopt deployment after refactoring and reset puma to default

This commit is contained in:
Sebastian Serth
2018-10-10 14:09:13 +02:00
parent dd0f56659e
commit 58f82178b8
2 changed files with 2 additions and 3 deletions

View File

@ -19,7 +19,6 @@ namespace :deploy do
after :compile_assets, :copy_vendor_assets do after :compile_assets, :copy_vendor_assets do
on roles(fetch(:assets_roles)) do on roles(fetch(:assets_roles)) do
within release_path do within release_path do
execute :cp, '-r', 'vendor/assets/images/', 'public/assets/'
execute :cp, '-r', 'vendor/assets/javascripts/ace', 'public/assets/' execute :cp, '-r', 'vendor/assets/javascripts/ace', 'public/assets/'
end end
end end

View File

@ -21,14 +21,14 @@ environment ENV.fetch("RAILS_ENV") { "development" }
# Workers do not work on JRuby or Windows (both of which do not support # Workers do not work on JRuby or Windows (both of which do not support
# processes). # processes).
# #
workers ENV.fetch("WEB_CONCURRENCY") { 2 } # workers ENV.fetch("WEB_CONCURRENCY") { 2 }
# Use the `preload_app!` method when specifying a `workers` number. # Use the `preload_app!` method when specifying a `workers` number.
# This directive tells Puma to first boot the application and load code # This directive tells Puma to first boot the application and load code
# before forking the application. This takes advantage of Copy On Write # before forking the application. This takes advantage of Copy On Write
# process behavior so workers use less memory. # process behavior so workers use less memory.
# #
preload_app! # preload_app!
# Allow puma to be restarted by `rails restart` command. # Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart plugin :tmp_restart