docs: restructures installation and moves legacy setups#2111
docs: restructures installation and moves legacy setups#2111somethings (lasomethingsomething) wants to merge 41 commits intomainfrom
Conversation
|
|
Su (sushmangupta)
left a comment
There was a problem hiding this comment.
I have suggested changes to some sections so far. Let me know if we have to proceed this way, or if I can make the changes directly to your branch ?
|
|
||
| --- | ||
|
|
||
| # Overview of Shopware 6 Installation |
There was a problem hiding this comment.
Push this file content into index.md file.
| docker compose ps | ||
| ``` | ||
|
|
||
| “Healthy” means the service passed its internal health check and is ready to use. |
There was a problem hiding this comment.
If the service status doesn't show "Healthy", then how do we proceed?
There was a problem hiding this comment.
Here I think we can refer them to docker docs, like https://docs.docker.com/reference/dockerfile#healthcheck or https://docs.docker.com/reference/cli/docker/inspect/ (cc Shyim (@shyim) for your thoughts)
Su (sushmangupta)
left a comment
There was a problem hiding this comment.
I have suggested changes to some sections so far. Let me know if we have to proceed this way, or if I can make the changes directly to your branch ?
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
Co-authored-by: Su <112690947+sushmangupta@users.noreply.github.com>
This PR reflects a product decision to highlight Docker as our primary installation method. Documentation about other methods remains, and is now stored in a separate folder.
Edits divide software requirements from hardware requirements.
The main page includes a line that takes users directly to the install section.