You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the weekend, I realized that the exposed port dockerfile-rails generated when Thruster is present is insufficient to make Thurster work transparently. I summed up my findings here but long story short:
Thruster's default port is 80
Thruster's default Puma port is 3000
dockerfile-rails exposes 3000
Services like Traefik, which checks for EXPOSE directives to route traffic to the correct port, will bypass Thruster completely in these cases
I think the easiest solution is to keep exposing 3000 for the sake of backward compatibility (and everyone expects Rails to expose 3000 anyway) but bind Thruster to 3000 and Puma to e.g. 3001, something like this:
Over the weekend, I realized that the exposed port
dockerfile-rails
generated when Thruster is present is insufficient to make Thurster work transparently. I summed up my findings here but long story short:dockerfile-rails
exposes 3000EXPOSE
directives to route traffic to the correct port, will bypass Thruster completely in these casesI think the easiest solution is to keep exposing 3000 for the sake of backward compatibility (and everyone expects Rails to expose 3000 anyway) but bind Thruster to 3000 and Puma to e.g. 3001, something like this:
I can take a stab at a PR for it unless you have a better idea
The text was updated successfully, but these errors were encountered: