Closed topofocus closed 1 year ago
If the port to serve is modified in /config/puma.yml, the value is not transmitted to die output-method
/config/puma.yml
$ bin/bt s [Bridgetown] Starting: Bridgetown v1.2.0.beta4 (codename "Bonny Slope") [Server] * Puma version: 5.6.5 (ruby 3.1.1-p18) ("Birdie's Version") [Server] * PID: 1295831 [Server] * Listening on http://0.0.0.0:4022 <<---- set in puma configuration --->> [Server] Use Ctrl-C to stop [Frontend] yarn run esbuild-dev [Frontend] yarn run v1.22.5 [Frontend] $ yarn shoelace:copy-assets && node esbuild.config.js --watch [Frontend] $ mkdir -p src/shoelace-assets && cp -r node_modules/@shoelace-style/shoelace/dist/assets src/shoelace-assets [Bridgetown] Environment: development [ ... ] [Bridgetown] Generating… [Frontend] esbuild: frontend bundling started... [Bridgetown] Pagination: Complete, processed 1 pagination page(s) [Bridgetown] Done! 🎉 Completed in less than 3.95 seconds. [Bridgetown] [Bridgetown] Now serving at: http://localhost:4000 <<------- not changed here ---> [Bridgetown] http://172.17.0.1:4000
The behavior of the server itself is correct.
Version: 1.2.beta4
This was addressed via documentation: https://www.bridgetownrb.com/docs/configuration/puma
If the port to serve is modified in
/config/puma.yml
, the value is not transmitted to die output-methodThe behavior of the server itself is correct.
Version: 1.2.beta4