rails-server

Start the Rails development server

$ rails server

$ rails server -p [port]

$ rails server -b 0.0.0.0

$ rails server -e production

$ rails server -u [puma|thin|webrick]

$ rails server -d

rails server [-p port] [-b address] [-e environment] [-d] [-u server]

rails server starts a web server for the Rails application. By default, it uses Puma and listens on http://localhost:3000 in the development environment.
The server automatically reloads code changes in development mode, allowing rapid iteration without restarts. It displays request logs in the terminal, showing HTTP methods, paths, response codes, and timing information.
Binding to 0.0.0.0 makes the server accessible from other machines on the network, useful for testing on mobile devices or from other computers.

-p, --port PORT

Run server on specified port (default: 3000)

Bind to specified IP address (default: localhost)

Run in specified environment (development, test, production)

Run server as a daemon (background process)

Use specified Rack server (puma, thin, webrick, etc.)

Specify PID file path

Toggle development mode caching

Enable HTTP/2 early hints

Show help information

The default binding to localhost (127.0.0.1) only accepts connections from the local machine. Use -b 0.0.0.0 to accept external connections, but be aware of security implications.
Development mode is not suitable for production. It lacks performance optimizations and may expose debugging information. Always use -e production with a proper production configuration for deployed applications.
The daemon mode (-d) requires manual process management. Use process managers like systemd or Passenger for production deployments.

rails(1), puma(1), rails-routes(1), bundle(1)