Underneath the socket
Read this right after A Postgres socket. Every command here reads; none changes the cluster.
$ shc integration plugs -s pgwebSTACK PLUG SOCKET CONNECTED TOpgweb postgres postgres db.postgres$ shc integration ls -s pgwebCONSUMER STACK NAME CONSUMER PLUG PROVIDER STACK NAME PROVIDER SOCKET STATUS IDpgweb postgres db postgres connected 0pgweb has one plug, postgres, connected to db.postgres: deployment db,
socket postgres. The integration is that connection, stored on the cluster.
The password in vars.yaml is a secret variable, so the install moved it into
the vault and the deployment’s variables now point at it.
$ shc vault ls -s pgwebKEY SCOPEvar_postgres.password deploymentvar_postgres.password is that password, scoped to the deployment. -s lists
the deployment’s own keys; the cluster’s are listed by --scope global.
Before pgweb started, the socket ran a job in db’s container that made the
database pgweb and its owner pgweb with that password. Log in as that role:
$ shc exec -s db -S postgres-1 -- env PGPASSWORD=P@ssw0rd psql -h 127.0.0.1 -U pgweb -d pgweb -tAc 'select current_user'pgwebNext: A label and a location.
shc@docs:~$