feat: Create landing webpage with Firebase Remote Config–driven Play Store link#271
Draft
feat: Create landing webpage with Firebase Remote Config–driven Play Store link#271
Conversation
… integration Co-authored-by: ZanderCowboy <59666243+ZanderCowboy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add webpage with Google Play button to repository
feat: Create landing webpage with Firebase Remote Config–driven Play Store link
Feb 28, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Adds a static landing page at
apps/webpage/deployable tohttps://zandercowboy.github.io/multichoice/. The Google Play button URL is driven at runtime by Firebase Remote Config (play_store_urlkey), with a hard-coded fallback.New files
apps/webpage/index.html– Single-file landing page (HTML/CSS/ES module JS). Fetchesplay_store_urlfrom Firebase Remote Config via the JS SDK CDN; falls back to the static Play Store URL on failure.apps/webpage/assets/– App icon + screenshots sourced from the existingplay_store/directory.apps/webpage/README.md– Documents Remote Config key, deployment, and required GitHub Secrets.CI/CD
.github/workflows/pages_workflow.yml– Deploysapps/webpage/togh-pageson push tomain(path-filtered toapps/webpage/**). Injects Firebase web-app config from six GitHub Secrets viasedbefore publishing withpeaceiris/actions-gh-pages@v4.Flutter model update
FirebaseConfigKeys– AddedplayStoreUrl('play_store_url')so the Flutter app and the webpage share the same Remote Config key.Firebase Remote Config integration
Required one-time setup
FIREBASE_*GitHub Secrets (seeapps/webpage/README.md).gh-pagesbranch.play_store_urlstring parameter in Firebase Remote Config.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
orpetron.com/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.