MCLOUD-5511: Add Multi-website Support into Cloud Docker

[mohanelamurugan]

Description

Added multi website support in cloud docker(Appended magneto-vars.php to php.ini) .

https://jira.corp.magento.com/browse/MCLOUD-5511:

1. Start the magento cloud docker, set to developer deploy mode following this tutorial: https://devdocs.magento.com/guides/v2.3/cloud/docker/docker-config.html
2. Set up a new website, store, store view and use this tutorial to set up a new website: https://devdocs.magento.com/guides/v2.3/cloud/project/project-multi-sites.html
3. Assuming we plan to have http://second.magento2.docker/ for the new website that we are adding, Add second.magento2.docker to hosts file.
4. Visit http://second.magento2.docker/

Fixed Issues (if relevant)

MCD-104

Manual testing scenarios

1. Add both websites base url to hosts
2. Visit each website's URL from browser
3. Secondary website URL should redirect to the secondary website instead of redirecting to the base website's URL.

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages

[shiftedreality]

Please add new line

[mohanelamurugan]

Added. Pls review again

[andriyShevtsov]

Created internal task MAGECLOUD-5584

[shiftedreality]

To run in Production mode:

1. Create file docker-compose.override.yaml:

version: '2.1'
services:
  web:
    volumes:
      - './magento-vars.php:/app/magento-vars.php:ro'

[andriyShevtsov]

@shiftedreality Please take a look. With production mode and docker-compose.override.yaml I have error
Fatal error: Cannot redeclare isHttpHost() (previously declared in /app/magento-vars.php:20) in /app/magento-vars.php on line 20

[shiftedreality]

@andriyShevtsov it looks like the trick with docker-compose.override.yml is not needed. This issue somehow relates to Docker itself and can be avoided by simple adjustment:

if (!function_exists('isHttpHost')) {
    function isHttpHost($host)
    {
        if (!isset($_SERVER['HTTP_HOST'])) {
            return false;
        }
        return strpos(str_replace('---', '.', $_SERVER['HTTP_HOST']), $host) === 0;
    }
}

[shiftedreality]

I just realized it will break the default behavior.

@mohanelamurugan could you please check this PR in Production mode if you have the same problem?

[mohanelamurugan]

Sure @shiftedreality , Let me check this

[mohanelamurugan]

@shiftedreality

I didn't use the docker-compose.override.yml
I tested it in production mode. I was able to run deploys, post deploys, cache clean, index:reindex as well.
Also multi site redirections are also working fine.
The first one runs in the URL magento2.docker whereas the other one is second.magento2.docker.
Also from the attached image below, You can find that the setup is running in production mode.
PFA

[andriyShevtsov]

Thank you. Most likely that issue was not related to your PR. QA approved.