-
Notifications
You must be signed in to change notification settings - Fork 4
Deployment Guide
Shaheer Ahmad edited this page Dec 17, 2025
·
1 revision
This project uses GitHub Actions to automate deployment to GitHub Pages.
The workflow is defined in .github/workflows/deploy.yml.
-
Trigger: Code is pushed to the
mainormasterbranch. -
Build:
- Ubuntu runner starts.
- Node.js is installed.
-
npm ciinstalls dependencies. -
Secrets Injection: The workflow reads secrets from the Repository Settings (
VITE_FIREBASE_...) and injects them into the build process. -
npm run buildcompiles the React code into thedist/folder.
-
Deploy: The content of
dist/is uploaded to GitHub Pages.
The application requires API keys to function. These are not committed to the repo.
To add secrets:
- Go to Repository Settings -> Secrets and variables -> Actions.
- Add the following secrets (values found in your local
.envor Firebase Console):VITE_FIREBASE_API_KEYVITE_FIREBASE_AUTH_DOMAINVITE_FIREBASE_PROJECT_IDVITE_FIREBASE_STORAGE_BUCKETVITE_FIREBASE_MESSAGING_SENDER_IDVITE_FIREBASE_APP_IDVITE_FIREBASE_MEASUREMENT_ID
Warning: If you add new environment variables for features, you MUST add them to GitHub Secrets, or the deployed site will break.
Home • GitHub Repository • Report an Issue • Contribute
Maintained with ❤️ by the 365Connect Community Team.
© 2025 365Connect Community. Licensed under MIT.