by Devin Yang
(This article was automatically translated.)

Published - 8 years ago ( Updated - 8 years ago )

This video introduces how to use the docker-compose command to specify multiple YAML structure language configuration files to create container execution, and introduces how we simplify docker-compose by using .env in the D-Laravel environment Start command.

D-Laravel users must watch the video, docker users, in this video, you can learn how to specify multiple yaml files at the same time by command.

Please update to the latest D-Laravel v1.2.13 to ensure that all functions can be executed normally,
Query the available version of D-Laravel./console version
Reminder:
If your D-Laravel project is already in operation, it is recommended to clone another version to try it out first.
In order to avoid site efect affecting the original normal operation of the project.
E.g:
git clone https://github.com/DevinY/dlaravel.git dlaravel-test

For a detailed introduction to D-Laravel, please refer to my GitHub URL:
https://github.com/DevinY/dlaravel
 

Tags: docker laravel

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


docker, d-laravel, docker-compose, laravel

docker-compose loads multiple configuration files

We will use docker --network to establish multiple container interconnections, but if there are four containers, Is it necessary to issue docker run instructions for different containers four times, kill me, This article introduces the establishment of multiple containers at one time through the yaml file definition of docker-compose. Learn how to load multiple configuration files with the dokcer-compose -f parameter.  

dlaravel

D-Laravel released v1.1.5

In response to the launch of Laravel 5.5, PHP also released PHP 7.0.23 and PHP 7.1.9. The fpm version used by D-Laravel is also updated...just adjust the version defined by your docker-compose You can use the latest php...

laravel, livewire

livewire important notes

Before starting your Livewire journey, here are three basic considerations about public properties: 1. The property name must not conflict with a property name reserved for Livewire (such as $rules or $message) 2. Store in Data in public properties is visible to front-end JavaScript. Therefore, you should not store sensitive data in it. 3. Properties can only be JavaScript-friendly data types (string, integer, array, boolean), or one of the following PHP types: Stringable, Collection, DateTime, Model, EloquentCollection.