Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • steering steering
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • AURAAURA
  • steeringsteering
  • Merge requests
  • !24

Allow extended database configuration through DATABASE_URL env variable

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Konrad Mohrfeldt requested to merge feature/extended-database-env-configuration into main Mar 23, 2023
  • Overview 1
  • Commits 3
  • Pipelines 3
  • Changes 4

This adds dj_database_url package to our dependencies and allows users to configure the database through the DATABASE_URL environment variable.

I’ve noticed that database configuration was misleading (most database env variables are prefixed with POSTGRES_) and not very practical while working on the CI setup in the dashboard with the goal of running integration tests against steering.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/extended-database-env-configuration