Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Conversation

hguthrie
Copy link
Contributor

@hguthrie hguthrie commented Aug 5, 2019

This PR updates the inaccuracies related to multi-sites outlined in the MAGECLOUD-3520:

  • update screenshot in Config guide
  • PHP code snippet formatting fixes
  • fix multi-site by differentiating between sites with shared domain and sites with unique domains

whatsnew
Updated the Set up multiple website or stores topic in the Cloud guide. Now, this topic differentiates between sites with a shared domain and sites with unique domains.

@hguthrie hguthrie added the Internal Dev Differentiates work between community and Magento staff label Aug 5, 2019
@hguthrie hguthrie self-assigned this Aug 5, 2019
@hguthrie hguthrie added 2.x Major Update Significant original updates to existing content labels Aug 9, 2019
@hguthrie hguthrie marked this pull request as ready for review August 9, 2019 22:46
Going to send this for another technical review.
From:

```php?start_inline=1
return strpos(str_replace('---', '.', $_SERVER['HTTP_HOST']), $host) === 0;
Copy link
Contributor

@NadiyaS NadiyaS Aug 13, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we need to change it in the file itself. Do not see reasons to keep example with ---.
Will create ticket.

@hguthrie
Copy link
Contributor Author

Yay! Major technical updates completed! @meker12 You are welcome to review again, if you like. Otherwise, this is ready to go!

@hguthrie
Copy link
Contributor Author

running tests


### Configure locations for shared domains {#locations}

Where the routes configuration defines how the URLs are processed, the `web` property in the `.magento.app.yaml` file defines how your application is exposed to the web. Web _locations_ allows more granularity for incoming requests. For example, if your domain is `store.com`, you can use `/first` (default site) and `/second` for requests to two different stores that share the same domain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Where the routes configuration defines how the URLs are processed, the `web` property in the `.magento.app.yaml` file defines how your application is exposed to the web. Web _locations_ allows more granularity for incoming requests. For example, if your domain is `store.com`, you can use `/first` (default site) and `/second` for requests to two different stores that share the same domain.
Where the routes configuration defines how the URLs are processed, the `web` property in the `.magento.app.yaml` file defines how your application is exposed to the web. Web _locations_ allow more granularity for incoming requests. For example, if your domain is `store.com`, you can use `/first` (default site) and `/second` for requests to two different stores that share the same domain.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw this after the test run, but yes, this is tricky. Locations is a web property category. The brain can get confused here. I'd like to find a way to get rid of Allow. I don't like using that word, in fact. Maybe provides.... ugh, staring too long...

@hguthrie hguthrie merged commit 1f18c1a into master Aug 15, 2019
@ghost
Copy link

ghost commented Aug 15, 2019

Hi @hguthrie, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@hguthrie hguthrie deleted the hg-mc3520-inaccuracies branch August 15, 2019 18:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
2.x Internal Dev Differentiates work between community and Magento staff Major Update Significant original updates to existing content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants