Pular para o conteúdo principal

FAQ

informação

This FAQ will be expanded as common questions are collected from clients.

General​

What is a "fork"?​

A fork is your own full copy of the Cactus base template. You have complete freedom to customize it — create components, add pages, change styles, redesign the layout, etc.

Where do I start customizing?​

The easiest starting points are:

  • app/config/theme.config.ts — Brand colors
  • app/config/routes.config.ts — Pages/routes
  • app/config/layout.config.ts — Layout component

But you're not limited to these. You can modify any file, create new components, add libraries — the fork is fully yours.

Can I add custom pages?​

Yes. Create a new file in app/routes/ and register it in routes.config.ts. You can also create custom components, hooks, stores, etc. See Routes customization.

What can't I change?​

The only thing you should avoid modifying directly is the @cactus-agents/* packages — they are npm dependencies updated via pnpm update. If you need something the SDK doesn't support, contact the Cactus team.

Technical​

Why do I need both .dev.vars and .env?​

.dev.vars is read by the SSR server (Wrangler/Cloudflare Workers) and .env is read by the build tool (Vite). Both are needed locally.

How do I update business logic?​

Run pnpm update @cactus-agents/* to get the latest packages. See SDK Updates.

Where do I set production environment variables?​

In the Cloudflare Workers dashboard. See Deployment.

Support​

Contact the Cactus team for:

  • Access tokens for GitHub Packages
  • API credentials
  • Deployment assistance
  • Bug reports