Download the PHP package mathieutu/php-project-launcher without Composer

🚀 PHP Project Launcher

Set a flexible Docker development environment in a second. This package assumes that you have docker installed, and a bash compatible operating system (actually not tested on Windows).

Set your project services

Just once per project, in its root sources folder.

If the services are already set up for your project you can directly jump to "Launch the services" chapter.

📦 Require the package

If you do not have php and composer on your computer you can directly use the composer docker container:

Tip: You should commit here! 😇

🐳 Initialize Docker files

Tip: You can personalize the project name, or leave empty to use the directory name. It will be used to automatically set your domain names: project-name.test and project-name.localhost by default. To use `.testthe developer need to edit itshostsor [add a dns server](https://medium.com/@narakuw/brew-install-dnsmasq-in-macos-sierra-26021c824be8), but.localhost` should work out of the box in unix OS

📝 Choose your flavour

Edit the docker-compose.yml, docker/*, and .env files to fit your needs.

A standard Laravel 5 / Symfony 4 application with a PostgreSQL database should work out of the box after updating your .env file.

See the configuration chapter for all the details.

Tip: You also should commit here 😇!

Launch the services

For each developer on its computer, every time s‧he need to launch the project.

🚀 Launch your project

Tip: A container of jwilder/nginx-proxy will be launched as nginx-proxy if not found and if ther is the standard 'web' container. It will allow you to use several domain names for your projects.

🎉 Make great things

Update your .env file

With the ppl db command you will see all the values that you need for your .env file:

See your project in the browser

Tip: If you do it quickly after up command, you could see a 502 page. Hold tight and refresh after few seconds, it's just the time your server needs to start!

Tip²: You can customize the domain to open with the $PPL_OPEN env variable in web service.

See your database content in a dedicated software

You can see the public port of your database with:

Use your favorite framework cli tool

You can directly access to cli tools with:

Tip: because we never save too much time, you can directly them with ppla and pplsf aliases.

Example:

And more...

You can see all you can do with:

Tip: By adding ./vendor/bin/ to your path, you will be able to directly type ppl instead of ./vendor/bin/ppl. And it will be useful for all the composer binaries, like phpunit! For that, you just have to add export PATH=./vendor/bin:$PATH to your .bashrc, or .zshrc file.

Make the configuration all yours

A standard Laravel/Symfony application with a PostgreSQL database should work out of the box, after having configured your .env file.

Uncomment the mysql example in docker-compose.yml if you prefer to use it.

For now, in the original flavour, you can see the documentation pages of:

• jwilder/nginx-proxy: The reverse proxy that allows you to use domain names on your projects.
• richarvey/nginx-php-fpm: The image used to serve the web service. Directly shipped with git, nginx, php, composer, xdebug, etc.
• postgres and mysql databases containers.
• docker and docker-compose tools.

Customize your URLs

In the docker-compose.yml file, you will be able to customise several env variables in your web service:

• $VIRTUAL_HOST which is the list of all the domain names that the proxy will redirect to this container.
• $PPL_OPEN which is the root url that the command ppl open will use.

TO BE CONTINUED...

Contribute to this project

Please feel free encouraged to make Issues and Pull Requests, for new features and bugs fixes as well as documentation.