Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dashboard dashboard
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • AURA
  • dashboarddashboard
  • Issues
  • #10
Closed
Open
Created Feb 13, 2019 by Andrea Ida Malkah Klaura@jackieOwner

Manage and document environment variables

The way environment variables are handled by Vue have changed from Vue CLI 2 to Vue CLI 3. Now we have .env.production and .env.development, and they are loaded separately depending on the build mode. So you cannot only put those variables in .env.development that are different from those in .env.production, but you have to put all of them there. Only local modifications can then be overloaded with .env.development.local.

So what is to do:

  • make a generic .env.development
  • add local modifications (like the OIDC client ID) in .env.development.local
  • document all of this accordingly in README.md
Assignee
Assign to
Time tracking