Bug #23365

Foreman shows an error if .env doesn't exist when starting in development mode

Added by Ewoud Kohl van Wijngaarden 3 months ago. Updated about 8 hours ago.

Assignee:Ewoud Kohl van Wijngaarden
Category:Development tools
Target version:1.19.0
Difficulty: Team Backlog:
Triaged:No Fixed in Releases:
Bugzilla link: Found in Releases:
Pull request:https://github.com/theforeman/foreman/pull/5479

Associated revisions

Revision 3505d737
Added by Ewoud Kohl van Wijngaarden 3 months ago

Fixes #23365 - Silence the ENOENT error for .env

If .env doesn't exist, it can be safely ignored. This updates the
library to the newest version to simplify error handling. The 2.0.0 also
had a silent option, but that didn't allow for only hiding the ENOENT


#1 Updated by The Foreman Bot 3 months ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/5479 added

#2 Updated by Michael Moll 3 months ago

  • Legacy Backlogs Release (now unused) set to 353

#3 Updated by Anonymous 3 months ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

#4 Updated by Ewoud Kohl van Wijngaarden about 8 hours ago

  • Triaged set to No
  • Category set to Development tools

Also available in: Atom PDF