Download the PHP package emakinafr/docker-proximis without Composer
On this page you can find all versions of the php package emakinafr/docker-proximis. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download emakinafr/docker-proximis
More information about emakinafr/docker-proximis
Files in emakinafr/docker-proximis
Package docker-proximis
Short Description Docker environment that meets Proximis requirements
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package docker-proximis
Docker for Proximis 
This repository allows the creation of a Docker environment that meets Proximis Omnichannel requirements.
Requirements
Installation
This process assumes that Docker Engine and Docker Compose are correctly installed. Otherwise, you should have a look to the installation documentation before proceeding further.
Add the package to development requirements
This Docker environment is available as a Composer package, and thus, can be retrieved like a PHP dependency. To add the environment as a development requirement, just type the following commands inside your project directory.
The second command will copy several files in your project so that you can customize the environment without modifying vendor files.
Nginx servers
A default Nginx configuration is installed at docker/local/nginx.conf. You are free to modify it as you want, to configure your own local domain(s) for instance.
By default, this configuration use the domain name to retrieve and use the correct configuration file for the CHANGE_CONFIG_NAME environment variable.
For example, if your domain app is proximis-demo-fr.localhost, the CHANGE_CONFIG_NAME value will be proximis-demo-fr.local.
Start the environment
That's all, you're done! :rocket:
Configuration of the Proximis project
This operation can be achieved through the PHP-FPM container.
Once in the container, the official documentation explains all the remaining steps.
Environment variables
Multiple environment variables are described inside the docker/local/.env file.
DOCKER_PHP_IMAGE
Defines which image will be used for the php container. There are three possible values: proximis_php (default), proximis_php_blackfire or proximis_php_xdebug.
BLACKFIRE_*
Defines the credentials needed to locally profile your application. You'll find more details in the official documentation.
MYSQL_*
Defines the credentials needed to locally setup MySQL server. You'll find more details in the official documentation.
Makefile
A Makefile is present in the repository to facilitate the usage of the Docker environment. In order to use it, you have to be in its directory. But as this file is quite useful and since we are often using the same commands all day, it's possible that you have also a Makefile in your project.
To avoid having to move to execute the right file, you can include the Makefile located in your environment directory in the Makefile located inside your project directory.
With this structure, you can execute the environment targets like env-start or env-php directly from your project without adding the environment in your repository.
