You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wait for the solver to start when `🟡 SOL solver registered` is logged, and then, in another terminal window, run:
@@ -213,6 +219,25 @@ Otherwise, if you don't have a GPU:
213
219
./stack resource-provider
214
220
```
215
221
222
+
### run saas
223
+
224
+
The generic-dcn repo also comes with a saas layer that can be used as a web2 layer to the underlying web3 stack.
225
+
226
+
The api will run using a `WEB3_PRIVATE_KEY` and essentially act as a job creator on behalf of registered users.
227
+
228
+
This means you can open up your decentralized compute network to a wider audience who might not have access to metamask or other web3 tools.
229
+
230
+
Once the core network is up and running as described above, you can run the saas layer as follows:
231
+
232
+
**NOTE** it's important that you started the solver using the `./stack solver --server-url http://172.17.0.1:8080` command as described above.
233
+
234
+
```bash
235
+
docker-compose build
236
+
docker-compose up -d
237
+
```
238
+
239
+
Now you should be able to access the saas layer using http://localhost
240
+
216
241
### run faucet
217
242
218
243
To run the faucet container so you can test with other user accounts:
@@ -447,6 +472,18 @@ You can now start and stop the various services using `systemd` and see logs usi
447
472
448
473
Make sure you start the solver first.
449
474
475
+
### running the saas layer
476
+
477
+
To run the saas layer in production it's important to use another machine than the solver so the saas api can speak to the solver using it's public http(s) endpoint.
478
+
479
+
To run the various services there are a few options:
480
+
481
+
* use the `docker-compose.yaml` file but change some values
482
+
* run the various services using another tool like k8s (they are all docker based services)
483
+
* run the various services using systemd
484
+
485
+
We have left this choice to the reader as it depends on the environment you are deploying to.
0 commit comments