-
Notifications
You must be signed in to change notification settings - Fork 2
Deployment Guide
Dae Houlihan edited this page Nov 11, 2024
·
2 revisions
Warning
This section is under construction. Some of this information is out of date with the latest release of the template. Use with caution.
This guide covers deploying your experiment to Firebase Hosting.
The template includes a release script that automates deployment:
yarn release
- Prompts for version increment
- Creates git commit
- Injects version and git hash
- Builds the project
- Deploys to Firebase
If you prefer to deploy manually:
- Build the project:
yarn build
- Deploy to Firebase:
yarn deploy
- Create feature branch:
git checkout -b feature/my-feature
- Make changes and commit:
git add .
git commit -m "Description of changes"
- Push changes:
git push origin feature/my-feature
- Create pull request and merge
- Run
yarn lint
to check formatting - Run TypeScript compiler
- Remove any console.log statements
- Check for unused imports
- Update Firestore rules if needed
- Verify Authentication settings
- Check Firebase quotas and limits
- Test with production Firebase config
- Verify data storage
- Test Prolific integration
- Cross-browser testing
After deploying:
- Visit your Firebase-hosted URL
- Complete test run of experiment
- Verify data in Firestore
- Check browser console for errors
- Test Prolific integration
Monitor your deployment in Firebase Console:
- Hosting tab for deployment status
- Authentication tab for user activity
- Firestore tab for database operations
If enabled, check Google Analytics for:
- User engagement
- Error rates
- Performance metrics
-
Build Failures
- Check build output
- Verify dependencies
- Check TypeScript errors
-
Firebase Errors
- Verify Firebase CLI login
- Check project permissions
- Validate firebase.json
-
Data Storage Issues
- Check Firestore rules
- Verify authentication flow
- Check database permissions
If needed, rollback to previous version:
- Find previous deployment in Firebase Console
- Click "Rollback"
- Verify rollback success
- Set up Data Collection
- Return to Development Workflow