-
Notifications
You must be signed in to change notification settings - Fork 19
Metabase in Local Demo environments
After performing initial application setup, use the command make setup-metabase
to run the local environment setup script. This will create an Admin and Basic user, remove the sample database, and add the Caseflow and VACOLS DB connection. To access Metabase, go to localhost:3002 and login with the credentials [email protected]
/caseflow1
or [email protected]
/password1
(these are set in the initialization script). At this point you are able to use Metabase in the same way that it is used in higher environments.
The basic setup does not include any dashboards, views, or other Metabase-specific objects. Those can be added via the UI or by using the Metabase API. To automate adding those objects when initializing Metabase, create a new shell script in the ./metabase
folder with the API commands and add the script execution to the Makefile command setup-metabase
.
The Metabase instance is automatically created and initialized as part of Demo deployments and can be accessed by going to /metabase
. The credentials for logging in are the same as for the local instance.
To automate adding extra objects to Metabase in Demo, new shell script executions need to be added to the startup script ./docker-bin/startup.sh after the initialization script runs. It isn't recommended to add them into the Demo initialization script. If they do not need to be executed on initialization, the scripts can be added to the ./metabase/
folder and run from the command line of the respective Demo EC2 instance.
- 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
- Tier 4
- Bat Team
- Technical Documentation
- Backend Code Patterns
- Backend Working Group
- FACOLS, VACOLS DB Schema
- Asyncable Models
- External Data: where and why
- Data Fetching Scripts
- Caseflow Data Model and Dictionary
- User Access Permissions
- Controller Schemas
- Constants
- 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