docker-apache-php-laravel
webgrind
docker-apache-php-laravel | webgrind | |
---|---|---|
1 | 2 | |
119 | 3,245 | |
3.4% | - | |
4.2 | 3.4 | |
2 months ago | 4 months ago | |
PHP | PHP | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-apache-php-laravel
-
Deploying PHP App to Apache
The main concept you need to know about is the apache document root. This defines the start/root of "web space". Your document root is going to be the /public directory of your project. You should not be versioning or copying files in /vendor. That directory should be created by running composer install on the server from a shell in your project directory. composer will create the vendor directory, and pull all the same files you've been working with. This assumes that you have been versioning the composer.lock file. In production you only ever run composer install. Since laravel implements the front controller pattern, you need some sort of configuration to handle rewriting requests so they utilize the front controller (/public/index.php). Here is a typical mod_rewrite configuration you can put in a .htaccess file in the /public directory. For quite a while, many sysadmins paired nginx/php-fpm, whereas with apache you have the option to use mod_php. However, it is now quite possible to use apache and php-fpm. Think of php-fpm as the application server for php. Although this article talks about setting this up for the symfony framework, the principle would be exactly the same for a laravel app. I would recommend using apache with php-fpm as this is a more efficient use of resources and memory than setting apache up with mod_php. The main thing to ignore in that article is the use of the symfony package, which just provides a .htaccess that works with symfony. As symfony and Laravel are both front controller frameworks it might actually work with laravel, but I can't say for sure.
webgrind
-
What are modern profiling tools?
Webgrind
-
Weekly help thread
Is there a way to read the xDebug 3 Profiler results on Windows? I've tried: 1) QCacheGrind?(https://sourceforge.net/projects/qcachegrindwin/) 2) WinCacheGrind (https://github.com/ceefour/wincachegrind/releases/tag/1.1) 3) Webgrind (https://github.com/jokkedk/webgrind) But none of them was able to read the .gz files
What are some alternatives?
crunz - A PHP-based job scheduler
dd-trace-php - Datadog PHP Clients
laracaptcha - A Laravel package to seamlessly use hCapthca or reCaptcha v2 or v3 on your forms or RESTful APIs
wincachegrind - [NO LONGER MAINTAINED] WinCacheGrind is a viewer for cachegrind.out files generated by xdebug 2. WinCacheGrind is functionally similar to KCacheGrind, only it is much simpler and runs on Windows.
lamp - Docker LAMP stack
kcachegrind - GUI to profilers such as Valgrind
Spikster - Install and manage your server like a pro! With Spikster you don’t need to be a Sys Admin to deploy and manage websites and PHP applications powered by cloud VPS.
Dephpugger - Php Debugger to run in terminal to debug your code easily.
devilbox - A modern Docker LAMP stack and MEAN stack for local development
forp-PHP-profiler - A PHP profiler written in C. forp is a lightweight PHP extension which provides the full call stack of your script, with CPU and memory usage, in a plain PHP Array or JSON output.
over-api - ¡BACKEND OVER APP! API REST IMPLEMENTANDO CONCEPTOS DE ARQUITECTURA HEXAGONAL, DDD, TDD Y SOLID. HECHO EN LARAVEL & PHP
Quo-php - This specific package is the Quo companion package for PHP. Quo for PHP is framework-agnostic and can be run on any PHP ^7.1 project using composer. Quo-php has zero-dependencies.