Skip to content
SHC Docs

Underneath Nextcloud

Read this right after Nextcloud on Postgres. Every command here reads; none changes the cluster.

home01
$ shc integration ls -s cloud
CONSUMER STACK NAME CONSUMER PLUG PROVIDER STACK NAME PROVIDER SOCKET STATUS ID
cloud postgres db postgres connected 0
cloud s3 store s3 connected 0

cloud holds two integrations: its plug postgres connected to the socket of db, and its plug s3 connected to the socket of store.

Nextcloud’s configuration names the hosts those sockets gave it:

home01
$ shc exec -s cloud -S nextcloud -u www-data -- php occ config:system:get dbhost
prod.postgres.db:5432
$ shc exec -s cloud -S nextcloud -u www-data -- php occ config:system:get objectstore arguments hostname
prod.versitygw.store

Each name is the environment, the service and the deployment, the form both sockets’ data use.

The Postgres socket made a database and its owner for Nextcloud, as it did for pgweb. The install named neither, so the plug’s default names both for the deployment and its environment. Read the name Nextcloud holds, then find it in Postgres:

home01
$ shc exec -s cloud -S nextcloud -u www-data -- php occ config:system:get dbname
cloud_prod
$ shc exec -s db -S postgres-1 -- psql -U postgres -d postgres -tAc "select datname, pg_get_userbyid(datdba) from pg_database where datname = 'cloud_prod'"
cloud_prod|cloud_prod

The gateway’s socket runs no job. Nextcloud made its bucket itself, the first time it started.

Next: A vapp and an add-on.