A recent commit changed the “unicorn port” from 9292 to 3000. I don’t see any way to change the port now and this is confliciting with another rails site I have running on 3000. Previously, I’ve been running discourse as bundle exec rails server --port=3001, but this no longer works as unicorn is no…

Changed that line in bin/rails to point to 3001 and it seems to work now. Should that line be an ||=?

Why do you have another Rails site running in the same container as Discourse?

[imagen] typeoneerror: Any way to work around this? There are 2 schools of thought when it comes to launching a rails server in development. The @sam school of thought, where you want to keep console pristine cause you are a fanatical puts debugger . That way you can just add puts statements …

[imagen] sam: Note, I had to push a few fixes to make this post true, so pull latest. You rock, @sam , cheers!

Or you subscribe to @LeoMcA ’s school of thought, where you’re a fanatical puts debugger, but launch with rails s, so you have to squint really hard to see what you want among all the rails logs. I feel like a fool.

Yeah, I launch my local dev with Puma via Foreman so I think I get “puts” in the Foreman logs and “logger.log” in the Rails log, so I think I’m with the @sam school in my other project. Nice to have these two schools for Discourse local dev now!

FYI, foreman support has just been removed per: [imagen] DEV: remove foreman gem and unsupported Procfile discourse approved commit DEV: remove forem…

[imagen] LeoMcA: Or you subscribe to @LeoMcA ’s school of thought, where you’re a fanatical puts debugger, but launch with rails s , so you have to squint really hard to see what you want among all the rails logs. I just added an option to avoid all that squinting, you can now use DISCOURSE_D…

Nice! I’ve been using RAILS_LOGS_STDOUT=0 rails s, but this allows showing warnings/errors rather than binning everything :heart_eyes:

Cambiar puerto de unicorn de 3000 en desarrollo

Desarrollador

typeoneerror (Benjamin Borowski) 14 Agosto, 2018 22:43 4

Donno, Matt. I followed Beginners Guide to Install Discourse on macOS for Development which didn’t have me setting up containers (I’m assuming you’re referring to Docker or something related?).

Tema		Respuestas	Vistas
The site setting `port` can no longer be set based on Rails environment Development	1	747	2 Enero 2018
Switching Puma ↔ Unicorn Self-hosting unsupported-install	5	840	30 Noviembre 2022
Bundle exec rails server --binding=0.0.0.0 Development	3	3502	22 Marzo 2021
Issue in setup discourse on ubuntu server Self-hosting dev-install	10	1655	21 Junio 2019
Why would discourse want to connect to port 3000 Support	6	1264	23 Octubre 2020

Cambiar puerto de unicorn de 3000 en desarrollo

Temas relacionados