fluencelabs/gitbook-docs
1
0
Fork 0
mirror of https://github.com/fluencelabs/gitbook-docs synced 2025-06-15 16:01:32 +00:00
Code Issues Projects Releases Wiki Activity

GitBook: [main] 53 pages and 14 assets modified

Browse Source
This commit is contained in:
boneyard93501
2021-05-08 00:47:34 +00:00
committed by gitbook-bot
parent 84e814d02d
commit b383a8a319
29 changed files with 40 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
development_development/development_reward_block_app/development_sqlite.md
View File

@ -83,7 +83,6 @@ wget https://github.com/fluencelabs/sqlite/releases/download/v0.10.0_w/sqlite3.w
mv sqlite3.wasm artifacts/
```
Run `./build.sh` and check the artifacts for the expected wasm files
Like all Fluence services, Ethqlite needs a [service configuration](https://github.com/fluencelabs/examples/blob/main/multi-service/ethqlite/Config.toml) file, which looks a little more involved than what we have seen so far.
@ -114,7 +113,6 @@ name = "ethqlite"
Let's break it down:
* the first \[\[module\]\] section
* specifies the _sqlite3.wasm_ module we pulled from the repo,
* allocates memory, where each page is about 64KB, and
@ -371,7 +369,6 @@ Particle id: 2fb4a366-6f40-46c1-9329-d77c6d03dfad. Waiting for results... Press
===================
```
If you run the init script again, you will receive an error _"Service already initiated"_, so we can be reasonably confident our code is working and it looks like our Ethqlite service is up and running on the local node.
Due to the security concerns for our database, it is not advisable, or even possible, to use an already deployed Sqlite service from the Fluence Dashboard. Instead, we deploy our own instance with our own \(secret\) client seed. To determine which network nodes are available, run: