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
You may need to allow network access to the launcher if Windows prompts you to do so.
62
74
63
75
### Build from Source
@@ -191,7 +203,6 @@ Click on `Edit model selection` to select models for your node.
191
203
openai
192
204
gemini
193
205
openrouter
194
-
VLLM
195
206
← Go Back
196
207
```
197
208
@@ -257,6 +268,8 @@ Use the `points` command to display how much you have earned!
257
268
dkn-compute-launcher points
258
269
```
259
270
271
+
You can also check out your [node dashboard](https://dria.co/edge-ai) for this information.
272
+
260
273
### Updating Manually
261
274
262
275
Using the `update` command you can check for updates & automatically update your compute node and launcher.
@@ -300,6 +313,62 @@ When you run a specific release your node & launcher will **not** be automatical
300
313
> The Dria Knowledge Network always considers the latest `minor` version as the active version; therefore,
301
314
> if the latest is `0.3.x` and you decide to run a smaller version like `0.2.x` you will most likely kept out of network due to protocol mismatch.
302
315
316
+
### Running in Background
317
+
318
+
#### Linux/MacOS
319
+
320
+
In Linux/MacOS systems you can use [`screen`](https://gist.github.com/jctosta/af918e1618682638aa82) command to run the launcher in the background.
321
+
322
+
First, create a screen with a given name (here we name it `dkn-compute-node`):
323
+
324
+
```sh
325
+
screen -S dkn-compute-node
326
+
```
327
+
328
+
Within the newly opened screen, start the node:
329
+
330
+
```sh
331
+
dkn-compute-launcher start
332
+
```
333
+
334
+
Now we will _detach_ from this screen and let it run in the background. For this, press <kbd>CTRL + A</kbd> and then press the <kbd>D</kbd> letter. You should now exit the screen, and see a `[detached]` log in the terminal that you have returned to.
335
+
336
+
At a later time, you can list your screens with:
337
+
338
+
```sh
339
+
screen -list
340
+
```
341
+
342
+
You can connect to a screen via its name directly:
343
+
344
+
```sh
345
+
screen -r dkn-compute-node
346
+
```
347
+
348
+
Within the screen, you can continue to use your launcher as you would normally, or stop the node with <kbd>CTRL+C</kbd>. You can `exit` within the screen to terminate it.
349
+
350
+
<!--
351
+
TODO: test these commands and then publish them here
352
+
#### Windows
353
+
354
+
In Windows systems, you can start the launcher in background using the `start` command:
355
+
356
+
```cmd
357
+
start /B dkn-compute-launcher.exe start
358
+
```
359
+
360
+
To list running processes:
361
+
362
+
```cmd
363
+
tasklist | findstr "dkn-compute"
364
+
```
365
+
366
+
To terminate the process:
367
+
368
+
```cmd
369
+
taskkill /IM dkn-compute-launcher.exe /F
370
+
``` -->
371
+
303
372
## Contributions
304
373
305
374
Contributions are welcome! You can start by cloning the repo:
You can uninstall the launcher binary along with the environment files and compute node binaries with the `uninstall` command:
399
+
You can uninstall the launcher binary along with the environment files and compute node binaries with the `uninstall` command.
400
+
401
+
Make sure you backup your private key within `.env` before removing these files, so that you do not lose your hard-earned $DRIA points. We have a `--backup` option for this purpose!
331
402
332
403
```sh
333
404
dkn-compute-launcher uninstall
334
-
```
335
405
336
-
> [!CAUTION]
337
-
>
338
-
> Make sure you backup your private key within `.env` before removing these files, so that you do not lose your hard-earned $DRIA points!
406
+
# will save the removed .env file to the given path
0 commit comments