Update ffa6653a-7d0e-41cc-a24e-074752b2ce1e.md#274
Conversation
| > | ||
| > Outcome: | ||
| > - You know how to quickly set up Spryker in a local environment. | ||
| In this guide we are going to launch an existing Spryker project in Docker containers on a local developemnt machine, |
There was a problem hiding this comment.
Clearly set epxectations.
There was a problem hiding this comment.
Focus only on Dev mode. Once concern per page, please.
Production specification is more complex than a snippet on this page :)
| - `--data` - fetch new demo data | ||
|
|
||
|
|
||
| ## Setting up a production-like environment |
There was a problem hiding this comment.
@sprymiker please split into a separate page, if we still don't have one.
There was a problem hiding this comment.
And there is nothing quick in the launching production env
| - `--assets` - build assets | ||
| - `--data` - get new demo data | ||
|
|
||
| Here you go! Now every Spryker Application of your project is running in a separate Docker container and |
There was a problem hiding this comment.
@sprymiker could you add, how can I confirm a successful installation,
what links to use? or maybe a healthcheck run?
| 1. Using a terminal navigate to your project root folder, there you can find src/ directory and composer.json file. | ||
|
|
||
| 2. Clone the latest version of the Docker SDK: | ||
| 2. Clone the latest version of the Docker SDK into the project root folder: |
There was a problem hiding this comment.
@sprymiker we need to place a correct docker.yaml to the root,
if I didn't have any Docker SDK before.
What template should I use?
How does the template correlate to the version of Docker?
There was a problem hiding this comment.
If you use demoshop boilerplate, you already have a bunch of deploy.yml files inside. If you did not use it for more than 2 years you will need an integration guide anyway.
Also one template does cover only one case, therefore we probably need multiple templates. So I assume we can just direct users to our demoshops boilerplates.
| > | ||
| > Outcome: | ||
| > - You know how to quickly set up Spryker in a local environment. | ||
| In this guide we are going to launch an existing Spryker project in Docker containers on a local developemnt machine, |
There was a problem hiding this comment.
developemnt -> development
| - `--data` - get new demo data | ||
|
|
||
| Here you go! Now every Spryker Application of your project is running in a separate Docker container and | ||
| you can continue writing amazing code using Docker environment! |
There was a problem hiding this comment.
I am not sure this is a place of stilted phrases here....
|
The primal source of this document is in docker/sdk repo. @andriitserkovnyi Please, manage these changes. Thanks |
2 participants
No description provided.