* feat(backend): credential swap * ci: formatting * fix: importing is hard okay * fix: spelln' is hard * feat: better credential provider handling * docs: update the imports locations * fix: test credentials + formatting * feat: drop continuous read mode * fix: lint * feat: fallback credentials * feat: charge for credential useage and have a bad backup mechnism * fix: don't save default credentials + add d_id * fix: formatting * feat: basic encryption/decryption * ref: move files around * ref: sign all blocks out of their credentials * ref: update target to match a new, and encrypted future * wip: llm provider merger * don't delete `credentials` input on nodes * fix llm block ci issues * updated get AICredentials * fix fix * insert migration to move integration credentials from `auth.user` metadata to `platform.User.metadata` * fixed migration * add migration for existing user integration credentials * disabled reddit and email block * fix credential handling in LLM blocks * add other secret fields to credential scrubber migration * add other secret fields to credential scrubber migration (vol. 2) * fix: pr fixes * fix: mock funciton * add encrypted values --------- Co-authored-by: Reinier van der Leer <pwuts@agpt.co> Co-authored-by: SwiftyOS <craigswift13@gmail.com> Co-authored-by: Aarushi <50577581+aarushik93@users.noreply.github.com> Co-authored-by: Aarushi <aarushik93@gmail.com> |
||
---|---|---|
.. | ||
.storybook | ||
public | ||
src | ||
.env.development | ||
.env.example | ||
.env.production | ||
.eslintrc.json | ||
.gitignore | ||
.prettierignore | ||
.prettierrc | ||
Dockerfile | ||
README.md | ||
components.json | ||
next.config.mjs | ||
package.json | ||
playwright.config.ts | ||
postcss.config.mjs | ||
sentry.client.config.ts | ||
sentry.edge.config.ts | ||
sentry.server.config.ts | ||
tailwind.config.ts | ||
test-runner-jest.config.js | ||
tsconfig.json | ||
webpack.config.js | ||
yarn.lock |
README.md
This is the frontend for AutoGPT's next generation
Getting Started
Run the following installation once.
npm install
# or
yarn install
# or
pnpm install
# or
bun install
Next, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx
. The page auto-updates as you edit the file.
For subsequent runs, you do not have to npm install
again. Simply do npm run dev
.
If the project is updated via git, you will need to npm install
after each update.
This project uses next/font
to automatically optimize and load Inter, a custom Google Font.
Deploy
TODO
Storybook
Storybook is a powerful development environment for UI components. It allows you to build UI components in isolation, making it easier to develop, test, and document your components independently from your main application.
Purpose in the Development Process
- Component Development: Develop and test UI components in isolation.
- Visual Testing: Easily spot visual regressions.
- Documentation: Automatically document components and their props.
- Collaboration: Share components with your team or stakeholders for feedback.
How to Use Storybook
-
Start Storybook: Run the following command to start the Storybook development server:
npm run storybook
This will start Storybook on port 6006. Open http://localhost:6006 in your browser to view your component library.
-
Build Storybook: To build a static version of Storybook for deployment, use:
npm run build-storybook
-
Running Storybook Tests: Storybook tests can be run using:
npm run test-storybook
For CI environments, use:
npm run test-storybook:ci
-
Writing Stories: Create
.stories.tsx
files alongside your components to define different states and variations of your components.
By integrating Storybook into our development workflow, we can streamline UI development, improve component reusability, and maintain a consistent design system across the project.