diff --git a/docs/functions/sync_handlers_event_data_sync_wasm_handler.syncWasmEventData.html b/docs/functions/sync_handlers_event_data_sync_wasm_handler.syncWasmEventData.html index a480dea..98d89ee 100644 --- a/docs/functions/sync_handlers_event_data_sync_wasm_handler.syncWasmEventData.html +++ b/docs/functions/sync_handlers_event_data_sync_wasm_handler.syncWasmEventData.html @@ -18,7 +18,7 @@
+ -
Syncs all the public info from an ixo blockchain to an instance of PostgreSQL.
- - -Refer to src/schema/api.yml or visit the online version.
- +Syncs all the public info from an ixo blockchain to an instance of PostgreSQL. It gets fed from a ixo-blocksync-core database in order to speed up indexing and put less strain on nodes, which means you need an ixo-blocksync-core database connection in order to run this.
+
+For now the only source for information is a ixo-blocksync-core database connection, but we plan on expanding that to different sources in the near future.
+
docker build -t ixofoundation/ixo-blocksync:latest .
docker compose up -d
-The server exposes a Graphql api endpoint at /graphql
which is set up using Postgraphile along with some plugins:
src/seed/json_exports
directoryDATABASE_URL
in .env
with the correct username, password and hostLocal PostgreSQL
-npx prisma migrate reset
npx prisma generate
npx ts-node src/seed/seed.ts
-
-Docker PostgreSQL
-docker build .
docker compose up block-sync-db
npx prisma generate
npx ts-node src/seed/seed.ts
-
+A graphiql playground gets exposed at the endpoint /graphiql
where you can play around, test queries and see the schemas.
We also generate and expose the full graphql schema file (schema.graphql) under the endpoint /api/graphql_schema
if you need it to generate clients.