Skip to content

Conversation

snissn
Copy link

@snissn snissn commented Jul 16, 2025

[kicking netlify/vercel to make a preview link]

Copy link

netlify bot commented Jul 16, 2025

Deploy Preview for meek-salamander-66a264 ready!

Name Link
🔨 Latest commit f720df3
🔍 Latest deploy log https://app.netlify.com/projects/meek-salamander-66a264/deploys/6881284903e05a00089f0e1d
😎 Deploy Preview https://deploy-preview-12--meek-salamander-66a264.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@snissn
Copy link
Author

snissn commented Jul 21, 2025

  • I completely understand that eliza's documentation requires bun for installing, but afaik bun is intentionally a drop in replacement for node and eliza /should/ work with either bun or node. It's worth considering whether to carry that nuance forward to Derrek or into our tutorial, or simply reflect eliza's tutorial speification for using bun. Also maybe I am incorrect and bun /is/ a requirement and node is not (either way it's fairly minor to our goals in writing this tutorial and there's limited upside for us to fully encapsulate this nuance) We can rectify with a link to https://bun.com/docs/installation
  • we should talk user through elizaos create recall-eliza-bot for the install i think we want to suggest pg, openai, yes, open api key
│
◇  Which database would you like to use?
│  Pglite (Pglite)
│
◇  Which AI model would you like to use?
│  OpenAI
│
◇  Create project "recall-eliza-bot" in eliza-test?
│  Yes
┌  🤖 OpenAI API Configuration
│
◇  API Key Information ─────────────────────────────────────────╮
│                                                               │
│  Get your API key from: https://platform.openai.com/api-keys  │
│                                                               │
├───────────────────────────────────────────────────────────────╯
│
◇  Enter your OpenAI API key:
│  ▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
│
  • if user sets up open api key in the earlier step they don't need to add it to their env
  • Create .env at the project root: the eliza bot set up creates an .env file with text below so the wording should be Append to the .env file
OPENAI_API_KEY=sk-...
PGLITE_DATA_DIR=/Users/../dev/recall/eliza-test/recall-eliza-bot/.eliza/.elizadb

running elizaos start
error:

[2025-07-21 21:10:04] WARN: Failed to import project from /Users/michaelseiler/dev/recall/eliza-test/recall-eliza-bot/src/index.ts:
[2025-07-21 21:10:04] ERROR: Error loading project:
    message: "(Error) Could not find project entry point"
    stack: [
      "Error: Could not find project entry point",
      "at loadProject (/Users/michaelseiler/dev/recall/eliza-test/recall-eliza-bot/node_modules/@elizaos/cli/dist/index.js:4431:17)",
      "at processTicksAndRejections (native:7:39)"
    ]

Also I see an agent named "Eliza" not "Recall Trader"
image

image

@nijoe1
Copy link
Collaborator

nijoe1 commented Jul 23, 2025

  • I completely understand that eliza's documentation requires bun for installing, but afaik bun is intentionally a drop in replacement for node and eliza /should/ work with either bun or node. It's worth considering whether to carry that nuance forward to Derrek or into our tutorial, or simply reflect eliza's tutorial speification for using bun. Also maybe I am incorrect and bun /is/ a requirement and node is not (either way it's fairly minor to our goals in writing this tutorial and there's limited upside for us to fully encapsulate this nuance) We can rectify with a link to https://bun.com/docs/installation

that's true but currently bun is just the package manager

  • we should talk user through elizaos create recall-eliza-bot for the install i think we want to suggest pg, openai, yes, open api key

included some comments to address this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants