By default, when you run
steampipe query, Steampipe will start the database and shut it down at the end of the query command or session. In this case, you cannot run another query until the first query has completed, and you cannot start another instance of Steampipe until the query completes and Steampipe shuts down. Additionally, the database only listens on the loopback address (127.0.0.1) - You cannot connect over the network.
Alternatively, you can run Steampipe in service mode. Running
steampipe service start will run Steampipe as a local service, exposing it as a database endpoint for connection from any Postgres compatible database client. If the Steampipe service is started by
steampipe service start, multiple parallel query sessions can be run.
When you run
steampipe service start, Steampipe will start in service mode. Steampipe prints connection information to the console that you can use in connection strings for your application or 3rd party tools:
$ steampipe service startSteampipe database service is now running:Host(s): localhost, 127.0.0.1, 192.168.1.64Port: 9193Database: steampipeUser: steampipePassword: f6c8-4af0-a563Connection string:postgres://steampipe:f6c8-4af0-a563@localhost:9193/steampipe?sslmode=disableSteampipe service is running in the background.# Get status of the servicesteampipe service status# Restart the servicesteampipe service restart# Stop the servicesteampipe service stop
Once the service is started, you can connect to the Steampipe from tools that integrate with Postgres.
To stop the Steampipe service, issue the
steampipe service stop command.