douzhiba6873 2014-05-16 20:36
浏览 197
已采纳

来自php的dump-autoload命令

I am building a web application where the user dynamically can upload Controllers php files from the web browser. There is a problem in all of this.

Since every class should be compiled in order be used inside of laravel, the commmand composer dump-autoload must be executed. But I do not want to do this manually from the terminal. Inside of a "register class" I have called explicitly some commands that have not worked for me, for example:

  • Artisan::call('dump-autoload');
  • exec("/path/to/app/composer dump-autoload");
  • shell_exec('php artisan dump-autoload');
  • shell_exec('composer dump-autoload');

The new controllers are still not being found. So, I do not know what I am missing. Or if there is another way to "load" my classes dynamically.

Things to consider:

  1. Security implications: of course, but my question is widely open to dynamically recognize new classes in execution time
  2. I am completely sure about paths, I have tested every issue from a linux terminal and all worked fine (with absolute and relative path). For these reasons, I look for another reason instead of paths.
  3. Don't forget to actually 'require' or 'include' the class after you compile it Sure, the file is included and confirmed by the point 2.
  4. This looks suspicious:

    my off-the-cuff guess would be that the user running php doesn't have sufficient privileges to perform the operation or write to the required directories

    However, how could it be possible that php doesn't have enough privileges, could be it affects the composer dump-autoclass command?

  5. Apache/2.4.9 (Fedora) PHP/5.5.12

  • 写回答

2条回答

  • donglao9606 2014-05-16 21:13
    关注

    Well to work this out you can do this:

    exec("composer dump-autoload -d /path/to/laravel-project/");
    

    You have to explicitly tell composer where to look for composer.json.

    -d If specified use the given directory as working directory

    Without -d option, composer assumes your composer.json lives in path/to/laravel-project/public/. Because all requests are routed to front controller index.php and by that mean the current working directory is public/

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥15 安卓adb backup备份应用数据失败
  • ¥15 eclipse运行项目时遇到的问题
  • ¥15 关于#c##的问题:最近需要用CAT工具Trados进行一些开发
  • ¥15 南大pa1 小游戏没有界面,并且报了如下错误,尝试过换显卡驱动,但是好像不行
  • ¥15 没有证书,nginx怎么反向代理到只能接受https的公网网站
  • ¥50 成都蓉城足球俱乐部小程序抢票
  • ¥15 yolov7训练自己的数据集
  • ¥15 esp8266与51单片机连接问题(标签-单片机|关键词-串口)(相关搜索:51单片机|单片机|测试代码)
  • ¥15 电力市场出清matlab yalmip kkt 双层优化问题
  • ¥30 ros小车路径规划实现不了,如何解决?(操作系统-ubuntu)