CLI Reference

runnem run

Start a service and immediately view its logs.

Usage

runnem run <service>

Description

The run command is a convenient combination of runnem up and runnem log that starts a specific service and immediately begins streaming its logs. This is perfect for development workflows where you want to:

  1. Start a service
  2. Immediately see its output and logs
  3. Monitor its behavior in real-time

Note: Unlike runnem up, the run command requires a service name - you cannot run all services at once. This keeps the command focused and the log output manageable.

Examples

# Start the API service and view its logs
runnem run api

# Start the frontend service and watch its output
runnem run frontend

# Start a background worker and monitor its activity
runnem run worker

How it works

  1. Service Startup:

    • Performs all the same checks as runnem up
    • Validates dependencies and port availability
    • Starts the specified service
    • Handles any startup errors
  2. Log Streaming:

    • Immediately begins streaming logs from the service
    • Shows both stdout and stderr output
    • Continues until you press Ctrl+C
    • Uses the same log viewing logic as runnem log

Service Status

During startup, you'll see status messages followed by log output:

  • ๐Ÿš€ Starting service...
  • โœ… Started service (with URL if configured)
  • ๐Ÿ“‹ Viewing logs for service...
  • [Log output begins streaming]

When to Use Run

The run command is ideal when:

  • Developing a specific service and need immediate feedback
  • Debugging service startup issues
  • Testing configuration changes
  • Working on a single service in isolation
  • You want to see logs immediately after startup

Comparison with Other Commands

CommandPurposeLogsAll Services
runnem upStart servicesNoYes/Single
runnem runStart + logsYesSingle only
runnem logView logs onlyYesYes/Single

Best Practices

  1. Use run for active development on specific services
  2. Use regular up when starting multiple services
  3. Press Ctrl+C to stop viewing logs (service continues running)
  4. Check service URLs in the startup messages
  5. Monitor logs for any error patterns

Next Steps

Previous
runnem up