Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • lava lava
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 45
    • Merge requests 45
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lava
  • lavalava
  • Merge requests
  • !1851

Merged
Created Oct 17, 2022 by eds-collabora@eds-collaboraContributor

Run django migrations as the correct target user

  • Overview 2
  • Commits 1
  • Changes 1

Running them as root leaves blank unwritable logs if they don't already exist, as is the case for the docker image. It seemed safer to run the commands as the correct user (to avoid future permission problems) than to simply bughunt the files that are currently created that have the wrong owners.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: wip/eds/at7958/django_migrations_upstream