Merge latest

.vscode/launch.json

@@ -8,8 +8,8 @@
       "type": "pwa-chrome",
       "request": "launch",
       "name": "Launch Chrome against localhost",
-      "url": "http://localhost:3003",
-      "sourceMap": true,
+      "url": "https://localhost:3003",
+      //   "sourceMap": true,
       "webRoot": "${workspaceFolder}/client",
       "trace": true,
       "sourceMapPathOverrides": {

.vscode/settings.json

@@ -4,5 +4,8 @@
   "prettier.configPath": "./.prettierrc.json",
   "eslint.workingDirectories": ["./client", "./core", "./server"],
   "typescript.tsserver.experimental.enableProjectDiagnostics": true,
-  "cSpell.enabled": false
+"cSpell.enabled": false,
+"[typescript]": {
+    "editor.defaultFormatter": "vscode.typescript-language-features"
+}
 }

README.md

@@ -7,6 +7,8 @@ Thoth is a multishot system builder. It leverages a visual coding style interfac
 You will need **yarn or npm** and **Docker** installed, along with **Node.js 16 or higher**. We use Docker to run a local Postgres database. You can skip the docker and install postgres directly, but you are almost always better off just using Docker.
 For **Linux** and **MAC** users, **sleep** and **concurently** commands must be installed in the machine.
 
+Install xvfb, chromium and ffmpeg
+
 First, clone and set up Thoth
 
 ```

appspec.yml

@@ -16,4 +16,4 @@ hooks:
   ApplicationStart:
     - location: scripts/application_start.sh
       timeout: 300
-      runas: root
+      runas: root

deployment_steps.md

@@ -0,0 +1,41 @@
+# Thoth Deployment steps
+
+1. Setup AWS CICD (https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines.html)
+
+2. Login aws EC2 server using ssh
+
+3. Install node js (https://github.com/nodesource/distributions#debinstall)
+4. Install pm2 (https://pm2.keymetrics.io/) and run pm2 startup command
+
+5. Install docker (https://docs.docker.com/engine/install)
+
+6. Generate SSL certificate -` sudo certbot certonly --standalone --agree-tos --preferred-challenges http -d <domainName>`
+
+   sudo certbot certonly --manual --agree-tos --preferred-challenges dns -d superreality.com,thoth.superreality.com
+
+7. Go to the project root path
+8. Copy certificates
+
+   - Copy generated certificates into client dir. (tooth/client/certs)
+     - `sudo cp /etc/letsencrypt/live/superreality.com/privkey.pem /opt/thoth/packages/client/certs/key.pem`
+     - `sudo cp /etc/letsencrypt/live/superreality.com/cert.pem /opt/thoth/packages/client/certs/cert.pem`
+   - Copy generated certificates into server dir. (tooth/server/certs)
+     - `sudo cp /etc/letsencrypt/live/superreality.com/privkey.pem /opt/thoth/packages/server/certs/key.pem`
+     - `sudo cp /etc/letsencrypt/live/superreality.com/cert.pem /opt/thoth/packages/server/certs/cert.pem`
+
+9. Open client .env file (vim client/.env).
+
+- Change following env params REACT_APP_LAPI_ROOT_URL, REACT_APP_API_ROOT_URL, REACT_APP_API_ROOT_URL_PROD, REACT_APP_CORS_URL, REACT_APP_API_URL,REACT_APP_SEARCH_FILE_URL
+
+10. Open core .env file (vim client/.env).
+
+- Change following env params REACT_APP_API_ROOT_URL, API_URL
+
+11. Open server .env file (vim client/.env).
+
+- Change following .env params API_URL, PGUSER, PGHOST, PGPASSWORD, PGDATABASE, GOOGLE_APPLICATION_CREDENTIALS, WITAI_KEY, UBER_DUCK_KEY, UBER_DUCK_SECRET_KEY, OPENAI_API_KEY, HF_API_KEY
+  Note: In GOOGLE_APPLICATION_CREDENTIALS set path of credential json file
+
+12. Run following commands
+    - `pm2 --name thoth start "yarn run dev"`
+    - `pm2 save`

docs/docs/developers/agents/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Agents",
+  "position": 4
+}

docs/docs/developers/agents/agentStructure.md

@@ -0,0 +1,50 @@
+---
+title: Structure of an Agent
+description: What is an Agent and how is it structured
+hide_table_of_contents: false
+sidebar_position: 1
+---
+
+# Agent Architecture of an Agent
+
+## Data Structure
+
+speaker -- key of who is speaking, probably discord id of person chatting with agent
+agent -- key of this particular agent receiving, since each agent can be different, probably supplied from agent settings (depends on connector)
+client -- type of client -- discord, xrengine, etc
+channel -- where it is received, i.e. discord channel or xrengine room (at least ideally, discord does this but other connectors might need work)
+entity -- information about this running entity instance (entity number, etc)
+roomInfo -- info from the world, this is how we do text gen from worlds ideally
+output -- actual information received
+
+### Input
+
+This is the input which the agent is receiving. Usually a snippet of conversation, but could be anything that is being processed by the particular agent.
+
+### Speaker
+
+The person interacting with or engaging with the Agent. This helps to store associated data between the speaker and the agent. Could be a user ID, a user name, etc.
+
+### Agent
+
+Key of this particular agent receiving the input, since each agent can be different, probably supplied from agent settings (depends on connector). Agent is and ID.
+
+### Client
+
+Type of client that is interacting with the Agent (discord, XR Engine, twitter, web, etc)
+
+### Channel Id
+
+Where it is received from, i.e. discord channel or xrengine room (at least ideally, discord does this but other connectors might need work)
+
+### Entity
+
+Information about this running entity instance (entity number, etc)
+
+### roomInfo
+
+Info from the world, this is how we do text gen from worlds ideally
+
+### Output (output socket)
+
+This is the original input that was received.