Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #299

Merged
merged 1 commit into from
May 23, 2022
Merged

Update README.md #299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,18 @@ git push --set-upstream origin hotfix/my-fix
* In GitHub, go to `Code -> tags -> releases -> Draft a new release`
* Publish a new release using tag sprint-#, be sure to Auto-generate release notes

## Technical Environment Plan

The fecfile-web-api is our system's backend while the fecfile-web-app is the single-page angular app. The fecfile-web-api is deployed as a cloud.gov application per environment (dev, stage, and prod). Each cloud.gov fecfile-web-api application has at least two instances running. Similarly, the fecfile-web-app is deployed as a cloud.gov application per environment (dev, stage, and prod). There are also at least two instances running per cloud.gov fecfile-web-app application.

The following events occur for fecfile-web-api and fecfile-web-app independently of each other:

* When a branch is merged into the develop branch, it is deployed to the dev environment on cloud.gov
* The Dev environment is used for the bulk of sprint integration and QA testing
* When a release is cut (creating a release tag in git), that release is deployed to the stage environment on cloud.gov.
* The Stage environment is used for final deployment preparation, integration testing, and final QA testing.
* When the release is merged into the main branch, it is deployed to the prod environment on cloud.gov
* The Production environment will be used by end users once the application launches.

## Additional developer notes
This section covers a few topics we think might help developers after setup.
Expand Down