-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Pum5.x : Multi Apps on same server #305
Comments
I also meet this problem, you can unset After do that deploy at least works. |
This is to do with the lookup in the "#{fetch(:puma_service_unit_name)}.service" One workaround is to define your project's own template at |
thanks @bendilley, |
Rather than having to define a template per staging environment, use `puma.service` as the template name to lookup. Fixes seuros#305
When I looked at other usage of the |
Using a default systemd service name that is consistent with the default names used in the nginx and monit plugins. In combination with seuros#308, forms a zero-config solution to seuros#305
Rather than having to define a template per staging environment, use `puma.service` as the template name to lookup. Fixes seuros/capistrano-puma#305
Using a default systemd service name that is consistent with the default names used in the nginx and monit plugins. In combination with seuros/capistrano-puma#308, forms a zero-config solution to seuros/capistrano-puma#305
Rather than having to define a template per staging environment, use `puma.service` as the template name to lookup. Fixes seuros/capistrano-puma#305
Using a default systemd service name that is consistent with the default names used in the nginx and monit plugins. In combination with seuros/capistrano-puma#308, forms a zero-config solution to seuros/capistrano-puma#305
Hey guys,
I have multiple rails apps on the same server. (everything worked fine with puma 4.x and capistrano-puma4.x)
Now with Puma 5.x, I try to set set :puma_service_unit_name, "puma_#{fetch(:application)}_#{fetch(:stage)}" otherwise the puma.service file of app A overwrites the file of app B when I launch cap production puma:systemd:config.
But i have this error
1: from /Users/jules/.rvm/gems/ruby-2.6.6@wgroupe_production/gems/capistrano3-puma-5.0.1/lib/capistrano/puma.rb:47:in
template_puma' /Users/jules/.rvm/gems/ruby-2.6.6@wgroupe_production/gems/capistrano3-puma-5.0.1/lib/capistrano/puma.rb:47:in
read': no implicit conversion of nil into String (TypeError)Have you an idea ?
Thanks,
The text was updated successfully, but these errors were encountered: