Skip to content

refactor(firebase): Added init script and made Firebase optional for devs - #123

Merged
iswheeler merged 3 commits into
navigation-hubfrom
init-script-without-firebase
Oct 20, 2026
Merged

iswheeler merged 3 commits into
navigation-hubfrom
init-script-without-firebase

Conversation

@iswheeler

@iswheeler iswheeler commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Description

We have a few new folks joining the frontend team and setting up the app with a Firebase token is a pain. Since most frontend devs don't need Firebase support, I added an init.sh script to: A) make setup easier, and B) let devs run the app without Firebase

Type of Change

  • New feature (feat)
  • Bug fix (fix)
  • Refactor / code improvement
  • Dependency / build update
  • Documentation
  • Other (explain)

Changed Files

(Please list all files you changed, each with a description of what you changed and why.)
Tip: see a list of everything you changed on the "Files changed" tab

Example:

  • notification_service.dart
    • Added a flag to disable Firebase if the USE_FIREBASE environment variable is not set. (The flag is automatically set to true when creating a release build)
  • setup.sh
    • Added setup script to check the Flutter install, ask user for Google Maps API key, copy the API key to the proper locations (removing any old keys), install Flutter dependencies, and create dummy Firebase config files if they don't already exist.
    • Note: The dummy firebase_options.dart generated by setup.sh includes a warning, so if you try to build a release app it'll yell at you that there's no Firebase config. (This is to prevent us accidentally publishing a Maizebus version that has Firebase disabled.)'
  • README.md
    • Added a nice header image and instructions to get an API key and use the setup script

Related Issues

Does your code rely on another PR

Testing Done

Flutter:

  • Tested on:
    • iOS Simulator
    • Android Emulator
    • Physical device

Screenshots / Demo (if UI or notification change)

Checklist

  • Commit messages follow Conventional Commits
  • PR title follows [type](scope): short description
  • PR target branch is not main and is our current working update branch (e.g. maizebus2.1)
  • No print() / debugPrint() / console.log() left in production code
  • Secrets / keys not committed

@i-kumar i-kumar left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also update the readme to include instructions for using the setup script?

@iswheeler

Copy link
Copy Markdown
Contributor Author

Can we also update the readme to include instructions for using the setup script?

Great idea. I'll make sure to include that too

@iswheeler
iswheeler merged commit f2c2c7f into navigation-hub Oct 20, 2026
12 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants