Migration to Laravel

[ghost]

This is happening right now. As we plan to do continuous integration on the Plugin catalogue of GLPi (glpi-plugin-directory running at plugins.glpi-project.org), the codebase is moving to Laravel right now. I'm writing this issue as a memo for myself, it will be updated.

For all those points, I'm looking for Laravel best-practices, but writing it down here first

• moving the configuration files to laravel's .env usage or use any practice encouraged by laravel in order to have custom configuration values for the app runtime
• [practice included] using Laravel Schemas instead of the previous structure.sql which eventually starts to be difficult to maintain. Write those Schemas definition in Laravel migrations.
• properly "include" the angular.js application in the new laravel project's directory structure, will need a beautiful solution for that, meaning that I don't see why PHP should be used to serve the index.html, looking for apache mod_rewrite usage/anything good for the purpose of keeping both angular and laravel codebases technically separated at the app runtime stack level
• ~~eventually move some Apache configuration parameters for the virtualhost in the .htaccess file if possible [for deployment easiness]~~ (planned for a future version, will simply edit the recommended virtualhost)

[becker]

Hello! Is there any way I can contribute with this? :D