-
Notifications
You must be signed in to change notification settings - Fork 19
Caseflow Makefile
Craig Reese edited this page Nov 13, 2023
·
1 revision
Caseflow can be run in several different ways with various make commands seen below. If you are using an Apple-silicon based Mac, you must use the commands with -m1
appended to them
-
make up
: Uses docker-compose to launch the required docker containers (Caseflow DB, VACOLS DB, localstack, redis) -
make up-m1
: Uses docker-compose to launch the required docker containers. On an Apple-silicon Mac, we run the VACOLS DB in a VM instead of a docker container, so this only launches the Caseflow DB, localstack, and redis containers. -
make run
: Executesmake up
and then uses the Foreman gem to run multiple services at once. The services can be seen in the file 'Procfile' in the Caseflow root directory. -
make run-m1
: Same asrun
, but executesmake up-m1
instead ofmake up
-
make run-backend
: Executesmake up
and then starts the Rails server with hot reloading -
make run-backend-m1
: Same asrun-backend
but executesmake up-m1
instead ofmake up
-
make run-frontend
: Starts the webpack dev server with hot reloading
These commands will run Caseflow servers without hot reloading enabled. This saves significant system resources, but can lead to running outdated code if you are not restarting the servers when changing code.
-
make run-backend-cold
: Executesmake up
and then starts the Rails server without hot reloading -
make run-backend-cold-m1
: Same asrun-backend-cold
but executesmake up-m1
instead ofmake up
-
make run-frontend-cold
: Starts the webpack server without hot reloading. This will precompile assets and serve pages from the/public
folder like the servers do in higher environments
-
make clean
: Removes logs, compiled webpack assets, and temporary files -
make realclean
: Executesclean
and then removes the node_modules folder -
make reset
: Executesreset-dbs
,seed-dbs
,enable-feature-flags
to reset and reseed the local environment -
make migrate
: Runs any pending Rails migrations for all Caseflow DBs
-
make one-test {args}
: Runs a single Rspec test file whose path is passed in as {args}. Specific tests can be specified with a colon and the test line number at the end of the file path -
make one-jest {args}
: Runs a single Jest test file whose path is passed in as {args} -
make one-jest-snapshot-update {args}
: Updates the snapshot for the file whose path is passed in as {args} -
make lint
: Runs thelint
rake command, the same used in our Github Actions builds
-
make c
: Launches the Rails console -
make db
: Opens a command line connection to the Caseflow DB
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
- Caseflow-Team
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks