SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

✨ Firebase Multi-Tenant Setup Guide

Open
#1,503 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
37
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Hi DevOps,

Pain

Each tenant needs their own Firebase project for push notifications. Setting this up is complex and needs clear documentation.

Suggested Solution

Create comprehensive step-by-step guide for setting up Firebase projects per tenant, including Android and iOS app setup, configuration files, and secret management.

Implementation:

  • Document Firebase project creation
  • Document Android and iOS app setup
  • Create configuration templates
  • Document secret management
Tasks
  • Document Firebase project setup process
  • Document Android app registration steps
  • Document iOS app registration steps
  • Create template for google-services.json
  • Create template for GoogleService-Info.plist
  • Document how to store secrets in CI/CD
  • Add validation for Firebase configs
  • Create troubleshooting section
Acceptance Criteria
More Information

Files to Create:

  • NEW: _docs/Firebase-Setup-Guide.md
  • NEW: templates/google-services.template.json
  • NEW: templates/GoogleService-Info.template.plist

Epic: #1483

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read _docs/Definition-of-Done.md first, then organize the work around the listed new files: _docs/Firebase-Setup-Guide.md and the two templates under templates/. Done means the guide covers Firebase project, Android and iOS setup, configuration templates, and CI/CD secret management, with the requested validation and troubleshooting tasks addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, ios
Domain
ci-cd, documentation, mobile
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.