Prerequisites
Before you begin, ensure you have the following installed and configured:Node.js 18+
Download from nodejs.org
Package Manager
npm, yarn, or pnpm
Supabase Account
Sign up at supabase.com
Web3 Wallet
MetaMask or compatible wallet
You’ll also need access to Base Sepolia testnet for contract deployments and testing.
Installation
Install Dependencies
This will install all frontend dependencies, including Next.js 15.5.9, React 19, Web3 libraries (Wagmi 2.17, Viem 2.38, RainbowKit 2.2), and AI service SDKs.
Set Up Environment Variables
Create a You’ll configure the specific variables in the next section.
.env.local file in the root directory by copying from the example:Configure Supabase
Create a Supabase Project
- Go to supabase.com/dashboard
- Create a new project
- Navigate to Settings > API to get your credentials
Run Database Migrations
eStory includes SQL migrations for all required tables:001_create_weekly_reflections.sql- Weekly AI reflection summaries002_enable_rls_policies.sql- Row Level Security policies003_add_oauth_fields.sql- OAuth integration fields004_create_habits_tables.sql- Habit tracking tables005_create_waitlist_table.sql- Waitlist management006_create_verified_metrics_tables.sql- CRE verified metrics
Create Storage Bucket
Create a storage bucket namedstory-audio for audio file storage:- Go to Storage in your Supabase dashboard
- Create a new bucket named
story-audio - Set appropriate access policies (authenticated users can upload)
Verify Installation
Run the development server to verify everything is set up correctly:Project Structure
After installation, your project structure will look like this:Next Steps
Configure Environment
Set up all required API keys and environment variables
Local Development
Learn development workflows and available commands
Common Issues
Node version errors
Node version errors
eStory requires Node.js 18 or higher. Check your version:If it’s below v18, update Node.js before proceeding.
Installation fails with peer dependency warnings
Installation fails with peer dependency warnings
These are typically safe to ignore. If installation fails completely, try:
Port 3000 already in use
Port 3000 already in use
You can specify a different port: