What's the common wisdom/best-practices regarding configuring an app to run on a different port while developing (say, 3001 instead of 3000)?
I've been searching the web for this over the past few days, and I've found two kinds of solutions: The first (as seen a few places on StackOverflow) is sort-of monkey-patching Rails::Server.default_options to override the :Port option. Another is to put "#\ -p 3001" at the beginning of the "config.ru" file. Anybody have any strong preference for either of these two methods, or for a third that I haven't found? It seems to me that the ideal would be if there was a line I could add to config/environments/development.rb , but I'm not sure what that would be. I'm particularly worried about potentially using a undocumented interface that could go away at any time. Alternatively, is there an argument out there that "modifying your app to use something other than 3000 is bad, it's better just to use the -p argument"? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/20150408182542.5fc8f924482d576dbaeda76d%40brisammon.fastmail.fm. For more options, visit https://groups.google.com/d/optout.
