Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Multiple environment deployment strategy and infrastructure

Open
  • Is something wrong?
#259 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
firebase, gcp
Domain
ci-cd, cloud, devops, infrastructure

Research direction

Start by reviewing the deployment setup and the existing Firebase/Google Cloud project configuration, then compare it with the proposed local, dev, demo, and prod environments. Define the deployment entry points and release flow before implementing anything; done means staging deploys from main and production deploys by intentional choice.

Written by the indexing model from the issue text.

Description

big lift

Idea:

  • a deploy to a staging environment (need to create this) should happen automatically when a push to main occurs
  • a deploy to production environment should happen by intentional choice (usually after confirming things are all good in staging, but also perhaps after a hot-fix bug is remediated)

Pre-req: must build a new firebase/gcloud project environment.

@Justin-MacIntosh 's specific ideas based on his experience:

  • local: working on a local branch
  • dev: deployed from latest main, the environment QA testing happens on (similar to staging above)
  • demo: deployed ad-hoc and untouched, used for showing people outside the team the product
  • prod: deployed from latest GitHub release, the actual deployed product
Dominant language
Java
Stars
16
Forks
5
Avg merge
17h 24m
Merged PRs (30d)
23

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from CodeForPhilly/benefit-decision-toolkit

All issues in CodeForPhilly/benefit-decision-toolkit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.