-
Notifications
You must be signed in to change notification settings - Fork 0
/
dev.html
66 lines (64 loc) · 3.12 KB
/
dev.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
<!doctype html>
<html>
<head>
<title>Everlife Node for Developers</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="github-markdown.css">
<style>
.markdown-body {
box-sizing: border-box;
min-width: 200px;
max-width: 980px;
margin: 0 auto;
padding: 45px;
padding-top: 15px;
}
@media (max-width: 767px) {
.markdown-body {
padding: 15px;
}
}
</style>
</head>
<body class="markdown-body">
<!DOCTYPE HTML>
<html>
<head>
<meta charset="utf-8">
</head>
<body>
<h1 id="everlife-node-for-developers">Everlife Node for Developers</h1>
<h2 id="troubleshooting">Troubleshooting</h2>
<p>Processes are managed by process managers like <a href="https://pm2.io/">pm2</a> and <a href="https://www.npmjs.com/package/@elife/pm2">@elife/pm2</a>. The logs for these can be found under your <code>$HOME/everlife</code> and in the <code>logs</code> folder in this repository. These logs are very useful for debugging/troubleshooting any issues you may face.</p>
<h2 id="package-overview">Package Overview</h2>
<p>The Everlife Server Node will download and manage all the other dependencies needed to run the avatar, install the skills, communicate with the user and soon. Configuration, updates, and troubleshooting can all take place from here.</p>
<p>This package itself can be thought of as the core of the avatar - it keeps the rest of the avatar (the AI brain, the immortal feed, the database etc) alive and stable. That is it's main responsibility (after all - it has to <em>live forever</em>).</p>
<h3 id="everlife-server-node-architectural-overview">Everlife Server Node Architectural Overview</h3>
<p><img src="elife.png" alt="Everlife Architecture" /></p>
<p>As you can see from the architecture above, the server node delegates all other work to other core processes (a.l.a Erlang's supervisor trees).</p>
<p>These core processes include:</p>
<ol>
<li>The EverChain Feed and Replication</li>
<li>A Database for storing working data</li>
<li>A Skill Manager for installing, running, and managing skills<ul>
<li>Infrastructure Skills (as hub/as host/…)</li>
<li>Worker skills (twitter svc, vanity address, …)</li></ul></li>
<li>A Communication Manager for installing, running, and managing communication channels<ul>
<li>Telegram channel</li>
<li>Messenger channel</li>
<li>Alexa channel</li>
<li>Web channel</li>
<li>…</li></ul></li>
<li>An AI for understanding and managing user interaction and strategies for earning<ul>
<li>Intent Resolution</li>
<li>NLP</li>
<li>Generative Dialogues (python with microservices relay…)</li>
<li>…</li></ul></li>
<li>The stellar blockchain interface for payments, receipts, and smart contracts.</li>
<li>The interface to the polkadot relay chain to integrate with other blockchains.</li>
</ol>
<p>Because all the code is open source you should be able to go through and understand any part that interests you in more detail. Otherwise you are welcome to <a href="https://discord.gg/TDyRSr4">ping us on our Discord channel</a> and ask any questions or doubts you may have.</p>
</body>
</html>
</body>
</html>