On most *nix systems, listening on a port below 1024 requires super-user (root) access. All the ports above 1024 do not, removing the need to execute the ruby command using root access.
As far as why 3000 specifically, I don't believe it has any particular significance, although you'd have to research back to the early days of Rails to know if there was a specific compelling reason this port was chosen as the default. Typically you only use that in development, because in a production environment you will have a web server like nginx that will operate on the normal web port (80) -Jason On Sep 17, 2014, at 3:23 PM, Jonathan Haar <[email protected]> wrote: > Why does the rails server default to port 3000? -- 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/E8ACDE20-B1CF-4592-8656-4C438C864636%40datatravels.com. For more options, visit https://groups.google.com/d/optout.
