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:
- Start a service
- Immediately see its output and logs
- 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
Service Startup:
- Performs all the same checks as
runnem up
- Validates dependencies and port availability
- Starts the specified service
- Handles any startup errors
- Performs all the same checks as
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
Command | Purpose | Logs | All Services |
---|---|---|---|
runnem up | Start services | No | Yes/Single |
runnem run | Start + logs | Yes | Single only |
runnem log | View logs only | Yes | Yes/Single |
Best Practices
- Use
run
for active development on specific services - Use regular
up
when starting multiple services - Press Ctrl+C to stop viewing logs (service continues running)
- Check service URLs in the startup messages
- Monitor logs for any error patterns
Next Steps
- runnem rerun - Restart a service and view logs
- runnem log - View logs without starting services
- runnem up - Start services without logs
- Service Management - Understand service lifecycle management