docker-apache-php-laravel
over-api
docker-apache-php-laravel | over-api | |
---|---|---|
1 | 2 | |
119 | 39 | |
3.4% | - | |
4.2 | 4.3 | |
2 months ago | about 1 year ago | |
PHP | PHP | |
MIT License | - |
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.
over-api
What are some alternatives?
crunz - A PHP-based job scheduler
ddd-hexagonal-architecture-laravel - Aplicación de prueba hecha en Laravel implementando conceptos de DDD y Arquitectura Hexagonal en base a principios SOLID
webgrind - Xdebug Profiling Web Frontend in PHP
assessment - Assessment for Laravel PHP developer.
laracaptcha - A Laravel package to seamlessly use hCapthca or reCaptcha v2 or v3 on your forms or RESTful APIs
Hateoas - A PHP library to support implementing representations for HATEOAS REST web services.
lamp - Docker LAMP stack
clean-architecture-manga - :cyclone: Clean Architecture with .NET6, C#10 and React+Redux. Use cases as central organizing structure, completely testable, decoupled from frameworks
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.
php-ddd-example - 🐘🎯 Hexagonal Architecture + DDD + CQRS in PHP using Symfony 6
devilbox - A modern Docker LAMP stack and MEAN stack for local development
laravel-jwt-api-starter - JWT API Auth: Laravel JSON Web Token API Authentication Template.