Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
VILLASweb-backend-nodejs
VILLASweb-backend-nodejs
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
    • P
      Public
  • VILLASframework
  • VILLASweb-backend-nodejsVILLASweb-backend-nodejs
  • Issues
  • #31

Closed
Open
Created Jun 08, 2018 by Steffen Vogel@stvogel🎅🏼Owner

Enable nodemon explicitly via environment variable

In production, I currently use the "dotenv" environemnt.

With the latest changes, this will cause the docker image to start nodemon.

Can we use a special environement variable to enable the use of nodemon instead of activating it by default?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None