Bug #23365
Foreman shows an error if .env doesn't exist when starting in development mode
Status:
Closed
Priority:
Normal
Assignee:
Category:
Development tools
Target version:
Pull request:
Fixed in Releases:
Found in Releases:
Associated revisions
History
#1
Updated by The Foreman Bot about 4 years 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 Anonymous about 4 years ago
- Legacy Backlogs Release (now unused) set to 353
#3
Updated by Anonymous about 4 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 3505d7370ce00ae673c6c5b6f9323c8fcc17c35a.
#4
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Triaged set to No
- Category set to Development tools
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
error.