Add warning when use env_file and environments at the same time

[fzn0x]

Description

Can we add warning when we use env_file and environments at the same time? env_file will not work and environments will use default .env instead.

For most people, this is really waste time and I've seen so many Issues and Stackoverflow posts talking about this, I think adding a warning could solve the problem.

[fzn0x]

service will use env_file:

  skphonesmart:
    image: name:tag
    env_file:
      - .env.production.local
    ports:
      - 3001:3001
    restart: always
    depends_on:
      - postgres_server
      - adminer
    networks:
      - adminer-network

service will ignore env_file:

  skphonesmart:
    image: name:tag
    env_file:
      - .env.production.local
    environment:
      MY_PUBLIC_KEY: ${MY_PUBLIC_KEY}
    ports:
      - 3001:3001
    restart: always
    depends_on:
      - postgres_server
      - adminer
    networks:
      - adminer-network

[ndeloof]

There's no reason to warn user about this, both are valid and there's many relevant scenario where user will use both.

service will ignore env_file

it won't, but environment has precedence so same value in env_file will be ignored. Still other variables will be used.
See https://docs.docker.com/compose/environment-variables/set-environment-variables/#additional-information-2