Assess if we can avoid putenv usage to avoid some thread safety issues #4879

New Issue

OVERLORD · 2026-02-05T09:23:27+03:00

OVERLORD commented

2026-02-05 09:23:27 +03:00

Originally created by @ssddanbrown on GitHub (Jul 17, 2024).

In thread error-prone environments (Apache on XAMPP windows by default for example) there can be issues with things like config loading, where config ends up blank.

This can be helped by config caching as a workaround, which we don't advise/document, but I feel it's better to avoid such thread problematic scenarios completely where possible, which it looks like it may be:

https://github.com/laravel/framework/pull/28908
https://github.com/laravel/framework/pull/28740

From what I can tell, this could effect libraries that use putenv/getenv, so might need to think-about/audit potential impacts there.

Originally created by @ssddanbrown on GitHub (Jul 17, 2024). In thread error-prone environments (Apache on XAMPP windows by default for example) there can be issues with things like config loading, where config ends up blank. This can be helped by config caching as a workaround, which we don't advise/document, but I feel it's better to avoid such thread problematic scenarios completely where possible, which it looks like it may be: https://github.com/laravel/framework/pull/28908 https://github.com/laravel/framework/pull/28740 From what I can tell, this could effect libraries that use putenv/getenv, so might need to think-about/audit potential impacts there.

OVERLORD added the 🔧 Maintenance 🏭 Back-End 🔍 Pending Validation labels 2026-02-05 09:23:27 +03:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#4879