-
Notifications
You must be signed in to change notification settings - Fork 19
Caseflow Demo
Craig Reese edited this page Jan 17, 2024
·
3 revisions
Caseflow Demo is a containerized version of Caseflow that is deployed into AWS EC2 instances. Caseflow demo uses this seed data to populate databases.
Seed data is created when db/seeds.rb is ran during deployment.
Individual seed data files are stored in db/seeds/
The demo environment at www.caseflowdemo.com is rebuilt daily from the latest commit of the master branch. All other demo environments are built and deployed only when requested, and are not refreshed daily. Any reset or reseed requires either a redeploy OR clicking the "Reseed the DB" button at the /test/users endpoint.
- 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