Docker Kit For Laravel - DEV and PROD Environments

Quickly get your Laravel project up and running with this Docker starter kit for Laravel. If you are looking for a bit more flexibility then this might be your solution.
Why another way to create and develop a Laravel application?
1. Enhanced Environment - I had a need to integrate with SQL Server, Active Directory, and other services. It was easier to have full control over the Dockerfile to facilitate these enhancements.
2. Architecture - I believe "application code" and "infrastructure code" belong in separate git repositories. This provides flexibility to easily create dev / prod environments.
Links:
- Github Repo: github.com/rcr...
- Introducing the Kit Facade: • Docker Kit For Laravel...
- Original Video Covering Kit Code: • Docker Kit For Laravel...
- Laravel Demo Repo Used In This Video: github.com/rcr...
- Laravel Github Repo: github.com/lar...
- Laravel Home Page: laravel.com/
- Docker Desktop Download: www.docker.com...
- Docker Home Page: www.docker.com/
#docker
#laravel
#technologysandbox

[@karlson2804]

At the end I am fond a person who can explain all these things with docker (prod, dev) and CI/CD
No one explains it in a real and good way or just some small videos for 0.1 level. Thank you very much.
I am creating my own environments for laravel and WordPress for now with infrastructure pattern and I am stuck in GitHub action one of my actions can see vendor files inside.
Also, you have your own solution "kit" and it look cool becouse I start do on makefile my commands and now I am thinking about migrating it to your "kit" idea.
If it possible can you make some videos about
- Git Hub action makes a button for a rollback of a deployed project on the last version or version that we want of project.
- Set up staging environment too.
Thx for your work.

[@decar4773]

Thank you for video

[@thetechnologysandbox]

You are welcome

[@abrahamolaobaju1781]

nice

[@thetechnologysandbox]

Thanks

[@DeGuzmanBonjourL]

Nice Video. How about running the project only in http

[@thetechnologysandbox]

In the dev environment, that would not be hard. I think most of the work is in the nginx/web_site.conf file. Just remove the top section that redirects HTTP requests to HTTPS. Then setup the bottom server section to listen on port 80 and remove the two lines setting ssl_certificate and ssl_certificate_key. Something like this (untested):
server {
listen 80;
server_name _ default;
root "/var/www/html/public";
index index.html index.htm index.php;
charset utf-8;
location / {
try_files $uri $uri/ /index.php?$query_string;
}
location = /favicon.ico { access_log off; log_not_found off; }
location = /robots.txt { access_log off; log_not_found off; }
access_log off;
error_log /var/log/nginx/web_site.app-error.log error;
sendfile off;
client_max_body_size 100m;
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass php:9000;
fastcgi_index index.php;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_intercept_errors off;
fastcgi_buffer_size 32k;
fastcgi_buffers 16 16k;
fastcgi_connect_timeout 300;
fastcgi_send_timeout 300;
fastcgi_read_timeout 300;
}
location ~ /\.ht {
deny all;
}
}