{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"No Compromises","title":"Where do credentials end and configuration begin in your env file?","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/d4a5f17d\"></iframe>","width":"100%","height":180,"duration":560,"description":"Have you ever fixed a failing test by adding a variable to phpunit.xml and moved on, not thinking twice about whether that was actually the right call?\nIn the latest episode of the No Compromises podcast, we discuss a real pull request disagreement about where environment variables belong and why it actually matters.\nWe draw an important distinction between credentials and workflow configuration in your env file, and why that difference should determine exactly what goes into phpunit.xml and what stays out.\nWe also get into why zeroing out API keys and hostnames in your test environment is not optional, and how a small oversight in one PR can quietly expose your tests to real third-party services.\nCome talk through decisions like these with developers who care in the No Compromises community.","thumbnail_url":"https://img.transistorcdn.com/Z2EtRaIjEnyUZU7bc944H_cjygcmUk4l_35aeIjws5o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzIzMDM3LzE2Mjc1/MjExMTAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}