You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
max-zaremba-tcg edited this page Nov 18, 2025
·
1 revision
Technical Environment Plan
The fecfile-web-api is FECfile+'s backend while the fecfile-web-app is the single-page angular app frontend. The fecfile-web-api is deployed as a cloud.gov application in each environment (DEV, STAGE, TEST, 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, TEST, 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 and TEST environments on cloud.gov
The TEST environment will be used by alpha users for UAT.
The PROD environment will be used by end users once the application launches.