<legend id='sBFZu'><style id='sBFZu'><dir id='sBFZu'><q id='sBFZu'></q></dir></style></legend>
  • <small id='sBFZu'></small><noframes id='sBFZu'>

    • <bdo id='sBFZu'></bdo><ul id='sBFZu'></ul>

      <i id='sBFZu'><tr id='sBFZu'><dt id='sBFZu'><q id='sBFZu'><span id='sBFZu'><b id='sBFZu'><form id='sBFZu'><ins id='sBFZu'></ins><ul id='sBFZu'></ul><sub id='sBFZu'></sub></form><legend id='sBFZu'></legend><bdo id='sBFZu'><pre id='sBFZu'><center id='sBFZu'></center></pre></bdo></b><th id='sBFZu'></th></span></q></dt></tr></i><div id='sBFZu'><tfoot id='sBFZu'></tfoot><dl id='sBFZu'><fieldset id='sBFZu'></fieldset></dl></div>

      <tfoot id='sBFZu'></tfoot>
      1. 如何在 Laravel whoops 输出中隐藏 .env 密码?

        How to hide .env passwords in Laravel whoops output?(如何在 Laravel whoops 输出中隐藏 .env 密码?)

      2. <small id='rL6Es'></small><noframes id='rL6Es'>

        <tfoot id='rL6Es'></tfoot>
          <i id='rL6Es'><tr id='rL6Es'><dt id='rL6Es'><q id='rL6Es'><span id='rL6Es'><b id='rL6Es'><form id='rL6Es'><ins id='rL6Es'></ins><ul id='rL6Es'></ul><sub id='rL6Es'></sub></form><legend id='rL6Es'></legend><bdo id='rL6Es'><pre id='rL6Es'><center id='rL6Es'></center></pre></bdo></b><th id='rL6Es'></th></span></q></dt></tr></i><div id='rL6Es'><tfoot id='rL6Es'></tfoot><dl id='rL6Es'><fieldset id='rL6Es'></fieldset></dl></div>

                  <bdo id='rL6Es'></bdo><ul id='rL6Es'></ul>
                  <legend id='rL6Es'><style id='rL6Es'><dir id='rL6Es'><q id='rL6Es'></q></dir></style></legend>
                    <tbody id='rL6Es'></tbody>
                  本文介绍了如何在 Laravel whoops 输出中隐藏 .env 密码?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                  问题描述

                  如何在 Laravel 的 whoops 输出中隐藏我的密码和其他敏感环境变量?

                  有时其他人正在查看我的开发工作.如果抛出异常,我不希望他们看到这些秘密,但我也不希望不得不不断地打开和关闭调试,或者为了快速预览而启动一个专用站点.

                  解决方案

                  截至

                  How can I hide my passwords and other sensitive environment variables on-screen in Laravel's whoops output?

                  Sometimes other people are looking at my development work. I don't want them to see these secrets if an exception is thrown, but I also don't want to have to keep toggling debug on and off, or spin up a dedicated site just for a quick preview.

                  解决方案

                  As of Laravel 5.5.13, you can censor variables by listing them under the key debug_blacklist in config/app.php. When an exception is thrown, whoops will mask these values with asterisks * for each character.

                  For example, given this config/app.php

                  return [
                  
                      // ...
                  
                      'debug_blacklist' => [
                          '_ENV' => [
                              'APP_KEY',
                              'DB_PASSWORD',
                              'REDIS_PASSWORD',
                              'MAIL_PASSWORD',
                              'PUSHER_APP_KEY',
                              'PUSHER_APP_SECRET',
                          ],
                          '_SERVER' => [
                              'APP_KEY',
                              'DB_PASSWORD',
                              'REDIS_PASSWORD',
                              'MAIL_PASSWORD',
                              'PUSHER_APP_KEY',
                              'PUSHER_APP_SECRET',
                          ],
                          '_POST' => [
                              'password',
                          ],
                      ],
                  ];
                  

                  Results in this output:

                  这篇关于如何在 Laravel whoops 输出中隐藏 .env 密码?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                  本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

                  相关文档推荐

                  When should use doctrine ORM and when zend-db-table?(什么时候应该使用学说 ORM,什么时候应该使用 zend-db-table?)
                  Doctrine - self-referencing entity - disable fetching of children(Doctrine - 自引用实体 - 禁用获取子项)
                  Doctrine 2, query inside entities(原则 2,实体内部查询)
                  Complex WHERE clauses using the PHP Doctrine ORM(使用 PHP Doctrine ORM 的复杂 WHERE 子句)
                  Doctrine - OneToMany relation, all result row doesn#39;t fetch in object(Doctrine - OneToMany 关系,所有结果行不获取对象)
                  Doctrine and unrefreshed relationships(教义和未更新的关系)

                  <small id='291Yc'></small><noframes id='291Yc'>

                  <tfoot id='291Yc'></tfoot>
                    <tbody id='291Yc'></tbody>

                  • <bdo id='291Yc'></bdo><ul id='291Yc'></ul>

                          • <i id='291Yc'><tr id='291Yc'><dt id='291Yc'><q id='291Yc'><span id='291Yc'><b id='291Yc'><form id='291Yc'><ins id='291Yc'></ins><ul id='291Yc'></ul><sub id='291Yc'></sub></form><legend id='291Yc'></legend><bdo id='291Yc'><pre id='291Yc'><center id='291Yc'></center></pre></bdo></b><th id='291Yc'></th></span></q></dt></tr></i><div id='291Yc'><tfoot id='291Yc'></tfoot><dl id='291Yc'><fieldset id='291Yc'></fieldset></dl></div>
                          • <legend id='291Yc'><style id='291Yc'><dir id='291Yc'><q id='291Yc'></q></dir></style></legend>