Search…
Run the Stack
Once you have created the Organization, the Workgroup and invited participants, you can initialize the baseline stack so that you can begin to send and receive messages.
1
prvd baseline stack start
Copied!
During this process, you will be prompted to:
  • Select the appropriate Organization.
  • Select the appropriate Workgroup.
  • Select whether you want to authorize a refresh token. Choose (Y) if following the quickstart.
  • Select your System of Record. To Send a Protocol Message that is viewable in the terminal, select Ephemeral.
  • Select whether to expose a tunnel for the local API. Choose (Y) if following the quickstart.
  • Select whether to expose a tunnel for the local messaging endpoint. Choose (Y) if following the quickstart.

Monitoring Local Infrastructure

The following example shows how to tail the NATS server logs. This will allow you to monitor inbound protocol messages from counterparties. You can monitor any of the docker containers listed following the same pattern.
CLI
1
❯ docker ps
2
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3
2c682a2cf9b5 provide/baseline "./ops/run_consumer.…" 9 minutes ago Up 9 minutes (healthy) 8080/tcp baseline-local-consumer
4
6925c03ff7b6 provide/baseline "./ops/run_api.sh" 9 minutes ago Up 9 minutes (healthy) 0.0.0.0:8080->8080/tcp baseline-local-api
5
b044666d54b5 redis "docker-entrypoint.s…" 9 minutes ago Up 9 minutes (healthy) 0.0.0.0:6379->6379/tcp baseline-local-redis
6
8466c41510f6 postgres "docker-entrypoint.s…" 9 minutes ago Up 9 minutes (healthy) 0.0.0.0:5432->5432/tcp baseline-local-postgres
7
3bf57df3db11 provide/nats-server:2.5.0-PRVD "/bin/nats-server --…" 9 minutes ago Up 9 minutes (healthy) 5222/tcp, 6222/tcp, 0.0.0.0:4221-4222->4221-4222/tcp, 8222/tcp baseline-local-nats
8
9
# using the provide/nats-server container id...
10
docker logs 3bf5 -f
Copied!