On Wed, Apr 8, 2015 at 3:25 PM, Brian Sammon <[email protected]> wrote: > 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'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"? This seems utterly too trivial to be worrying about. For one thing it depends on what server you're using (webrick isn't the only option). If you don't want to have to add the '-p 3001' manually to whatever you're using just create a shell alias or script and be done with it. Alternately, if you're on a Mac, use Pow (http://pow.cx/) and ignore the whole issue :-) FWIW, -- Hassan Schroeder ------------------------ [email protected] http://about.me/hassanschroeder twitter: @hassan Consulting Availability : Silicon Valley or remote -- 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/CACmC4yCyQRfD0h%2BXzxE49hkDjH1WF%3DVFodqns_g23JQTxxGePg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
