For basic setup instructions, see the Quickstart Guide.
Development Scripts
Here are the available development commands:Environment Variables
API Variables
For API environment variables, check/apps/api/.env.example.
Available Environment Variables for API
Available Environment Variables for API
DATABASE_URL: Database connection string, you can get it from Neon Console after creating a new databaseJWT_SECRET: JWT secret key, useopenssl rand -base64 32to generateCOOKIE_KEY: Cookie key, it uesed to be cookie name to store JWT token. You can use any string as the cookie key, but it should be the same as the one in the admin frontend. default totoken
Admin Frontend Variables
For Admin Frontend environment variables, check/apps/admin/.env.example.
Available Environment Variables for Admin Frontend
Available Environment Variables for Admin Frontend
VITE_APP_NAME: Application name, it will be used as the title of the admin panelVITE_API_URL: API endpoint URL, it will be used to fetch data from the APIVITE_ENABLE_DEVTOOLS: Enable/disable development tools, default tofalseVITE_EDITOR: Editor configuration, default tovscode, you can usecursorif you are using Cursor IDE
Testing
The project includes several testing utilities:Component Development
We use Storybook for component development and testing:Documentation
To work on the documentation locally:Code Quality
The project uses several tools to maintain code quality:- ESLint: For code linting
- simple-git-hooks: For pre-commit checks
- lint-staged: For running linters on staged files
- commitlint: For commit message conventions
Troubleshooting
Can't run the development script
Can't run the development script
If you’re having trouble running the development script:
- Make sure you have installed the project dependencies using pnpm
- Make sure you have set up the environment variables correctly
Next Steps
- Learn about our routing system
- Explore state management
- Read the deployment guide