Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 278
    • Issues 278
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #501
Closed
Open
Issue created Mar 04, 2021 by Andrei Pavel@andreiMaintainer

Comment STORK_DATABASE_PASSWORD in etc/server.env

I saw the # empty password is set to avoid prompting user for password to database, but I refuse to think that this is something that some simple engineering can't fix. This should only be here if there are users who want to get prompted for their passwords. These users will want to comment out the password. Even then maybe it should be a separate variable? Like PROMPT_USER_FOR_PASSWORD?

I think this change would make the interfacing with the user more pleasant.

Assignee
Assign to
Time tracking