Fix typos and add missing last step in Generalize-To-Lamp.md

This commit is contained in:
Hosung Song 2018-10-15 15:22:49 -07:00
Родитель ee0214a6c1
Коммит bb6d440af5
2 изменённых файлов: 5 добавлений и 3 удалений

Просмотреть файл

@ -58,7 +58,7 @@ chmod 400 /azlamp/certs/wpsitename.mydomain.com/*
Navigate to the WordPress content directory and run the following command:
```
mkdir -p /azlam/data/wpsitename.mydomain.com/wp-content/uploads
mkdir -p /azlamp/data/wpsitename.mydomain.com/wp-content/uploads
cd /azlamp/html/wpsitename.mydomain.com
ln -s /azlamp/data/wpsitename.mydomain.com/wp-content/uploads .
```
@ -74,7 +74,7 @@ On the controller machine, look up the file `/azlamp/bin/update-vmss-config`. If
```
#1)
# . /azlamp/bin/utils.sh
# reset_all_sites true VMSS apache
# reset_all_sites_on_vmss true VMSS apache
#;;
```
@ -82,4 +82,6 @@ Remove all the leading `#` characters from these lines (uncommenting) and save t
If you are adding sites for the second or later time, you'll already have the above lines commented out. Just create another `case` block, copying the 4 lines, but make sure to change the number so that it's one greater than the last VMSS config version number (you should be able to find that from the script).
The last step is to let the `/azlamp/html` directory sync with `/var/www/html` in every VMSS instance. This should be done by running `/usr/local/bin/update_last_modified_time.azlamp.sh` script on the controller machine as root. Once this is run and after a minute, the `/var/www/html` directory on every VMSS instance should be the same as `/azlamp/html`, and the newly added sites should be available.
At this point, your LAMP application is setup to use in the LAMP cluster. If you'd like to install a separate LAMP application (WordPress or otherwise), you'll have to repeat the process listed here with a new domain for the new application.

Просмотреть файл

@ -257,7 +257,7 @@ do
#1)
# . /azlamp/bin/utils.sh
# reset_all_sites true VMSS apache
# reset_all_sites_on_vmss true VMSS apache
#;;
*)