Skip to content

Commit 494f54e

Browse files
Moved Docker/DevDocs build steps to the wiki
1 parent c9bcff9 commit 494f54e

File tree

1 file changed

+1
-30
lines changed

1 file changed

+1
-30
lines changed

README.md

+1-30
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ You can build the site locally in the following ways:
1818
- [Using Docker (docker-compose)](#docker-docker-compose) (Mac, Linux, Windows)
1919
- [Using a Vagrant virtual machine](https://github.com/magento-devdocs/vagrant-for-magento-devdocs) (Mac, Linux, Windows)
2020
- [Build DevDocs in Windows](https://github.com/magento/devdocs/wiki/Build-DevDocs-in-Windows) (Windows 7 & 10)
21-
- [Building older versions of the documentation](#building-old-versions)
21+
- [Building older versions of the documentation](https://github.com/magento/devdocs/wiki/Build-DevDocs-with-Docker)
2222

2323
## Build locally
2424

@@ -142,35 +142,6 @@ exclude:
142142
>rake preview:all
143143
>```
144144
145-
## Docker (docker-compose)
146-
147-
Docker provides a quick and easy way to build and preview the documentation. You do not need to install Ruby dependencies manually. This Docker solution launches Jekyll inside the container in `watch` mode.
148-
149-
Every change of a markdown file automatically triggers a rebuild of the documentation.
150-
151-
1. Install [Docker](https://www.docker.com/get-started). If you have Docker installed, launch the Docker application.
152-
153-
1. Clone the DevDocs repository.
154-
155-
1. Change to the `devdocs` directory.
156-
157-
1. Build and start the Docker environment.
158-
159-
```bash
160-
docker-compose up
161-
```
162-
163-
1. Use the server address URL provided by the system response.
164-
165-
For example:
166-
167-
```terminal
168-
jekyll_1 | Server address: http://127.0.0.1:4000/
169-
jekyll_1 | Server running... press ctrl-c to stop.
170-
```
171-
172-
1. Press `Ctrl+C` in the serve terminal to stop the server.
173-
174145
## Building old versions
175146
176147
The published website contains documentation for the latest Magento releases only. For cases, when you need to view the content as it was for an earlier release, we created [tags](https://github.com/magento/devdocs/tags) in this repository. Typically, they point at the commit when the release notes were finalized and published.

0 commit comments

Comments
 (0)