Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

pi-hole / FTL Public

Notifications You must be signed in to change notification settings
Fork 208
Star 1.4k

Code
Issues 38
Pull requests 10
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Print values of env vars if they are invalid#2273

Merged

DL6ER merged 4 commits intodevelopmentpi-hole/FTL:developmentfrom new/print_invalid_envpi-hole/FTL:new/print_invalid_envCopy head branch name to clipboard

Feb 24, 2025

+63-76

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Feb 24, 2025

Log incorrect env vars
DL6ER
committed
Explicitly log allowed items
DL6ER
committed
Ensure warnings/errors about invalid env vars are only printed once
DL6ER
committed
Avoid (null) as explanation
DL6ER
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.