support access to `server` in .service template

[takumiabe]

this change can do like this:

config/deploy/xxxx.rb

server "1.2.3.4", roles: %w{app web db}, puma_port: 8080

config/systemd/puma.service.erb

...

[Service]
...
ExecStart=bundle exec puma -C <%= current_path %>/config/puma.rb -p <%= server.properties.puma_port %>

...

I update a lot of rspecs, but I'm not sure it is right... :(

[minimum2scp]

Why don't you put port number configuration to config/puma.rb?

[takumiabe]

@minimum2scp Thank you for comment!

sorry, It is (my personal) too complex case, :( I have many sub-app on a single service under loadbalancer. (I call them A, B ,C here)

then, I want to setup this case:

• from deploy/staging.rb

  • EC2
    • A - port 3000
    • B - port 3001
    • C - port 3002

• from deploy/production.rb

  • EC2 X
    • A - port 3000
  • EC2 Y
    • B - port 3000
  • EC2 Z
    • C - port 3000

I think it is difficult to implement this case by only config/puma.rb (neither ENV inside puma.rb)

thanks

[minimum2scp]

@takumiabe Thanks, I understand.

I found that I can access server properties by backend.host.properties (an instance of Capistrano::Configuration::Server::Properties), so maybe you can set port number by backend.host.properties.fetch(:puma_port) in config/systemd/puma.service.erb.

...

[Service]
...
ExecStart=bundle exec puma -C <%= current_path %>/config/puma.rb -p <%= backend.host.properties.fetch(:puma_port) %>

...

Please try.

[takumiabe]

@minimum2scp Ohh, It works! (Sorry, I searched by "server", but by "host")

Thank you for better solution!