Closed whysthatso closed 1 year ago
Oops, we haven't documented the recommended way of configuring Puma options. In this case you would want to keep config/puma.rb
as is (with 4000 as a default), and instead update your bridgetown.config.yml
file to include this:
development:
bind: "tcp://0.0.0.0:4001"
Let me know if that works for you.
(and placing that within development
means it's a separate configuration option from the production environment, which you can also change independently if you don't want to use the BRIDGETOWN_PORT
ENV variable)
development: bind: "tcp://0.0.0.0:4001"
that did it, thanks.
Added Puma docs in the latest commit.
setting port ENV.fetch("BRIDGETOWN_PORT") { 4001 } in config/puma.rb results in the site being served under port 4001 but the logs showing this:
setting
port: 4001
inbridgetown.config.yml
did not change the output.this is the line responsible for setting the value, i believe:
is this possibly a regression due to the migration to puma?