project-templates.md

Project templates

In most cases, you do not need this. But for some projects it is quite useful.

You make a docker-compose.yml, but instead of loading an image, you build your own.

Build development

With build-development you can build smaller websites without having to create a new Docker project each time. Of course it is also sent, if you just want to test something for a short time.

Copy the folder build-development into your project folder and change this in your docker-compose.yml file:

services:
  web:
    build: build-development
    #image: cyb10101/php-dev:nginx-8.3 (or simply remove this line)
    environment:
      - VIRTUAL_HOST=~^(.+\.)?development\.localhost$$
      - WEB_DOCUMENT_ROOT=/app

Build with docker-compose and start the container:

docker-compose build && docker-compose up -d

Now you have little magic in the script. For example, you now have this folder structure:

# test1.development.localhost (only for nginx)
./test1/index.php

# test2.development.localhost/script.php
./test2/public/script.php

# development.localhost/test.php
./test.php

If you go to development.localhost you will get a small file list.

If you create a folder, a domain is automatically reachable: test1.development.localhost

If there is a subfolder "public" in the created folder, then the created domain will be accessible from there: test2.development.localhost

Note: The subfolder "public" detection can until now only nginx.

In this sense, happy coding!