Introduction
In this section, you'll find information specific to how Backend Engineering works on VA.gov.
Communication channels
-
Slack channels: #vfs-platform-support
-
Github labels: platform-cop-backend, backend
Points of contact
The Backend points of contact are:
-
Eric Boehs
-
@Eric Boehs on Slack, @ericboehs on Github
-
-
Lindsey Hattamer on Slack, @LindseySaari on Github
-
@User
-
Table of contents
The following list is a set of resources compiled by the people in your practice area to help you do your work and answer questions you might have. Some of the links may take you to other sites and resources outside this repo. If you need a hand with anything, don't hesitate to ping the Slack channels and/or people listed above.
-
Getting started
-
Environment setup
-
Docker setup
-
Docker Desktop (Engine + Compose)
-
Linux (Ubuntu)
-
-
Common tasks
-
Clone & Build
-
Run the app
-
Logging in
-
Testing & Tools
-
Running test suite
-
(Jenkins, Sentry)
-
Datadog
-
-
API Reference
-
Database Migrations
-
Mocking data
-
-
Code organization
-
We enforce a consistent code style with Rubocop code linting
-
- used to manage unreleased features
-
Standards and conventions
-
for reference: 18F API standards (some good advice here)
-
-
Development workflow
-
How to File Bugs, Tasks, and Questions
-
Code review
-
Deploy and Release Process
-
Deploy Details (K8s vs BRD)
-
Triage Processes
-
External Service Partners (aka APIs)
-
Breakers gem - Handles downtime for external services by marking them as “down” while continuously checking for valid response statuses
-
Facilities Locator - A single consolidated place where veterans and beneficiaries can easily find and understand high-level information about facilities offering priority VA benefits and services
-
HCA - Health Care Applications
-
GIBFT - GI Bill Feedback Tool
-
Datasources
Help and feedback
-
Get help from the Platform Support Team in Slack.
-
Submit a feature idea to the Platform.