Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Development Environment
The development environment is used for active feature development, bug fixes, and experimentation. It is expected to be unstable at times.
Access
| Resource | Access method | Who |
|---|---|---|
| GCP project (dev) | Entra ID SSO | All squad members |
| Cloud Run (dev) | gcloud CLI / console | All squad members |
| BigQuery (dev) | Console + bq CLI | All squad members |
| GitHub repositories | GitHub account + org membership | All squad members |
Access requests via ServiceNow — see IAM.
Key URLs and endpoints
| System | Dev URL / endpoint |
|---|---|
| (fill in) | (fill in) |
Rules for dev environment
- No real personal data — use synthetic or anonymized datasets only
- Feature branches deploy automatically to dev on push (if CI/CD is configured)
- Dev environment may be reset or wiped without notice — do not store important state there
- GCP costs in dev are monitored — avoid large unnecessary jobs
Local development setup
(Fill in with setup instructions for the most common local development workflow — e.g., Docker Compose, local env vars, GCP auth.)
# Authenticate with GCP (one-time setup)
gcloud auth login --update-adc
gcloud config set project [DEV_PROJECT_ID]
# Clone the repository
git clone https://github.com/patria/[repo-name].git
# Install dependencies
pip install -r requirements.txt # Python
# or
npm install # Node.js
# Copy environment template
cp .env.example .env
# Fill in dev values in .env