Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multistore docs fixes #1853

Merged
merged 3 commits into from
May 16, 2023
Merged

Multistore docs fixes #1853

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
998b434
Multistore docs fixes
lenadoc May 16, 2023
0928f7c
fixing the links
lenadoc May 16, 2023
701c4db
fixing the docs
lenadoc May 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 19 additions & 19 deletions ...loud-commerce-os/multi-store-setups/checklist-for-a-new-store-implementation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,26 +4,26 @@ description: Learn how to implement a new store in a multistore environment
template: concept-topic-template
related:
- title: Multistore setup options
link: docs\cloud\dev\spryker-cloud-commerce-os\multi-store-setups\multistore-setup-options.html
link: docs/cloud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.html
---

This document outlines the high-level tasks and responsibilities of Spryker and Customer when setting up a new store depending on the chosen setup for the multistore environment. For description of setups referred to in this document, see [Multistore setup options](/docs/cloud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.html).
This document outlines the high-level tasks and responsibilities of Spryker and Customer when setting up a new store depending on the chosen setup for the multistore environment. For a description of setups referred to in this document, see [Multistore setup options](/docs/cloud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.html).

For detailed steps about the new store implementation, see [HowTo: Set up multiple stores](/docs/scos/dev/tutorials-and-howtos/howtos/howto-set-up-multiple-stores.html).

## Setup 1

**Spryker**
1. Adjust deployment structure / CI: define the environment variables in Spryker CI based on the deployment files.
2. Make adjustments for stage and production: adjust configuration in the `config.php` file.
2. Make adjustments for stage and production: adjust the configuration in the `config.php` file.
3. Change DNS (Spryker owns DNS in AWS).

**SI / Customer**
1. Set up a local dev environment and adjust configuration in `config.php` including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
1. Set up a local dev environment and adjust configuration in `config.php`, including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
2. Implement and apply [code buckets](/docs/scos/dev/architecture/code-buckets.html) for different themes.
3. Adjust the importer and define product, content, data, payment including OMS or stock store relations via importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
3. Adjust the importer and define product, content, data, payment, including OMS, or stock store relations via the importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
4. Change DNS (merchant owns DNS).
5. Check third party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
5. Check third-party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
6. Migration of the existing data into the shared instance. Spryker can support you in this on request.
7. Full UAT, end2end tests.
8. Check the provided launch list from Spryker, if you start a new project.
Expand All @@ -45,17 +45,17 @@ For this setup, send a support request to Spryker and do the following:

**Spryker**
1. Adjust deployment structure / CI: define the environment variables in Spryker CI based on the deployment files.
2. Make adjustments for staging and production: adjust configuration in the `config.php` file.
2. Make adjustments for staging and production: adjust the configuration in the `config.php` file.
3. Add new endpoints for stores and regions (Spryker owns DNS in AWS).
4. Update RDS configuration to activate multi-database feature
4. Update the RDS configuration to activate multi-database feature

**SI / Customer**

1. Set up a local dev environment and adjust configuration in `config.php` including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
1. Set up a local dev environment and adjust the configuration in `config.php`, including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
2. Implement and apply [code buckets](/docs/scos/dev/architecture/code-buckets.html) for different themes.
3. Adjust the importer and define product, content, data, payment including OMS or stock store relations via importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
3. Adjust the importer and define product, content, data, payment, including OMS or stock store relations via the importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
4. Change DNS (merchant owns DNS).
5. Check third party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
5. Check third-party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
6. Migrate the existing data into the shared instance. Spryker can support you in this on request.
7. Conduct the full UAT, end2end tests.
8. If you start a new project, check the provided launch list from Spryker.
Expand Down Expand Up @@ -83,11 +83,11 @@ Provision of a new fully isolated environment per store.

**SI / Customer**

1. Set up a local dev environment and adjust configuration in `config.php` including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
1. Set up a local dev environment and adjust the configuration in `config.php`, including hosts in data YML files, for example, in `/deploy.spryker-b2c-production.yml`.
2. Implement and apply [code buckets](/docs/scos/dev/architecture/code-buckets.html) for different themes.
3. Adjust the importer and define product, content, data, payment including OMS or stock store relations via importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
3. Adjust the importer and define product, content, data, payment, including OMS or stock store relations via the importer. See [example for the B2C demo shop](https://github.com/spryker-shop/b2c-demo-shop/tree/master/data/import/common/common).
4. Change DNS (merchant owns DNS).
5. Check third party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
5. Check third-party integrations (ERP, CRM, CMS, PIM, Payment, Logistics, Search).
6. Migrate the existing data into the shared instance. Spryker can support you in this on request.
7. Conduct the full UAT, end2end tests.
8. Check the provided launch list from Spryker, if you start a new project.
Expand All @@ -105,19 +105,19 @@ The touchpoints listed here may vary depending on the project. If view of that,
| config/Shared/stores.php | Contains store-specific application configuration. | Add new stores, configure formats, locales, available countries, currencies. |
| config/install/*.yml | YAML files, describing application building steps for different environments used by docker/sdk. | Some of the commands have a context of the store for which they are executed. Make sure the right store is used. |
| data/import/*.csv | Demo data, a lot of store-specific content. | Make sure to add or remove data for respective stores in all the files. |
| deploy.{environment-name}.yml | Main docker/sdk configuration file, which is used to build all application images. | Regions, stores, groups, and databases, domains. You can create a dedicated environment file for each store. |
| deploy.{environment-name}.yml | Main docker/sdk configuration file, which is used to build all application images. | Regions, stores, groups, databases, domains. You can create a dedicated environment file for each store. |

### Data
1. Generate product data files to add new localized attributes and entries.
2. Create the folder `data/import/common/{NewStore}` and fill it with all the files that reflect the new store.
3. Modify install recipes to add the new folder you created or copied at the previous steps
3. Modify install recipes to add the new folder you created or copied in the previous steps

### Store domains and certificates
Request the Spryker Cloud team to create domains and certificates.

{% info_block infoBox "Info" %}

Certificates are created for all domains
Certificates are created for all domains.

{% endinfo_block %}

Expand All @@ -129,5 +129,5 @@ Certificates are created for all domains
- Update the list of the [related CMS stores](https://docs.spryker.com/docs/scos/user/features/202009.0/cms-feature-overview/cms-pages-overview.html#cms-page-store-relation)
- Update store-specific Terms & Conditions

### Addons
Configure the project-specific addons. The addons vary and depend on the project implementation. For example, create country admin roles, configure the outgoing email address, etc.
### Add-ons
Configure the project-specific add-ons. The add-ons vary and depend on the project implementation. For example, create country admin roles, configure the outgoing email address, etc.
Loading