Note: If you are not using Git yet for your project, you can use `git clone` instead of `git submodule `.
- If you are not using Git yet for your project, you can use `git clone` instead of `git submodule `.
*To keep track of your Laradock changes, between your projects and also keep Laradock updated [check this docs](/documentation/#keep-track-of-your-laradock-changes)*
- Note 2: To keep track of your Laradock changes, between your projects and also keep Laradock updated. [Check this](/documentation/#keep-track-of-your-laradock-changes)
Your folder structure should look like this:
Your folder structure should look like this:
```
```
+ project-a
+ project-a
+ laradock-a
+ laradock-a
+ project-b
+ project-b
+ laradock-b
+ laradock-b
```
```
(It's important to rename the folders differently in each project.)
*(It's important to rename the laradock folders to unique name in each project, if you want to run laradock per project).*
> **Now jump to the [Usage](#Usage) section.**
> **Now jump to the [Usage](#Usage) section.**
...
@@ -77,11 +75,12 @@ Your folder structure should look like this:
...
@@ -77,11 +75,12 @@ Your folder structure should look like this:
2 - Edit your web server sites configuration.
2 - Edit your web server sites configuration.
**In case of NGINX:** open `nginx/sites/default.conf` and change the `root` from `/var/www/public` to `/var/www/{my-project-folder-name}/public`.
**NGINX Example:**
Open `nginx/sites/default.conf` and change the `root` from `/var/www/public` to `/var/www/{my-project-folder-name}/public`.
*Or you can keep `default.conf` as it is, and create a separate config `my-site.conf` file for it.*
*Or you can keep `default.conf` as it is, and create a separate config `my-site.conf` file for it.*