From 04bde7daac10225a2e5f1d119222c8ff8590d994 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Duchesneau?= Date: Tue, 28 Nov 2023 09:40:28 -0500 Subject: [PATCH] improve tutorial to use 'spkg' file in last prod deployment --- docs/tutorials/substreams-sql.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/tutorials/substreams-sql.md b/docs/tutorials/substreams-sql.md index 142a50361..fe0ecc641 100644 --- a/docs/tutorials/substreams-sql.md +++ b/docs/tutorials/substreams-sql.md @@ -299,12 +299,16 @@ substreams alpha service deploy substreams.sql.yaml --prod * See that the database starts correctly and that the tables defined in `dbt` are being created correctly -* When you are happy with the results, verify or bump the `version` field in `substreams.sql.yaml`, then run `substreams pack substreams.sql.yaml` to generate the .spkg file. +* When you are happy with the results, verify or bump the `version` field in `substreams.sql.yaml`, you can generate the `cryptopunks-v0.1.0.spkg` file. + +```bash +substreams pack substreams.sql.yaml +``` ## Deploy your production package to the "hosted prod" environment ```bash -substreams alpha service deploy substreams.sql.yaml -e https://deploy.streamingfast.io --prod +substreams alpha service deploy cryptopunks-v0.1.0.spkg -e https://deploy.streamingfast.io --prod ``` -The production environment does not allow direct SQL access at the moment, so your apps will need to access the data to either the `rest` frontend or the `postgraphile` frontend. \ No newline at end of file +The production environment does not allow direct SQL access at the moment, so your apps will need to access the data to either the `rest` frontend or the `postgraphile` frontend.