You can deploy devdocs.magento.com site locally using this Vagrant project. Vagrant enables you to run the software needed to build the devdocs project in a self-contained virtual machine (VM). Our Vagrant project clones the devdocs repository in the VM and shares the devdocs
directory with your system in the root of this project. You can then run Jekyll from the VM in /vagrant/devdocs
project root.
Vagrantfile
- a new VM configurationbootstrap.sh
- VM software installation
Install the VirtualBox and Vagrant software for your operating system:
You can change the following parameters in Vagrantfile
:
NAME
is a name of virtual machine (default:magento-devdocs
).HOST_PORT
is a localhost port that enables you to observe the generated site from your host (default:4000
).RAM
is the amount of RAM used by the virtual VM (default:1024
MB).CPU
is the maximum percentage of CPU used for the VM. (default:50
percent).
To enable symlinks to work, Windows users must run both the UNIX shell (recommended, Cygwin) and the VirtualBox application as administrator. The easiest way to do that is to modify the applications' shortcuts as follows:
- Right-click the application on your desktop or under Start > All Programs
- From the pop-up menu, click Properties.
- In the Properties dialog box, click Advanced.
- Select the Run as administrator check box.
- Follow the prompts on your screen to save your changes.
- Using a terminal, change to
vagrant
on your host (that is, the directory in which this README is located). Example:cd ~/magento-devdocs-vagrant/
- Create and configure guest machines according to the Vagrantfile
vagrant up
- Wait for the project to initialize, clone the repository, and install all gems. This command takes some time to complete the first time you run it.
SSH into a running Vagrant machine:
vagrant ssh
Run Jekyll:
cd /vagrant/devdocs/
bin/jekyll serve --host=0.0.0.0
After Jekyll has started, go to http://127.0.0.1:4000
in a web browser on your host.
For additional command options, see Basic Usage.
If you made any changes in devdocs project, you can stop Jekyll and run it again to regenerate the _site
and preview them in HTML. Automatic regeneration doesn't work in the VM.
All commands must be run in the terminal from the directory that contains Vagrantfile
.
-
Stop Jekyll server. (Stops devdocs site generation.)
vagrant ssh -c "kill $(ps aux | grep '[j]ekyll' | awk '{print $2}')"
-
Run Jekyll server. (Generates devdocs site.)
vagrant ssh -c 'cd /vagrant/devdocs; jekyll serve --host=0.0.0.0'
-
Reload Jekyll server. (Regenerates devdocs site.)
vagrant ssh -c "kill $(ps aux | grep '[j]ekyll' | awk '{print $2}'); cd /vagrant/devdocs; jekyll serve --host=0.0.0.0"
-
Connect to the running virtual machine. You can run Jekyll commands inside the virtual machine from the
/vagrant/devdocs
directory.vagrant ssh
(VM command) To terminate the connection, run the command:
exit
-
Shut down the running virtual machine
vagrant halt
-
Start and configure the virtual machine
vagrant up
-
Stop and remove the virtual machine
vagrant destroy
-
Reload virtual machine to apply changes in
Vagrantfile
vagrant reload
-
Reload virtual machine to apply changes in
Vagrantfile
andbootstrap.sh
vagrant reload --provision
-
Reload virtual machine to apply changes in
bootstrap.sh
vagrant provision