Download the PHP package iamluc/docker-hostmanager without Composer
On this page you can find all versions of the php package iamluc/docker-hostmanager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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-hostmanager
docker-hostmanager
ABOUT
Update automatically your /etc/hosts to access running containers.
Inspired by vagrant-hostmanager.
Project homepage: https://github.com/iamluc/docker-hostmanager
USAGE
Linux
The easiest way is to use the docker image
Note: the --restart=always option will make the container start automatically with your computer (recommended).
Mac OS
Download the PHAR executable here : https://github.com/iamluc/docker-hostmanager/releases
And then run it:
Note: We run the command as root as we need the permission to write file /etc/hosts.
If you don't want to run the command as root, grant the correct permission to you user.
Before running the command, don't forget to export your docker environment variables. i.e.
Also, you should add a route to access containers inside your VM.
Windows
If the host, dont use Docker ToolBox or not a Windows 10 PRO, then needs to mount the /c/Windows folder onto VirtualBox.
After run the container we need to add a route to access container subnets.
CONFIGURATION
With networks
When a container belongs to at least one network (typically when using a docker-compose.yml file in version >= 2), the name defined to access the container is CONTAINER_NAME.CONTAINER_NETWORK. It works also with the alias defined for the network.
As a container can belongs to several networks at the same time, and thanks to alias, you can define how you want to access your container.
Example 1 (default network):
The container web will be accessible with web.myapp_default (if the docker-compose project name is myapp)
Example 2 (custom network name and alias):
The web container will be accessible with web.myapp.
The mysql container will be accessible with mysql.myapp or bdd.myapp
Without networks
When a container has no defined network (only the default "bridge" one), it is accessible by its container name, concatened with the defined TLD (.docker by default).
It is the case when you run a single container with the docker command or when you use a docker-compose.yml file in version 1.
The DOMAIN_NAME environment variable lets you define additional hosts for your container.
e.g.:
Tests
To run test, execute the following command : vendor/bin/phpunit
