Configuration Files
A guide to the main configuration files in your ZapStart application.
On this page
Overview
ZapStart uses a centralized configuration approach that makes customizing your application simple and straightforward. Instead of modifying code throughout your project, you'll primarily work with two main configuration files.
Main Configuration Files
frontend/configFront.js
This file contains all frontend-specific settings including:
- Application name, description, and branding
- SEO configuration
- Pricing plans and display options
- Authentication settings
- Email templates and contact information
- Theme and color customization
Simply open this file and follow the detailed comments next to each setting. Every option is clearly documented with examples right in the file.
backend/configBack.js
This file contains all backend-specific settings including:
- API and service configurations
- Payment plan definitions
- Email sending configuration
- External service integrations
Like the frontend config, this file includes comprehensive instructions for each setting directly in the comments.
The Power of Centralized Configuration
These files provide a "single source of truth" for your application settings. When you need to make changes, you don't have to hunt through multiple files - just update the relevant config file and your changes will apply throughout the application.
Make sure to fill in the config files with the correct values before you proceed with the tutorials. All sensitive information like API keys should be stored in your environment variables (.env file in the backend), not in the config files.
Before you start building your startup, make sure to complete the extra config.