Supernothing

.eslintignore

@@ -4,6 +4,5 @@ node_modules/
 test/
 scripts/
 .eslintrc.js
-jest.config.js
 src/libs
 @types

.github/workflows/pull_request_ci.yml

@@ -58,11 +58,4 @@ jobs:
 
       - name: Install Dependencies
         run: yarn install
-        if: steps.core_diff.outcome != 'success' && (steps.no_thoth_core_label.outcome == 'success' || contains(github.event.pull_request.labels.*.name, 'thoth-core'))
-
-      # - name: Publish next canary release of @thothai/thoth-core
-      #   run: git checkout yarn.lock && yarn publish:canary
-      #   if: steps.core_diff.outcome != 'success' && (steps.no_thoth_core_label.outcome == 'success' || contains(github.event.pull_request.labels.*.name, 'thoth-core'))
-#       - name: Publish next canary release of @latitudegames/thoth-core
-#         run: git checkout yarn.lock && yarn publish:canary
-#         if: steps.core_diff.outcome != 'success' && (steps.no_thoth_core_label.outcome == 'success' || contains(github.event.pull_request.labels.*.name, 'thoth-core'))
+        if: steps.core_diff.outcome != 'success' && (steps.no_thoth_core_label.outcome == 'success' || contains(github.event.pull_request.labels.*.name, 'thoth-core'))

LICENSE

@@ -2,10 +2,6 @@ Copyright (c) 2022 Latitude, Inc.
 All rights reserved.
 https://www.latitude.io
 
-Licensed under the Apache License version 2.0 (the "License");
-You may not use this software except in compliance with the License.
-You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0
-
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0

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
 
 ```
@@ -38,15 +40,11 @@ yarn run dev:windows
 We use dotenv-flow for local environment variable management
 
 Go to client folder, and create a new file called .env.local -- copy and .env vars you want to set from .env there
-If you are developing independently and are not a member of Latitude Games team, set **REACT_APP_USE_LATITUDE=false**
 
 Go to server folder, and create a new file called .env.local -- copy and .env vars you want to set from .env there
-If you are developing independently and are not a member of Latitude Games team, set **USE_LATITUDE=false**
 
 ## Client Setup
 
-1. Generate a [Personal Access Token](https://github.com/settings/tokens) on Github which will allow you to install private latitude packages. Make sure you check the `write:packages` option. (`read:packages` will suffice as well if you aren't planning on publishing new versions of @thothai/thoth-core)
-1. In your `~/.bashrc`, append the line `export NPM_TOKEN=YourTokenGoesHere`, and restart your terminal (you can run `source ~/.bashrc` to do so)
 1. Clone the repository
 1. Navigate to the project root by running `cd thoth`
 1. Run `yarn install` to install project dependencies
@@ -57,37 +55,6 @@ If you are developing independently and are not a member of Latitude Games team,
 1. Core the contents of `core/.env.default` to `core/.env` and modify the secrets as necessary
 1. Step 2 in Monorepo Development Setup
 
-## Monorepo Development
-
-Within the yarn workspace we need to be mindful of which version of the shared package @thothai/thoth-core we are including in our local development setup and our deploys to Netlify.
-
-You can either:
-
-1. Target a published version of [@thothai/thoth-core](https://github.com/latitudegames/thoth/packages/983711) in client/package.json
-2. Or actively develop against the current state of the repository. (By ensuring that client/package.json is targetting the same version of @thothai/thoth-core that is currently listed in core/package.json)
-
-If you are testing with the Latitude API locally you can point the latitude api to your local thoth package:
-
-1.  making the dependance `"@thothai/thoth-core": "../thoth/core"`
-    or
-2.  run `yarn link` inside '/packages/core' and then copy the command it generates for you and run that command in your root latitude api path. This will tell your latitude api to use the simlinked version of thoth that your actively developing.
-
-## @thothai/thoth-core CI
-
-### Testing
-
-On Pull Request, GitHub actions will first determine if the diff contains changes in the `core` directory. If so
-and there isn't an active `thoth-core` labelled PR already open - it will proceed with building and deploying a Canary Release
-to GitHub packages. There can only be one `thoth-core` labelled PR active at a time, so if one exists additional PR's will be labelled `thoth-core-draft` by the CI. This `thoth-core-draft` label can be removed, and the CI re-run to build a canary once the unique `thoth-core` label position has been vacated.
-
-The latest canary release can be tested and installed locally with `yarn add @thothai/thoth-core@canary`. The Netlify Deploy Preview is configured to sense `thoth-core` PR's as well and targets the latest canary release, but it runs concurrently to the canary publishing process. You can test a canary release of `thoth-core` on your branch's Deploy Preview by re-deploying from the Netlify UI for your branch. It is important to note that `thoth-core-draft` PR's will still have a deploy preview on Netlify, but will be building with the latest canary release of `thoth-core` which may be unrelated to that PR's changes until it had it's own canary release and been re-deployed.
-
-### Releases
-
-When a `thoth-core` PR has been merged with main, the CI will create a prerelease based on the last commit, publish
-@thothai/thoth-core to GitHub packages and take care of incrementing the patch version in core/package.json to prepare
-for the next prerelease.
-
 ## Available Scripts
 
 In the project directory, you can run:

TODO.md

@@ -0,0 +1,7 @@
+[] Create a window registry for layout
+[] Switch workspace windows to registry
+[] Modularize the individual workspace code
+[] Migrate cor efunctionality to feathers
+[] Connect feathers to Subabase
+[] Localize layouts to worksapces
+[] Improve design system reusability

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.

lerna-debug.log

@@ -0,0 +1,23 @@
+0 silly argv {
+0 silly argv   _: [ 'exec' ],
+0 silly argv   scope: '@thothai/thoth-core',
+0 silly argv   args: [],
+0 silly argv   '--': [ 'yarn', 'start' ],
+0 silly argv   lernaVersion: '4.0.0',
+0 silly argv   '$0': 'node_modules/.bin/lerna'
+0 silly argv }
+1 notice cli v4.0.0
+2 verbose rootPath /home/beast/Documents/GitHub/nothing-thoth
+3 error JSONError: Expected double-quoted property name in JSON at position 172 while parsing '{  "name": "@thothai/thoth-sharedb",  ' in packages/sharedb/package.json
+3 error
+3 error    7 |   "scripts": {
+3 error    8 |     "start": "nodemon index.ts",
+3 error >  9 |   },
+3 error      |   ^
+3 error   10 |   "keywords": [],
+3 error   11 |   "author": "",
+3 error   12 |   "license": "ISC",
+3 error
+3 error     at parseJson (/home/beast/Documents/GitHub/nothing-thoth/node_modules/parse-json/index.js:29:21)
+3 error     at parse (/home/beast/Documents/GitHub/nothing-thoth/node_modules/@lerna/project/node_modules/load-json-file/index.js:15:9)
+3 error     at module.exports (/home/beast/Documents/GitHub/nothing-thoth/node_modules/@lerna/project/node_modules/load-json-file/index.js:18:47)