Docker standardizes development testing and production environments

For most businesses, building PaaS is neither that energy nor the necessity, and using Docker as a personal sandbox is a little less useful.

Docker can be used to standardize development, testing, and production environments.

Docker is small in resources, and deploying 100 containers on an E5 128 G memory server is more than enough to draw a container individually or deploy samba directly on the host physical host, mapping each user's home directory to Windows machines in the development center and test department using samba's home sharing scheme.

For a project group, a standard container environment is built by the architect for use by the project team and test department, and each development engineer can have his own separate container that maps the user's home directory to the container through docker run -v W hen you need to submit a test, you just need to hand over the code to the test department and assign -v load the test department's home directory to start. In this way, the development and testing within the company is basically unified, there will be no development department submitted code, test department can not deploy the problem.

Once the testing department has released the report that the test passed, the architect once again detects the container environment and can deploy the code and containers to the production environment directly to the deployment engineer. The scale of deployment scale in this way is also excellent.