ykxiao
/
laradock
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update the docs

This commit is contained in:
Mahmoud Zalt 2017-02-22 15:58:06 -05:00
parent 8e8020e8b0
commit e5fa629a64
20 changed files with 3406 additions and 3261 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/_settings/config.toml
View File

@ -47,44 +47,44 @@ googleAnalytics = ""
# ------- MENU START -----------------------------------------
[[menu.main]]
name = "Introduction"
name = "Overview"
url = "/"
weight = 0
weight = 1
[[menu.main]]
name = "Getting started"
name = "Getting Started"
url = "getting-started/"
weight = 10
weight = 2
[[menu.main]]
name = "Documentation"
url = "documentation/"
weight = 20
weight = 3
[[menu.main]]
name = "Related Projects"
url = "related-projects/"
weight = 30
weight = 4
[[menu.main]]
name = "Help & Questions"
url = "help/"
weight = 40
weight = 5
[[menu.main]]
name = "Contributing"
url = "contributing/"
weight = 50
weight = 6
[[menu.main]]
name = "License"
url = "license/"
weight = 60
weight = 7
# ------- MENU END -----------------------------------------
[blackfriday]
smartypants = false
fractions = false
smartDashes = false
plainIDAnchors = false
smartypants = true
fractions = true
smartDashes = true
plainIDAnchors = true

2
docs/_settings/content/contributing/index.md
View File

@ -1,7 +1,7 @@
---
title: Contributing
type: index
weight: 50
weight: 6
---

2
docs/_settings/content/documentation/index.md
View File

@ -1,7 +1,7 @@
---
title: Documentation
type: index
weight: 20
weight: 3
---

21
docs/_settings/content/getting-started/index.md
View File

@ -1,13 +1,11 @@
---
date: 2017
title: Getting started
weight: 10
title: Getting Started
type: index
weight: 2
---
<a name="Requirements"></a>
## Requirements
- [Git](https://git-scm.com/downloads)
@ -16,8 +14,6 @@ weight: 10
<a name="Installation"></a>
## Installation
Choose the setup the best suits your needs.
@ -114,8 +110,6 @@ Do the same for each project `project2.conf`, `project3.conf`,...
<a name="Usage"></a>
## Usage
**Read Before starting:**
@ -183,12 +177,3 @@ DB_HOST=mysql
If you need a special support. Contact me, more details in the [Help & Questions](#Help) section.

2
docs/_settings/content/help/index.md
View File

@ -1,7 +1,7 @@
---
title: Help & Questions
type: index
weight: 40
weight: 5
---
Join the chat room on [Gitter](https://gitter.im/LaraDock/laradock) and get help and support from the community.

4
docs/_settings/content/index.md
View File

@ -1,7 +1,7 @@
---
title: Welcome to Laradock
title: Overview
type: index
weight: 0
weight: 1
---
LaraDock strives to make the PHP development experience easier and faster.

2
docs/_settings/content/license/index.md
View File

@ -1,7 +1,7 @@
---
title: License
type: index
weight: 60
weight: 7
---
[MIT License](https://github.com/laradock/laradock/blob/master/LICENSE) (MIT)

2
docs/_settings/content/related-projects/index.md
View File

@ -1,7 +1,7 @@
---
title: Related Projects
type: index
weight: 30
weight: 4
---

40
docs/contributing/index.html
View File

@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a title="Getting started" href="http://laradock.io/getting-started/">
<a title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>
@ -336,26 +336,26 @@
<h2 id="guidelines:d680e8a854a7cbad6d490c445cba2eba">Guidelines</h2>
<h2 id="guidelines">Guidelines</h2>
<p>Your contribution is more than welcome.</p>
<h3 id="got-a-question-or-problem:d680e8a854a7cbad6d490c445cba2eba">Got a Question or Problem?</h3>
<h3 id="got-a-question-or-problem">Got a Question or Problem?</h3>
<p>If you have questions about how to use LaraDock, please direct your questions to the discussion on <a href="https://gitter.im/LaraDock/laradock">Gitter</a>. If you believe your question could help others, then consider opening an <a href="https://github.com/laradock/laradock/issues">Issue</a> (it will be labeled as Question).</p>
<h3 id="found-an-issue:d680e8a854a7cbad6d490c445cba2eba">Found an Issue?</h3>
<h3 id="found-an-issue">Found an Issue?</h3>
<p>If you find a bug in the source code or a mistake in the documentation, you can help us by
submitting an <a href="https://github.com/laradock/laradock/issues">Issue</a>. Even better you can submit a Pull Request with a fix.</p>
<h3 id="want-a-feature:d680e8a854a7cbad6d490c445cba2eba">Want a Feature?</h3>
<h3 id="want-a-feature">Want a Feature?</h3>
<p>You can request a new feature by submitting an <a href="https://github.com/laradock/laradock/issues">Issue</a> (it will be labeled as Feature Suggestion). If you would like to implement a new feature then consider submitting a Pull Request.</p>
<h2 id="coding-guidelines:d680e8a854a7cbad6d490c445cba2eba">Coding Guidelines</h2>
<h2 id="coding-guidelines">Coding Guidelines</h2>
<h3 id="support-new-software:d680e8a854a7cbad6d490c445cba2eba">Support new Software</h3>
<h3 id="support-new-software">Support new Software</h3>
<ul>
<li><p>Create folder with the software name.</p></li>
@ -371,7 +371,7 @@ submitting an <a href="https://github.com/laradock/laradock/issues">Issue</a>. E
<li><p>Add the software in the <code>Readme</code>.</p></li>
</ul>
<h3 id="edit-existing-software:d680e8a854a7cbad6d490c445cba2eba">Edit existing Software</h3>
<h3 id="edit-existing-software">Edit existing Software</h3>
<ul>
<li><p>Open the software (container) folder.</p></li>
@ -384,17 +384,17 @@ you need to edit their Dockerfiles from their GitHub repositories. For more info
<li><p>Make sure to update the <code>Readme</code> in case you made any changes.</p></li>
</ul>
<h2 id="issue-pr-submission-guidelines:d680e8a854a7cbad6d490c445cba2eba">Issue/PR Submission Guidelines</h2>
<h2 id="issue-pr-submission-guidelines">Issue/PR Submission Guidelines</h2>
<h3 id="submitting-an-issue:d680e8a854a7cbad6d490c445cba2eba">Submitting an Issue</h3>
<h3 id="submitting-an-issue">Submitting an Issue</h3>
<p>Before you submit your issue search the archive, maybe your question was already answered.</p>
<p>If your issue appears to be a bug, and hasn't been reported, open a new issue.
<p>If your issue appears to be a bug, and hasn&rsquo;t been reported, open a new issue.
Help us to maximize the effort we can spend fixing issues and adding new
features, by not reporting duplicate issues.</p>
<h3 id="before-submitting-a-pull-request-pr:d680e8a854a7cbad6d490c445cba2eba">Before Submitting a Pull Request (PR)</h3>
<h3 id="before-submitting-a-pull-request-pr">Before Submitting a Pull Request (PR)</h3>
<p>Always Test everything and make sure its working:</p>
@ -403,7 +403,7 @@ features, by not reporting duplicate issues.</p>
<li>Before editing anything:
<ul>
<li>Test building the container (docker-compose build --no-cache container-name) build with no cache first.</li>
<li>Test building the container (docker-compose build &ndash;no-cache container-name) build with no cache first.</li>
<li>Test running the container with some other containers in real app and see of everything is working fine.</li>
</ul></li>
<li>Now edit the container (edit section by section and test rebuilding the container after every edited section)
@ -414,12 +414,12 @@ features, by not reporting duplicate issues.</p>
</ul></li>
</ul>
<h3 id="submitting-a-pr:d680e8a854a7cbad6d490c445cba2eba">Submitting a PR</h3>
<h3 id="submitting-a-pr">Submitting a PR</h3>
<p>Consider the following guidelines:</p>
<ul>
<li><p>Search <a href="https://github.com/laradock/laradock/pulls">GitHub</a> for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.</p></li>
<li><p>Search <a href="https://github.com/laradock/laradock/pulls">GitHub</a> for an open or closed Pull Request that relates to your submission. You don&rsquo;t want to duplicate effort.</p></li>
<li><p>Make your changes in a new git branch:</p>
@ -454,7 +454,7 @@ git push origin my-fix-branch -f
<p><em>WARNING. Squashing or reverting commits and forced push thereafter may remove GitHub comments on code that were previously made by you and others in your commits.</em></p>
<h3 id="after-your-pr-is-merged:d680e8a854a7cbad6d490c445cba2eba">After your PR is merged</h3>
<h3 id="after-your-pr-is-merged">After your PR is merged</h3>
<p>After your pull request is merged, you can safely delete your branch and pull the changes
from the main (upstream) repository:</p>
@ -483,7 +483,7 @@ from the main (upstream) repository:</p>
<p><br></p>
<h3 id="happy-coding:d680e8a854a7cbad6d490c445cba2eba">Happy Coding :)</h3>
<h3 id="happy-coding">Happy Coding :)</h3>
<aside class="copyright" role="note">

32
docs/contributing/index.xml
View File

@ -16,26 +16,26 @@
<guid>http://laradock.io/contributing/</guid>
<description>
&lt;h2 id=&#34;guidelines:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Guidelines&lt;/h2&gt;
&lt;h2 id=&#34;guidelines&#34;&gt;Guidelines&lt;/h2&gt;
&lt;p&gt;Your contribution is more than welcome.&lt;/p&gt;
&lt;h3 id=&#34;got-a-question-or-problem:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Got a Question or Problem?&lt;/h3&gt;
&lt;h3 id=&#34;got-a-question-or-problem&#34;&gt;Got a Question or Problem?&lt;/h3&gt;
&lt;p&gt;If you have questions about how to use LaraDock, please direct your questions to the discussion on &lt;a href=&#34;https://gitter.im/LaraDock/laradock&#34;&gt;Gitter&lt;/a&gt;. If you believe your question could help others, then consider opening an &lt;a href=&#34;https://github.com/laradock/laradock/issues&#34;&gt;Issue&lt;/a&gt; (it will be labeled as Question).&lt;/p&gt;
&lt;h3 id=&#34;found-an-issue:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Found an Issue?&lt;/h3&gt;
&lt;h3 id=&#34;found-an-issue&#34;&gt;Found an Issue?&lt;/h3&gt;
&lt;p&gt;If you find a bug in the source code or a mistake in the documentation, you can help us by
submitting an &lt;a href=&#34;https://github.com/laradock/laradock/issues&#34;&gt;Issue&lt;/a&gt;. Even better you can submit a Pull Request with a fix.&lt;/p&gt;
&lt;h3 id=&#34;want-a-feature:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Want a Feature?&lt;/h3&gt;
&lt;h3 id=&#34;want-a-feature&#34;&gt;Want a Feature?&lt;/h3&gt;
&lt;p&gt;You can request a new feature by submitting an &lt;a href=&#34;https://github.com/laradock/laradock/issues&#34;&gt;Issue&lt;/a&gt; (it will be labeled as Feature Suggestion). If you would like to implement a new feature then consider submitting a Pull Request.&lt;/p&gt;
&lt;h2 id=&#34;coding-guidelines:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Coding Guidelines&lt;/h2&gt;
&lt;h2 id=&#34;coding-guidelines&#34;&gt;Coding Guidelines&lt;/h2&gt;
&lt;h3 id=&#34;support-new-software:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Support new Software&lt;/h3&gt;
&lt;h3 id=&#34;support-new-software&#34;&gt;Support new Software&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Create folder with the software name.&lt;/p&gt;&lt;/li&gt;
@ -51,7 +51,7 @@ submitting an &lt;a href=&#34;https://github.com/laradock/laradock/issues&#34;&g
&lt;li&gt;&lt;p&gt;Add the software in the &lt;code&gt;Readme&lt;/code&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;edit-existing-software:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Edit existing Software&lt;/h3&gt;
&lt;h3 id=&#34;edit-existing-software&#34;&gt;Edit existing Software&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Open the software (container) folder.&lt;/p&gt;&lt;/li&gt;
@ -64,17 +64,17 @@ you need to edit their Dockerfiles from their GitHub repositories. For more info
&lt;li&gt;&lt;p&gt;Make sure to update the &lt;code&gt;Readme&lt;/code&gt; in case you made any changes.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;issue-pr-submission-guidelines:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Issue/PR Submission Guidelines&lt;/h2&gt;
&lt;h2 id=&#34;issue-pr-submission-guidelines&#34;&gt;Issue/PR Submission Guidelines&lt;/h2&gt;
&lt;h3 id=&#34;submitting-an-issue:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Submitting an Issue&lt;/h3&gt;
&lt;h3 id=&#34;submitting-an-issue&#34;&gt;Submitting an Issue&lt;/h3&gt;
&lt;p&gt;Before you submit your issue search the archive, maybe your question was already answered.&lt;/p&gt;
&lt;p&gt;If your issue appears to be a bug, and hasn&#39;t been reported, open a new issue.
&lt;p&gt;If your issue appears to be a bug, and hasn&amp;rsquo;t been reported, open a new issue.
Help us to maximize the effort we can spend fixing issues and adding new
features, by not reporting duplicate issues.&lt;/p&gt;
&lt;h3 id=&#34;before-submitting-a-pull-request-pr:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Before Submitting a Pull Request (PR)&lt;/h3&gt;
&lt;h3 id=&#34;before-submitting-a-pull-request-pr&#34;&gt;Before Submitting a Pull Request (PR)&lt;/h3&gt;
&lt;p&gt;Always Test everything and make sure its working:&lt;/p&gt;
@ -83,7 +83,7 @@ features, by not reporting duplicate issues.&lt;/p&gt;
&lt;li&gt;Before editing anything:
&lt;ul&gt;
&lt;li&gt;Test building the container (docker-compose build --no-cache container-name) build with no cache first.&lt;/li&gt;
&lt;li&gt;Test building the container (docker-compose build &amp;ndash;no-cache container-name) build with no cache first.&lt;/li&gt;
&lt;li&gt;Test running the container with some other containers in real app and see of everything is working fine.&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Now edit the container (edit section by section and test rebuilding the container after every edited section)
@ -94,12 +94,12 @@ features, by not reporting duplicate issues.&lt;/p&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;submitting-a-pr:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Submitting a PR&lt;/h3&gt;
&lt;h3 id=&#34;submitting-a-pr&#34;&gt;Submitting a PR&lt;/h3&gt;
&lt;p&gt;Consider the following guidelines:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Search &lt;a href=&#34;https://github.com/laradock/laradock/pulls&#34;&gt;GitHub&lt;/a&gt; for an open or closed Pull Request that relates to your submission. You don&#39;t want to duplicate effort.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Search &lt;a href=&#34;https://github.com/laradock/laradock/pulls&#34;&gt;GitHub&lt;/a&gt; for an open or closed Pull Request that relates to your submission. You don&amp;rsquo;t want to duplicate effort.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Make your changes in a new git branch:&lt;/p&gt;
@ -134,7 +134,7 @@ git push origin my-fix-branch -f
&lt;p&gt;&lt;em&gt;WARNING. Squashing or reverting commits and forced push thereafter may remove GitHub comments on code that were previously made by you and others in your commits.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;after-your-pr-is-merged:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;After your PR is merged&lt;/h3&gt;
&lt;h3 id=&#34;after-your-pr-is-merged&#34;&gt;After your PR is merged&lt;/h3&gt;
&lt;p&gt;After your pull request is merged, you can safely delete your branch and pull the changes
from the main (upstream) repository:&lt;/p&gt;
@ -163,7 +163,7 @@ from the main (upstream) repository:&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;happy-coding:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Happy Coding :)&lt;/h3&gt;
&lt;h3 id=&#34;happy-coding&#34;&gt;Happy Coding :)&lt;/h3&gt;
</description>
</item>

174
docs/documentation/index.html
View File

@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a title="Getting started" href="http://laradock.io/getting-started/">
<a title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>
@ -340,7 +340,7 @@
<p><a name="List-current-running-Containers"></a></p>
<h2 id="list-current-running-containers:d680e8a854a7cbad6d490c445cba2eba">List current running Containers</h2>
<h2 id="list-current-running-containers">List current running Containers</h2>
<pre><code class="language-bash">docker ps
</code></pre>
@ -353,7 +353,7 @@
<p><br>
<a name="Close-all-running-Containers"></a></p>
<h2 id="close-all-running-containers:d680e8a854a7cbad6d490c445cba2eba">Close all running Containers</h2>
<h2 id="close-all-running-containers">Close all running Containers</h2>
<pre><code class="language-bash">docker-compose stop
</code></pre>
@ -366,7 +366,7 @@
<p><br>
<a name="Delete-all-existing-Containers"></a></p>
<h2 id="delete-all-existing-containers:d680e8a854a7cbad6d490c445cba2eba">Delete all existing Containers</h2>
<h2 id="delete-all-existing-containers">Delete all existing Containers</h2>
<pre><code class="language-bash">docker-compose down
</code></pre>
@ -374,7 +374,7 @@
<p><br>
<a name="Enter-Container"></a></p>
<h2 id="enter-a-container-run-commands-in-a-running-container:d680e8a854a7cbad6d490c445cba2eba">Enter a Container (run commands in a running Container)</h2>
<h2 id="enter-a-container-run-commands-in-a-running-container">Enter a Container (run commands in a running Container)</h2>
<p>1 - First list the current running containers with <code>docker ps</code></p>
@ -398,7 +398,7 @@
<p><br>
<a name="Edit-Container"></a></p>
<h2 id="edit-default-container-configuration:d680e8a854a7cbad6d490c445cba2eba">Edit default container configuration</h2>
<h2 id="edit-default-container-configuration">Edit default container configuration</h2>
<p>Open the <code>docker-compose.yml</code> and change anything you want.</p>
@ -421,7 +421,7 @@
<p><br>
<a name="Edit-a-Docker-Image"></a></p>
<h2 id="edit-a-docker-image:d680e8a854a7cbad6d490c445cba2eba">Edit a Docker Image</h2>
<h2 id="edit-a-docker-image">Edit a Docker Image</h2>
<p>1 - Find the <code>Dockerfile</code> of the image you want to edit,
<br>
@ -439,7 +439,7 @@ example for <code>mysql</code> it will be <code>mysql/Dockerfile</code>.</p>
<p><br>
<a name="Build-Re-build-Containers"></a></p>
<h2 id="build-re-build-containers:d680e8a854a7cbad6d490c445cba2eba">Build/Re-build Containers</h2>
<h2 id="build-re-build-containers">Build/Re-build Containers</h2>
<p>If you do any change to any <code>Dockerfile</code> make sure you run this command, for the changes to take effect:</p>
@ -456,18 +456,18 @@ example for <code>mysql</code> it will be <code>mysql/Dockerfile</code>.</p>
<p><br>
<a name="Add-Docker-Images"></a></p>
<h2 id="add-more-software-docker-images:d680e8a854a7cbad6d490c445cba2eba">Add more Software (Docker Images)</h2>
<h2 id="add-more-software-docker-images">Add more Software (Docker Images)</h2>
<p>To add an image (software), just edit the <code>docker-compose.yml</code> and add your container details, to do so you need to be familiar with the <a href="https://docs.docker.com/compose/compose-file/">docker compose file syntax</a>.</p>
<p><br>
<a name="View-the-Log-files"></a></p>
<h2 id="view-the-log-files:d680e8a854a7cbad6d490c445cba2eba">View the Log files</h2>
<h2 id="view-the-log-files">View the Log files</h2>
<p>The NGINX Log file is stored in the <code>logs/nginx</code> directory.</p>
<p>However to view the logs of all the other containers (MySQL, PHP-FPM,...) you can run this:</p>
<p>However to view the logs of all the other containers (MySQL, PHP-FPM,&hellip;) you can run this:</p>
<pre><code class="language-bash">docker logs {container-name}
</code></pre>
@ -477,7 +477,7 @@ example for <code>mysql</code> it will be <code>mysql/Dockerfile</code>.</p>
<p><a name="Install-PHP-Extensions"></a></p>
<h2 id="install-php-extensions:d680e8a854a7cbad6d490c445cba2eba">Install PHP Extensions</h2>
<h2 id="install-php-extensions">Install PHP Extensions</h2>
<p>Before installing PHP extensions, you have to decide whether you need for the <code>FPM</code> or <code>CLI</code> because each lives on a different container, if you need it for both you have to edit both containers.</p>
@ -488,15 +488,15 @@ The PHP-CLI extensions should be installed in <code>workspace/Dockerfile</code>.
<p><br>
<a name="Change-the-PHP-FPM-Version"></a></p>
<h2 id="change-the-php-fpm-version:d680e8a854a7cbad6d490c445cba2eba">Change the (PHP-FPM) Version</h2>
<h2 id="change-the-php-fpm-version">Change the (PHP-FPM) Version</h2>
<p>By default <strong>PHP-FPM 7.0</strong> is running.</p>
<blockquote>
<p>The PHP-FPM is responsible of serving your application code, you don't have to change the PHP-CLI version if you are planning to run your application on different PHP-FPM version.</p>
<p>The PHP-FPM is responsible of serving your application code, you don&rsquo;t have to change the PHP-CLI version if you are planning to run your application on different PHP-FPM version.</p>
</blockquote>
<h3 id="a-switch-from-php-7-0-to-php-5-6:d680e8a854a7cbad6d490c445cba2eba">A) Switch from PHP <code>7.0</code> to PHP <code>5.6</code></h3>
<h3 id="a-switch-from-php-7-0-to-php-5-6">A) Switch from PHP <code>7.0</code> to PHP <code>5.6</code></h3>
<p>1 - Open the <code>docker-compose.yml</code>.</p>
@ -520,7 +520,7 @@ The PHP-CLI extensions should be installed in <code>workspace/Dockerfile</code>.
<p>For more details about the PHP base image, visit the <a href="https://hub.docker.com/_/php/">official PHP docker images</a>.</p>
</blockquote>
<h3 id="b-switch-from-php-7-0-or-5-6-to-php-5-5:d680e8a854a7cbad6d490c445cba2eba">B) Switch from PHP <code>7.0</code> or <code>5.6</code> to PHP <code>5.5</code></h3>
<h3 id="b-switch-from-php-7-0-or-5-6-to-php-5-5">B) Switch from PHP <code>7.0</code> or <code>5.6</code> to PHP <code>5.5</code></h3>
<p>We do not natively support PHP 5.5 anymore, but you can get it in few steps:</p>
@ -539,22 +539,22 @@ The PHP-CLI extensions should be installed in <code>workspace/Dockerfile</code>.
<p><br>
<a name="Change-the-PHP-CLI-Version"></a></p>
<h2 id="change-the-php-cli-version:d680e8a854a7cbad6d490c445cba2eba">Change the PHP-CLI Version</h2>
<h2 id="change-the-php-cli-version">Change the PHP-CLI Version</h2>
<p>By default <strong>PHP-CLI 7.0</strong> is running.</p>
<blockquote>
<p>Note: it's not very essential to edit the PHP-CLI version. The PHP-CLI is only used for the Artisan Commands &amp; Composer. It doesn't serve your Application code, this is the PHP-FPM job.</p>
<p>Note: it&rsquo;s not very essential to edit the PHP-CLI version. The PHP-CLI is only used for the Artisan Commands &amp; Composer. It doesn&rsquo;t serve your Application code, this is the PHP-FPM job.</p>
</blockquote>
<p>The PHP-CLI is installed in the Workspace container. To change the PHP-CLI version you need to edit the <code>workspace/Dockerfile</code>.</p>
<p>Right now you have to manually edit the <code>Dockerfile</code> or create a new one like it's done for the PHP-FPM. (consider contributing).</p>
<p>Right now you have to manually edit the <code>Dockerfile</code> or create a new one like it&rsquo;s done for the PHP-FPM. (consider contributing).</p>
<p><br>
<a name="Install-xDebug"></a></p>
<h2 id="install-xdebug:d680e8a854a7cbad6d490c445cba2eba">Install xDebug</h2>
<h2 id="install-xdebug">Install xDebug</h2>
<p>1 - First install <code>xDebug</code> in the Workspace and the PHP-FPM Containers:
<br>
@ -598,7 +598,7 @@ xdebug.remote_connect_back=1
<p><br>
<a name="Control-xDebug"></a></p>
<h2 id="start-stop-xdebug:d680e8a854a7cbad6d490c445cba2eba">Start/Stop xDebug:</h2>
<h2 id="start-stop-xdebug">Start/Stop xDebug:</h2>
<p>By installing xDebug, you are enabling it to run on startup by default.</p>
@ -610,12 +610,12 @@ xdebug.remote_connect_back=1
<li>See the status: <code>./xdebugPhpFpm status</code>.</li>
</ul>
<p>Note: If <code>./xdebugPhpFpm</code> doesn't execute and gives <code>Permission Denied</code> error the problem can be that file <code>xdebugPhpFpm</code> doesn't have execution access. This can be fixed by running <code>chmod</code> command with desired access permissions.</p>
<p>Note: If <code>./xdebugPhpFpm</code> doesn&rsquo;t execute and gives <code>Permission Denied</code> error the problem can be that file <code>xdebugPhpFpm</code> doesn&rsquo;t have execution access. This can be fixed by running <code>chmod</code> command with desired access permissions.</p>
<p><br>
<a name="Install-Deployer"></a></p>
<h2 id="install-deployer-deployment-tool-for-php:d680e8a854a7cbad6d490c445cba2eba">Install Deployer (Deployment tool for PHP)</h2>
<h2 id="install-deployer-deployment-tool-for-php">Install Deployer (Deployment tool for PHP)</h2>
<p>1 - Open the <code>docker-compose.yml</code> file
<br>
@ -636,7 +636,7 @@ xdebug.remote_connect_back=1
<p>4 - Re-build the containers <code>docker-compose build workspace</code></p>
<h4 id="deployer-documentation-here-https-deployer-org-docs:d680e8a854a7cbad6d490c445cba2eba"><a href="https://deployer.org/docs">Deployer Documentation Here</a></h4>
<h4 id="deployer-documentation-here-https-deployer-org-docs"><a href="https://deployer.org/docs">Deployer Documentation Here</a></h4>
<p><br>
<a name="Production"></a></p>
@ -644,11 +644,11 @@ xdebug.remote_connect_back=1
<p><br>
<a name="LaraDock-for-Production"></a></p>
<h2 id="prepare-laradock-for-production:d680e8a854a7cbad6d490c445cba2eba">Prepare LaraDock for Production</h2>
<h2 id="prepare-laradock-for-production">Prepare LaraDock for Production</h2>
<p>It's recommended for production to create a custom <code>docker-compose.yml</code> file. For that reason, LaraDock is shipped with <code>production-docker-compose.yml</code> which should contain only the containers you are planning to run on production (usage example: <code>docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...</code>).</p>
<p>It&rsquo;s recommended for production to create a custom <code>docker-compose.yml</code> file. For that reason, LaraDock is shipped with <code>production-docker-compose.yml</code> which should contain only the containers you are planning to run on production (usage example: <code>docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...</code>).</p>
<p>Note: The Database (MySQL/MariaDB/...) ports should not be forwarded on production, because Docker will automatically publish the port on the host, which is quite insecure, unless specifically told not to. So make sure to remove these lines:</p>
<p>Note: The Database (MySQL/MariaDB/&hellip;) ports should not be forwarded on production, because Docker will automatically publish the port on the host, which is quite insecure, unless specifically told not to. So make sure to remove these lines:</p>
<pre><code>ports:
- &quot;3306:3306&quot;
@ -659,16 +659,16 @@ xdebug.remote_connect_back=1
<p><br>
<a name="Digital-Ocean"></a></p>
<h2 id="setup-laravel-and-docker-on-digital-ocean:d680e8a854a7cbad6d490c445cba2eba">Setup Laravel and Docker on Digital Ocean</h2>
<h2 id="setup-laravel-and-docker-on-digital-ocean">Setup Laravel and Docker on Digital Ocean</h2>
<h3 id="full-guide-here-https-github-com-laradock-laradock-blob-master-guides-digital-ocean-md:d680e8a854a7cbad6d490c445cba2eba"><a href="https://github.com/laradock/laradock/blob/master/_guides/digital_ocean.md">Full Guide Here</a></h3>
<h3 id="full-guide-here-https-github-com-laradock-laradock-blob-master-guides-digital-ocean-md"><a href="https://github.com/laradock/laradock/blob/master/_guides/digital_ocean.md">Full Guide Here</a></h3>
<p><br>
<a name="Laravel"></a></p>
<p><a name="Install-Laravel"></a></p>
<h2 id="install-laravel-from-a-docker-container:d680e8a854a7cbad6d490c445cba2eba">Install Laravel from a Docker Container</h2>
<h2 id="install-laravel-from-a-docker-container">Install Laravel from a Docker Container</h2>
<p>1 - First you need to enter the Workspace Container.</p>
@ -708,7 +708,7 @@ xdebug.remote_connect_back=1
<p><br>
<a name="Run-Artisan-Commands"></a></p>
<h2 id="run-artisan-commands:d680e8a854a7cbad6d490c445cba2eba">Run Artisan Commands</h2>
<h2 id="run-artisan-commands">Run Artisan Commands</h2>
<p>You can run artisan commands and many other Terminal commands from the Workspace container.</p>
@ -727,7 +727,7 @@ xdebug.remote_connect_back=1
<pre><code class="language-bash">docker-compose exec workspace bash
</code></pre>
<p>Add <code>--user=laradock</code> (example <code>docker-compose exec --user=laradock workspace bash</code>) to have files created as your host's user.</p>
<p>Add <code>--user=laradock</code> (example <code>docker-compose exec --user=laradock workspace bash</code>) to have files created as your host&rsquo;s user.</p>
<p>4 - Run anything you want :)</p>
@ -743,7 +743,7 @@ xdebug.remote_connect_back=1
<p><br>
<a name="Run-Laravel-Queue-Worker"></a></p>
<h2 id="run-laravel-queue-worker:d680e8a854a7cbad6d490c445cba2eba">Run Laravel Queue Worker</h2>
<h2 id="run-laravel-queue-worker">Run Laravel Queue Worker</h2>
<p>1 - First add <code>php-worker</code> container. It will be similar as like PHP-FPM Container.
<br>
@ -768,19 +768,19 @@ b) add a new service container by simply copy-paste this section below PHP-FPM c
<p><br>
<a name="Use-Redis"></a></p>
<h2 id="use-redis:d680e8a854a7cbad6d490c445cba2eba">Use Redis</h2>
<h2 id="use-redis">Use Redis</h2>
<p>1 - First make sure you run the Redis Container (<code>redis</code>) with the <code>docker-compose up</code> command.</p>
<pre><code class="language-bash">docker-compose up -d redis
</code></pre>
<p>2 - Open your Laravel's <code>.env</code> file and set the <code>REDIS_HOST</code> to <code>redis</code></p>
<p>2 - Open your Laravel&rsquo;s <code>.env</code> file and set the <code>REDIS_HOST</code> to <code>redis</code></p>
<pre><code class="language-env">REDIS_HOST=redis
</code></pre>
<p>If you don't find the <code>REDIS_HOST</code> variable in your <code>.env</code> file. Go to the database configuration file <code>config/database.php</code> and replace the default <code>127.0.0.1</code> IP with <code>redis</code> for Redis like this:</p>
<p>If you don&rsquo;t find the <code>REDIS_HOST</code> variable in your <code>.env</code> file. Go to the database configuration file <code>config/database.php</code> and replace the default <code>127.0.0.1</code> IP with <code>redis</code> for Redis like this:</p>
<pre><code class="language-php">'redis' =&gt; [
'cluster' =&gt; false,
@ -811,7 +811,7 @@ SESSION_DRIVER=redis
<p><br>
<a name="Use-Mongo"></a></p>
<h2 id="use-mongo:d680e8a854a7cbad6d490c445cba2eba">Use Mongo</h2>
<h2 id="use-mongo">Use Mongo</h2>
<p>1 - First install <code>mongo</code> in the Workspace and the PHP-FPM Containers:
<br>
@ -869,7 +869,7 @@ e) set it to <code>true</code></p>
],
</code></pre>
<p>5 - Open your Laravel's <code>.env</code> file and update the following variables:</p>
<p>5 - Open your Laravel&rsquo;s <code>.env</code> file and update the following variables:</p>
<ul>
<li>set the <code>DB_HOST</code> to your <code>mongo</code>.</li>
@ -895,7 +895,7 @@ e) set it to <code>true</code></p>
<p><br>
<a name="Use-phpMyAdmin"></a></p>
<h2 id="use-phpmyadmin:d680e8a854a7cbad6d490c445cba2eba">Use PhpMyAdmin</h2>
<h2 id="use-phpmyadmin">Use PhpMyAdmin</h2>
<p>1 - Run the phpMyAdmin Container (<code>phpmyadmin</code>) with the <code>docker-compose up</code> command. Example:</p>
@ -911,7 +911,7 @@ docker-compose up -d mariadb phpmyadmin
<p><br>
<a name="Use-pgAdmin"></a></p>
<h2 id="use-pgadmin:d680e8a854a7cbad6d490c445cba2eba">Use PgAdmin</h2>
<h2 id="use-pgadmin">Use PgAdmin</h2>
<p>1 - Run the pgAdmin Container (<code>pgadmin</code>) with the <code>docker-compose up</code> command. Example:</p>
@ -923,7 +923,7 @@ docker-compose up -d mariadb phpmyadmin
<p><br>
<a name="Use-Beanstalkd"></a></p>
<h2 id="use-beanstalkd:d680e8a854a7cbad6d490c445cba2eba">Use Beanstalkd</h2>
<h2 id="use-beanstalkd">Use Beanstalkd</h2>
<p>1 - Run the Beanstalkd Container:</p>
@ -960,7 +960,7 @@ b. set the queue host to beanstalkd : <code>QUEUE_HOST=beanstalkd</code></p>
<p><br>
<a name="Use-ElasticSearch"></a></p>
<h2 id="use-elasticsearch:d680e8a854a7cbad6d490c445cba2eba">Use ElasticSearch</h2>
<h2 id="use-elasticsearch">Use ElasticSearch</h2>
<p>1 - Run the ElasticSearch Container (<code>elasticsearch</code>) with the <code>docker-compose up</code> command:</p>
@ -969,7 +969,7 @@ b. set the queue host to beanstalkd : <code>QUEUE_HOST=beanstalkd</code></p>
<p>2 - Open your browser and visit the localhost on port <strong>9200</strong>: <code>http://localhost:9200</code></p>
<h3 id="install-elasticsearch-plugin:d680e8a854a7cbad6d490c445cba2eba">Install ElasticSearch Plugin</h3>
<h3 id="install-elasticsearch-plugin">Install ElasticSearch Plugin</h3>
<p>1 - Install the ElasticSearch plugin like <a href="https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugins-delete-by-query.html">delete-by-query</a>.</p>
@ -984,7 +984,7 @@ b. set the queue host to beanstalkd : <code>QUEUE_HOST=beanstalkd</code></p>
<p><br>
<a name="Use-Selenium"></a></p>
<h2 id="use-selenium:d680e8a854a7cbad6d490c445cba2eba">Use Selenium</h2>
<h2 id="use-selenium">Use Selenium</h2>
<p>1 - Run the Selenium Container (<code>selenium</code>) with the <code>docker-compose up</code> command. Example:</p>
@ -996,7 +996,7 @@ b. set the queue host to beanstalkd : <code>QUEUE_HOST=beanstalkd</code></p>
<p><br>
<a name="Use-RethinkDB"></a></p>
<h2 id="use-rethinkdb:d680e8a854a7cbad6d490c445cba2eba">Use RethinkDB</h2>
<h2 id="use-rethinkdb">Use RethinkDB</h2>
<p>The RethinkDB is an open-source Database for Real-time Web (<a href="https://rethinkdb.com/">RethinkDB</a>).
A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkDB</a>) is being developed and was released a version for Laravel 5.2 (experimental).</p>
@ -1025,7 +1025,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
],
</code></pre>
<p>4 - Open your Laravel's <code>.env</code> file and update the following variables:</p>
<p>4 - Open your Laravel&rsquo;s <code>.env</code> file and update the following variables:</p>
<ul>
<li>set the <code>DB_CONNECTION</code> to your <code>rethinkdb</code>.</li>
@ -1040,7 +1040,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="Install-CodeIgniter"></a></p>
<h2 id="install-codeigniter:d680e8a854a7cbad6d490c445cba2eba">Install CodeIgniter</h2>
<h2 id="install-codeigniter">Install CodeIgniter</h2>
<p>To install CodeIgniter 3 on LaraDock all you have to do is the following simple steps:</p>
@ -1053,12 +1053,12 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="Misc"></a></p>
<h2 id="miscellaneous:d680e8a854a7cbad6d490c445cba2eba">Miscellaneous</h2>
<h2 id="miscellaneous">Miscellaneous</h2>
<p><br>
<a name="Change-the-timezone"></a></p>
<h2 id="change-the-timezone:d680e8a854a7cbad6d490c445cba2eba">Change the timezone</h2>
<h2 id="change-the-timezone">Change the timezone</h2>
<p>To change the timezone for the <code>workspace</code> container, modify the <code>TZ</code> build argument in the Docker Compose file to one in the <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones">TZ database</a>.</p>
@ -1077,7 +1077,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="CronJobs"></a></p>
<h2 id="adding-cron-jobs:d680e8a854a7cbad6d490c445cba2eba">Adding cron jobs</h2>
<h2 id="adding-cron-jobs">Adding cron jobs</h2>
<p>You can add your cron jobs to <code>workspace/crontab/root</code> after the <code>php artisan</code> line.</p>
@ -1087,12 +1087,12 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
* * * * * root echo &quot;Every Minute&quot; &gt; /var/log/cron.log 2&gt;&amp;1
</code></pre>
<p>Make sure you <a href="#Change-the-timezone">change the timezone</a> if you don't want to use the default (UTC).</p>
<p>Make sure you <a href="#Change-the-timezone">change the timezone</a> if you don&rsquo;t want to use the default (UTC).</p>
<p><br>
<a name="Workspace-ssh"></a></p>
<h2 id="access-workspace-via-ssh:d680e8a854a7cbad6d490c445cba2eba">Access workspace via ssh</h2>
<h2 id="access-workspace-via-ssh">Access workspace via ssh</h2>
<p>You can access the <code>workspace</code> container through <code>localhost:2222</code> by setting the <code>INSTALL_WORKSPACE_SSH</code> build argument to <code>true</code>.</p>
@ -1107,7 +1107,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="MySQL-access-from-host"></a></p>
<h2 id="mysql-access-from-host:d680e8a854a7cbad6d490c445cba2eba">MySQL access from host</h2>
<h2 id="mysql-access-from-host">MySQL access from host</h2>
<p>You can forward the MySQL/MariaDB port to your host by making sure these lines are added to the <code>mysql</code> or <code>mariadb</code> section of the <code>docker-compose.yml</code> or in your <a href="https://docs.docker.com/compose/extends/">environment specific Compose</a> file.</p>
@ -1118,7 +1118,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="MySQL-root-access"></a></p>
<h2 id="mysql-root-access:d680e8a854a7cbad6d490c445cba2eba">MySQL root access</h2>
<h2 id="mysql-root-access">MySQL root access</h2>
<p>The default username and password for the root MySQL user are <code>root</code> and <code>root</code>.</p>
@ -1133,7 +1133,7 @@ A package (<a href="https://github.com/duxet/laravel-rethinkdb">Laravel RethinkD
<p><br>
<a name="Change-MySQL-port"></a></p>
<h2 id="change-mysql-port:d680e8a854a7cbad6d490c445cba2eba">Change MySQL port</h2>
<h2 id="change-mysql-port">Change MySQL port</h2>
<p>Modify the <code>mysql/my.cnf</code> file to set your port number, <code>1234</code> is used as an example.</p>
@ -1146,7 +1146,7 @@ port=1234
<p><br>
<a name="Use-custom-Domain"></a></p>
<h2 id="use-custom-domain-instead-of-the-docker-ip:d680e8a854a7cbad6d490c445cba2eba">Use custom Domain (instead of the Docker IP)</h2>
<h2 id="use-custom-domain-instead-of-the-docker-ip">Use custom Domain (instead of the Docker IP)</h2>
<p>Assuming your custom domain is <code>laravel.dev</code></p>
@ -1165,7 +1165,7 @@ port=1234
<p><br>
<a name="Enable-Global-Composer-Build-Install"></a></p>
<h2 id="enable-global-composer-build-install:d680e8a854a7cbad6d490c445cba2eba">Enable Global Composer Build Install</h2>
<h2 id="enable-global-composer-build-install">Enable Global Composer Build Install</h2>
<p>Enabling Global Composer Install during the build for the container allows you to get your composer requirements installed and available in the container after the build is done.</p>
@ -1190,7 +1190,7 @@ port=1234
<p><br>
<a name="Install-Prestissimo"></a></p>
<h2 id="install-prestissimo:d680e8a854a7cbad6d490c445cba2eba">Install Prestissimo</h2>
<h2 id="install-prestissimo">Install Prestissimo</h2>
<p><a href="https://github.com/hirak/prestissimo">Prestissimo</a> is a plugin for composer which enables parallel install functionality.</p>
@ -1209,7 +1209,7 @@ port=1234
<p><br>
<a name="Install-Node"></a></p>
<h2 id="install-node-nvm:d680e8a854a7cbad6d490c445cba2eba">Install Node + NVM</h2>
<h2 id="install-node-nvm">Install Node + NVM</h2>
<p>To install NVM and NodeJS in the Workspace container</p>
@ -1232,7 +1232,7 @@ port=1234
<p><br>
<a name="Install-Yarn"></a></p>
<h2 id="install-node-yarn:d680e8a854a7cbad6d490c445cba2eba">Install Node + YARN</h2>
<h2 id="install-node-yarn">Install Node + YARN</h2>
<p>Yarn is a new package manager for JavaScript. It is so faster than npm, which you can find <a href="http://yarnpkg.com/en/compare">here</a>.To install NodeJS and <a href="https://yarnpkg.com/">Yarn</a> in the Workspace container:</p>
@ -1256,7 +1256,7 @@ port=1234
<p><br>
<a name="Install-Linuxbrew"></a></p>
<h2 id="install-linuxbrew:d680e8a854a7cbad6d490c445cba2eba">Install Linuxbrew</h2>
<h2 id="install-linuxbrew">Install Linuxbrew</h2>
<p>Linuxbrew is a package manager for Linux. It is the Linux version of MacOS Homebrew and can be found <a href="http://linuxbrew.sh">here</a>. To install Linuxbrew in the Workspace container:</p>
@ -1280,7 +1280,7 @@ port=1234
<a name="Common-Aliases"></a>
<br></p>
<h2 id="common-terminal-aliases:d680e8a854a7cbad6d490c445cba2eba">Common Terminal Aliases</h2>
<h2 id="common-terminal-aliases">Common Terminal Aliases</h2>
<p>When you start your docker container, LaraDock will copy the <code>aliases.sh</code> file located in the <code>laradock/workspace</code> directory and add sourcing to the container <code>~/.bashrc</code> file.</p>
@ -1289,7 +1289,7 @@ port=1234
<p><br>
<a name="Install-Aerospike-Extension"></a></p>
<h2 id="install-aerospike-extension:d680e8a854a7cbad6d490c445cba2eba">Install Aerospike extension</h2>
<h2 id="install-aerospike-extension">Install Aerospike extension</h2>
<p>1 - First install <code>aerospike</code> in the Workspace and the PHP-FPM Containers:
<br>
@ -1324,7 +1324,7 @@ e) set it to <code>true</code></p>
<p><br>
<a name="Install-Laravel-Envoy"></a></p>
<h2 id="install-laravel-envoy-envoy-task-runner:d680e8a854a7cbad6d490c445cba2eba">Install Laravel Envoy (Envoy Task Runner)</h2>
<h2 id="install-laravel-envoy-envoy-task-runner">Install Laravel Envoy (Envoy Task Runner)</h2>
<p>1 - Open the <code>docker-compose.yml</code> file
<br>
@ -1345,21 +1345,21 @@ e) set it to <code>true</code></p>
<p>4 - Re-build the containers <code>docker-compose build workspace</code></p>
<h4 id="laravel-envoy-documentation-here-https-laravel-com-docs-5-3-envoy:d680e8a854a7cbad6d490c445cba2eba"><a href="https://laravel.com/docs/5.3/envoy">Laravel Envoy Documentation Here</a></h4>
<h4 id="laravel-envoy-documentation-here-https-laravel-com-docs-5-3-envoy"><a href="https://laravel.com/docs/5.3/envoy">Laravel Envoy Documentation Here</a></h4>
<p><br>
<a name="phpstorm-debugging"></a></p>
<h2 id="phpstorm-debugging-guide:d680e8a854a7cbad6d490c445cba2eba">PHPStorm Debugging Guide</h2>
<h2 id="phpstorm-debugging-guide">PHPStorm Debugging Guide</h2>
<p>Remote debug Laravel web and phpunit tests.</p>
<h4 id="debugging-guide-here-https-github-com-laradock-laradock-blob-master-guides-phpstorm-md:d680e8a854a7cbad6d490c445cba2eba"><a href="https://github.com/laradock/laradock/blob/master/_guides/phpstorm.md">Debugging Guide Here</a></h4>
<h4 id="debugging-guide-here-https-github-com-laradock-laradock-blob-master-guides-phpstorm-md"><a href="https://github.com/laradock/laradock/blob/master/_guides/phpstorm.md">Debugging Guide Here</a></h4>
<p><br>
<a name="keep-tracking-LaraDock"></a></p>
<h2 id="keep-track-of-your-laradock-changes:d680e8a854a7cbad6d490c445cba2eba">Keep track of your LaraDock changes</h2>
<h2 id="keep-track-of-your-laradock-changes">Keep track of your LaraDock changes</h2>
<ol>
<li>Fork the LaraDock repository.</li>
@ -1371,7 +1371,7 @@ e) set it to <code>true</code></p>
<p><br>
<a name="upgrading-laradock"></a></p>
<h2 id="upgrading-laradock:d680e8a854a7cbad6d490c445cba2eba">Upgrading LaraDock</h2>
<h2 id="upgrading-laradock">Upgrading LaraDock</h2>
<p>Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading LaraDock from v3.* to v4.*:</p>
@ -1384,12 +1384,12 @@ e) set it to <code>true</code></p>
<p><strong>Note:</strong> If you face any problem with the last step above: rebuild all your containers
<code>docker-compose build --no-cache</code>
&quot;Warning Containers Data might be lost!&quot;</p>
&ldquo;Warning Containers Data might be lost!&rdquo;</p>
<p><br>
<a name="Speed-MacOS"></a></p>
<h2 id="improve-speed-on-macos:d680e8a854a7cbad6d490c445cba2eba">Improve speed on MacOS</h2>
<h2 id="improve-speed-on-macos">Improve speed on MacOS</h2>
<p>Sharing code into Docker containers with osxfs have very poor performance compared to Linux. You can get around this issue by using NFS to share your files betwen your host and your container.</p>
@ -1424,7 +1424,7 @@ e) set it to <code>true</code></p>
<pre><code class="language-bash">~/d4m-nfs/d4m-nfs.sh
</code></pre>
<p>That's it! Run your containers.. Example:</p>
<p>That&rsquo;s it! Run your containers.. Example:</p>
<pre><code class="language-bash">docker-compose up -d nginx mysql
</code></pre>
@ -1434,13 +1434,13 @@ e) set it to <code>true</code></p>
<p><br>
<a name="Common-Problems"></a></p>
<h2 id="common-problems:d680e8a854a7cbad6d490c445cba2eba">Common Problems</h2>
<h2 id="common-problems">Common Problems</h2>
<p><em>Here's a list of the common problems you might face, and the possible solutions.</em></p>
<p><em>Here&rsquo;s a list of the common problems you might face, and the possible solutions.</em></p>
<p><br></p>
<h3 id="i-see-a-blank-white-page-instead-of-the-laravel-welcome-page:d680e8a854a7cbad6d490c445cba2eba">I see a blank (white) page instead of the Laravel 'Welcome' page!</h3>
<h3 id="i-see-a-blank-white-page-instead-of-the-laravel-welcome-page">I see a blank (white) page instead of the Laravel &lsquo;Welcome&rsquo; page!</h3>
<p>Run the following command from the Laravel root directory:</p>
@ -1449,19 +1449,19 @@ e) set it to <code>true</code></p>
<p><br></p>
<h3 id="i-see-welcome-to-nginx-instead-of-the-laravel-app:d680e8a854a7cbad6d490c445cba2eba">I see &quot;Welcome to nginx&quot; instead of the Laravel App!</h3>
<h3 id="i-see-welcome-to-nginx-instead-of-the-laravel-app">I see &ldquo;Welcome to nginx&rdquo; instead of the Laravel App!</h3>
<p>Use <code>http://127.0.0.1</code> instead of <code>http://localhost</code> in your browser.</p>
<p><br></p>
<h3 id="i-see-an-error-message-containing-address-already-in-use-or-port-is-already-allocated:d680e8a854a7cbad6d490c445cba2eba">I see an error message containing <code>address already in use</code> or <code>port is already allocated</code></h3>
<h3 id="i-see-an-error-message-containing-address-already-in-use-or-port-is-already-allocated">I see an error message containing <code>address already in use</code> or <code>port is already allocated</code></h3>
<p>Make sure the ports for the services that you are trying to run (22, 80, 443, 3306, etc.) are not being used already by other programs on the host, such as a built in <code>apache</code>/<code>httpd</code> service or other development tools you have installed.</p>
<p><br></p>
<h3 id="i-get-nginx-error-404-not-found-on-windows:d680e8a854a7cbad6d490c445cba2eba">I get NGINX error 404 Not Found on Windows.</h3>
<h3 id="i-get-nginx-error-404-not-found-on-windows">I get NGINX error 404 Not Found on Windows.</h3>
<ol>
<li>Go to docker Settings on your Windows machine.</li>
@ -1472,18 +1472,18 @@ e) set it to <code>true</code></p>
<p><br></p>
<h3 id="the-time-in-my-services-does-not-match-the-current-time:d680e8a854a7cbad6d490c445cba2eba">The time in my services does not match the current time</h3>
<h3 id="the-time-in-my-services-does-not-match-the-current-time">The time in my services does not match the current time</h3>
<ol>
<li>Make sure you've <a href="#Change-the-timezone">changed the timezone</a>.</li>
<li>Make sure you&rsquo;ve <a href="#Change-the-timezone">changed the timezone</a>.</li>
<li>Stop and rebuild the containers (<code>docker-compose up -d --build &lt;services&gt;</code>)</li>
</ol>
<p><br></p>
<h3 id="i-get-mysql-connection-refused:d680e8a854a7cbad6d490c445cba2eba">I get MySQL connection refused</h3>
<h3 id="i-get-mysql-connection-refused">I get MySQL connection refused</h3>
<p>This error sometimes happens because your Laravel application isn't running on the container localhost IP (Which is 127.0.0.1). Steps to fix it:</p>
<p>This error sometimes happens because your Laravel application isn&rsquo;t running on the container localhost IP (Which is 127.0.0.1). Steps to fix it:</p>
<ul>
<li>Option A
@ -1514,7 +1514,7 @@ e) set it to <code>true</code></p>
<nav class="pagination" aria-label="Footer">
<div class="previous">
<a href="http://laradock.io/getting-started/" title="Getting started">
<a href="http://laradock.io/getting-started/" title="Getting Started">
<span class="direction">
Previous
</span>
@ -1524,7 +1524,7 @@ e) set it to <code>true</code></p>
</div>
<div class="stretch">
<div class="title">
Getting started
Getting Started
</div>
</div>
</div>

162
docs/documentation/index.xml
View File

@ -20,7 +20,7 @@
&lt;p&gt;&lt;a name=&#34;List-current-running-Containers&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;list-current-running-containers:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;List current running Containers&lt;/h2&gt;
&lt;h2 id=&#34;list-current-running-containers&#34;&gt;List current running Containers&lt;/h2&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker ps
&lt;/code&gt;&lt;/pre&gt;
@ -33,7 +33,7 @@
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Close-all-running-Containers&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;close-all-running-containers:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Close all running Containers&lt;/h2&gt;
&lt;h2 id=&#34;close-all-running-containers&#34;&gt;Close all running Containers&lt;/h2&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose stop
&lt;/code&gt;&lt;/pre&gt;
@ -46,7 +46,7 @@
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Delete-all-existing-Containers&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;delete-all-existing-containers:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Delete all existing Containers&lt;/h2&gt;
&lt;h2 id=&#34;delete-all-existing-containers&#34;&gt;Delete all existing Containers&lt;/h2&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose down
&lt;/code&gt;&lt;/pre&gt;
@ -54,7 +54,7 @@
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Enter-Container&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;enter-a-container-run-commands-in-a-running-container:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Enter a Container (run commands in a running Container)&lt;/h2&gt;
&lt;h2 id=&#34;enter-a-container-run-commands-in-a-running-container&#34;&gt;Enter a Container (run commands in a running Container)&lt;/h2&gt;
&lt;p&gt;1 - First list the current running containers with &lt;code&gt;docker ps&lt;/code&gt;&lt;/p&gt;
@ -78,7 +78,7 @@
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Edit-Container&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;edit-default-container-configuration:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Edit default container configuration&lt;/h2&gt;
&lt;h2 id=&#34;edit-default-container-configuration&#34;&gt;Edit default container configuration&lt;/h2&gt;
&lt;p&gt;Open the &lt;code&gt;docker-compose.yml&lt;/code&gt; and change anything you want.&lt;/p&gt;
@ -101,7 +101,7 @@
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Edit-a-Docker-Image&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;edit-a-docker-image:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Edit a Docker Image&lt;/h2&gt;
&lt;h2 id=&#34;edit-a-docker-image&#34;&gt;Edit a Docker Image&lt;/h2&gt;
&lt;p&gt;1 - Find the &lt;code&gt;Dockerfile&lt;/code&gt; of the image you want to edit,
&lt;br&gt;
@ -119,7 +119,7 @@ example for &lt;code&gt;mysql&lt;/code&gt; it will be &lt;code&gt;mysql/Dockerfi
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Build-Re-build-Containers&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;build-re-build-containers:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Build/Re-build Containers&lt;/h2&gt;
&lt;h2 id=&#34;build-re-build-containers&#34;&gt;Build/Re-build Containers&lt;/h2&gt;
&lt;p&gt;If you do any change to any &lt;code&gt;Dockerfile&lt;/code&gt; make sure you run this command, for the changes to take effect:&lt;/p&gt;
@ -136,18 +136,18 @@ example for &lt;code&gt;mysql&lt;/code&gt; it will be &lt;code&gt;mysql/Dockerfi
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Add-Docker-Images&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;add-more-software-docker-images:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Add more Software (Docker Images)&lt;/h2&gt;
&lt;h2 id=&#34;add-more-software-docker-images&#34;&gt;Add more Software (Docker Images)&lt;/h2&gt;
&lt;p&gt;To add an image (software), just edit the &lt;code&gt;docker-compose.yml&lt;/code&gt; and add your container details, to do so you need to be familiar with the &lt;a href=&#34;https://docs.docker.com/compose/compose-file/&#34;&gt;docker compose file syntax&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;View-the-Log-files&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;view-the-log-files:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;View the Log files&lt;/h2&gt;
&lt;h2 id=&#34;view-the-log-files&#34;&gt;View the Log files&lt;/h2&gt;
&lt;p&gt;The NGINX Log file is stored in the &lt;code&gt;logs/nginx&lt;/code&gt; directory.&lt;/p&gt;
&lt;p&gt;However to view the logs of all the other containers (MySQL, PHP-FPM,...) you can run this:&lt;/p&gt;
&lt;p&gt;However to view the logs of all the other containers (MySQL, PHP-FPM,&amp;hellip;) you can run this:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker logs {container-name}
&lt;/code&gt;&lt;/pre&gt;
@ -157,7 +157,7 @@ example for &lt;code&gt;mysql&lt;/code&gt; it will be &lt;code&gt;mysql/Dockerfi
&lt;p&gt;&lt;a name=&#34;Install-PHP-Extensions&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-php-extensions:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install PHP Extensions&lt;/h2&gt;
&lt;h2 id=&#34;install-php-extensions&#34;&gt;Install PHP Extensions&lt;/h2&gt;
&lt;p&gt;Before installing PHP extensions, you have to decide whether you need for the &lt;code&gt;FPM&lt;/code&gt; or &lt;code&gt;CLI&lt;/code&gt; because each lives on a different container, if you need it for both you have to edit both containers.&lt;/p&gt;
@ -168,15 +168,15 @@ The PHP-CLI extensions should be installed in &lt;code&gt;workspace/Dockerfile&l
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Change-the-PHP-FPM-Version&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;change-the-php-fpm-version:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Change the (PHP-FPM) Version&lt;/h2&gt;
&lt;h2 id=&#34;change-the-php-fpm-version&#34;&gt;Change the (PHP-FPM) Version&lt;/h2&gt;
&lt;p&gt;By default &lt;strong&gt;PHP-FPM 7.0&lt;/strong&gt; is running.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The PHP-FPM is responsible of serving your application code, you don&#39;t have to change the PHP-CLI version if you are planning to run your application on different PHP-FPM version.&lt;/p&gt;
&lt;p&gt;The PHP-FPM is responsible of serving your application code, you don&amp;rsquo;t have to change the PHP-CLI version if you are planning to run your application on different PHP-FPM version.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;a-switch-from-php-7-0-to-php-5-6:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;A) Switch from PHP &lt;code&gt;7.0&lt;/code&gt; to PHP &lt;code&gt;5.6&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id=&#34;a-switch-from-php-7-0-to-php-5-6&#34;&gt;A) Switch from PHP &lt;code&gt;7.0&lt;/code&gt; to PHP &lt;code&gt;5.6&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;1 - Open the &lt;code&gt;docker-compose.yml&lt;/code&gt;.&lt;/p&gt;
@ -200,7 +200,7 @@ The PHP-CLI extensions should be installed in &lt;code&gt;workspace/Dockerfile&l
&lt;p&gt;For more details about the PHP base image, visit the &lt;a href=&#34;https://hub.docker.com/_/php/&#34;&gt;official PHP docker images&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&#34;b-switch-from-php-7-0-or-5-6-to-php-5-5:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;B) Switch from PHP &lt;code&gt;7.0&lt;/code&gt; or &lt;code&gt;5.6&lt;/code&gt; to PHP &lt;code&gt;5.5&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id=&#34;b-switch-from-php-7-0-or-5-6-to-php-5-5&#34;&gt;B) Switch from PHP &lt;code&gt;7.0&lt;/code&gt; or &lt;code&gt;5.6&lt;/code&gt; to PHP &lt;code&gt;5.5&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;We do not natively support PHP 5.5 anymore, but you can get it in few steps:&lt;/p&gt;
@ -219,22 +219,22 @@ The PHP-CLI extensions should be installed in &lt;code&gt;workspace/Dockerfile&l
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Change-the-PHP-CLI-Version&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;change-the-php-cli-version:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Change the PHP-CLI Version&lt;/h2&gt;
&lt;h2 id=&#34;change-the-php-cli-version&#34;&gt;Change the PHP-CLI Version&lt;/h2&gt;
&lt;p&gt;By default &lt;strong&gt;PHP-CLI 7.0&lt;/strong&gt; is running.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Note: it&#39;s not very essential to edit the PHP-CLI version. The PHP-CLI is only used for the Artisan Commands &amp;amp; Composer. It doesn&#39;t serve your Application code, this is the PHP-FPM job.&lt;/p&gt;
&lt;p&gt;Note: it&amp;rsquo;s not very essential to edit the PHP-CLI version. The PHP-CLI is only used for the Artisan Commands &amp;amp; Composer. It doesn&amp;rsquo;t serve your Application code, this is the PHP-FPM job.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The PHP-CLI is installed in the Workspace container. To change the PHP-CLI version you need to edit the &lt;code&gt;workspace/Dockerfile&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Right now you have to manually edit the &lt;code&gt;Dockerfile&lt;/code&gt; or create a new one like it&#39;s done for the PHP-FPM. (consider contributing).&lt;/p&gt;
&lt;p&gt;Right now you have to manually edit the &lt;code&gt;Dockerfile&lt;/code&gt; or create a new one like it&amp;rsquo;s done for the PHP-FPM. (consider contributing).&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-xDebug&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-xdebug:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install xDebug&lt;/h2&gt;
&lt;h2 id=&#34;install-xdebug&#34;&gt;Install xDebug&lt;/h2&gt;
&lt;p&gt;1 - First install &lt;code&gt;xDebug&lt;/code&gt; in the Workspace and the PHP-FPM Containers:
&lt;br&gt;
@ -278,7 +278,7 @@ xdebug.remote_connect_back=1
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Control-xDebug&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;start-stop-xdebug:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Start/Stop xDebug:&lt;/h2&gt;
&lt;h2 id=&#34;start-stop-xdebug&#34;&gt;Start/Stop xDebug:&lt;/h2&gt;
&lt;p&gt;By installing xDebug, you are enabling it to run on startup by default.&lt;/p&gt;
@ -290,12 +290,12 @@ xdebug.remote_connect_back=1
&lt;li&gt;See the status: &lt;code&gt;./xdebugPhpFpm status&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Note: If &lt;code&gt;./xdebugPhpFpm&lt;/code&gt; doesn&#39;t execute and gives &lt;code&gt;Permission Denied&lt;/code&gt; error the problem can be that file &lt;code&gt;xdebugPhpFpm&lt;/code&gt; doesn&#39;t have execution access. This can be fixed by running &lt;code&gt;chmod&lt;/code&gt; command with desired access permissions.&lt;/p&gt;
&lt;p&gt;Note: If &lt;code&gt;./xdebugPhpFpm&lt;/code&gt; doesn&amp;rsquo;t execute and gives &lt;code&gt;Permission Denied&lt;/code&gt; error the problem can be that file &lt;code&gt;xdebugPhpFpm&lt;/code&gt; doesn&amp;rsquo;t have execution access. This can be fixed by running &lt;code&gt;chmod&lt;/code&gt; command with desired access permissions.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Deployer&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-deployer-deployment-tool-for-php:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Deployer (Deployment tool for PHP)&lt;/h2&gt;
&lt;h2 id=&#34;install-deployer-deployment-tool-for-php&#34;&gt;Install Deployer (Deployment tool for PHP)&lt;/h2&gt;
&lt;p&gt;1 - Open the &lt;code&gt;docker-compose.yml&lt;/code&gt; file
&lt;br&gt;
@ -316,7 +316,7 @@ xdebug.remote_connect_back=1
&lt;p&gt;4 - Re-build the containers &lt;code&gt;docker-compose build workspace&lt;/code&gt;&lt;/p&gt;
&lt;h4 id=&#34;deployer-documentation-here-https-deployer-org-docs:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;&lt;a href=&#34;https://deployer.org/docs&#34;&gt;Deployer Documentation Here&lt;/a&gt;&lt;/h4&gt;
&lt;h4 id=&#34;deployer-documentation-here-https-deployer-org-docs&#34;&gt;&lt;a href=&#34;https://deployer.org/docs&#34;&gt;Deployer Documentation Here&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Production&#34;&gt;&lt;/a&gt;&lt;/p&gt;
@ -324,11 +324,11 @@ xdebug.remote_connect_back=1
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;LaraDock-for-Production&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;prepare-laradock-for-production:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Prepare LaraDock for Production&lt;/h2&gt;
&lt;h2 id=&#34;prepare-laradock-for-production&#34;&gt;Prepare LaraDock for Production&lt;/h2&gt;
&lt;p&gt;It&#39;s recommended for production to create a custom &lt;code&gt;docker-compose.yml&lt;/code&gt; file. For that reason, LaraDock is shipped with &lt;code&gt;production-docker-compose.yml&lt;/code&gt; which should contain only the containers you are planning to run on production (usage example: &lt;code&gt;docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s recommended for production to create a custom &lt;code&gt;docker-compose.yml&lt;/code&gt; file. For that reason, LaraDock is shipped with &lt;code&gt;production-docker-compose.yml&lt;/code&gt; which should contain only the containers you are planning to run on production (usage example: &lt;code&gt;docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;Note: The Database (MySQL/MariaDB/...) ports should not be forwarded on production, because Docker will automatically publish the port on the host, which is quite insecure, unless specifically told not to. So make sure to remove these lines:&lt;/p&gt;
&lt;p&gt;Note: The Database (MySQL/MariaDB/&amp;hellip;) ports should not be forwarded on production, because Docker will automatically publish the port on the host, which is quite insecure, unless specifically told not to. So make sure to remove these lines:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ports:
- &amp;quot;3306:3306&amp;quot;
@ -339,16 +339,16 @@ xdebug.remote_connect_back=1
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Digital-Ocean&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;setup-laravel-and-docker-on-digital-ocean:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Setup Laravel and Docker on Digital Ocean&lt;/h2&gt;
&lt;h2 id=&#34;setup-laravel-and-docker-on-digital-ocean&#34;&gt;Setup Laravel and Docker on Digital Ocean&lt;/h2&gt;
&lt;h3 id=&#34;full-guide-here-https-github-com-laradock-laradock-blob-master-guides-digital-ocean-md:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;&lt;a href=&#34;https://github.com/laradock/laradock/blob/master/_guides/digital_ocean.md&#34;&gt;Full Guide Here&lt;/a&gt;&lt;/h3&gt;
&lt;h3 id=&#34;full-guide-here-https-github-com-laradock-laradock-blob-master-guides-digital-ocean-md&#34;&gt;&lt;a href=&#34;https://github.com/laradock/laradock/blob/master/_guides/digital_ocean.md&#34;&gt;Full Guide Here&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Laravel&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;Install-Laravel&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-laravel-from-a-docker-container:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Laravel from a Docker Container&lt;/h2&gt;
&lt;h2 id=&#34;install-laravel-from-a-docker-container&#34;&gt;Install Laravel from a Docker Container&lt;/h2&gt;
&lt;p&gt;1 - First you need to enter the Workspace Container.&lt;/p&gt;
@ -388,7 +388,7 @@ xdebug.remote_connect_back=1
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Run-Artisan-Commands&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;run-artisan-commands:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Run Artisan Commands&lt;/h2&gt;
&lt;h2 id=&#34;run-artisan-commands&#34;&gt;Run Artisan Commands&lt;/h2&gt;
&lt;p&gt;You can run artisan commands and many other Terminal commands from the Workspace container.&lt;/p&gt;
@ -407,7 +407,7 @@ xdebug.remote_connect_back=1
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose exec workspace bash
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Add &lt;code&gt;--user=laradock&lt;/code&gt; (example &lt;code&gt;docker-compose exec --user=laradock workspace bash&lt;/code&gt;) to have files created as your host&#39;s user.&lt;/p&gt;
&lt;p&gt;Add &lt;code&gt;--user=laradock&lt;/code&gt; (example &lt;code&gt;docker-compose exec --user=laradock workspace bash&lt;/code&gt;) to have files created as your host&amp;rsquo;s user.&lt;/p&gt;
&lt;p&gt;4 - Run anything you want :)&lt;/p&gt;
@ -423,7 +423,7 @@ xdebug.remote_connect_back=1
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Run-Laravel-Queue-Worker&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;run-laravel-queue-worker:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Run Laravel Queue Worker&lt;/h2&gt;
&lt;h2 id=&#34;run-laravel-queue-worker&#34;&gt;Run Laravel Queue Worker&lt;/h2&gt;
&lt;p&gt;1 - First add &lt;code&gt;php-worker&lt;/code&gt; container. It will be similar as like PHP-FPM Container.
&lt;br&gt;
@ -448,19 +448,19 @@ b) add a new service container by simply copy-paste this section below PHP-FPM c
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-Redis&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-redis:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use Redis&lt;/h2&gt;
&lt;h2 id=&#34;use-redis&#34;&gt;Use Redis&lt;/h2&gt;
&lt;p&gt;1 - First make sure you run the Redis Container (&lt;code&gt;redis&lt;/code&gt;) with the &lt;code&gt;docker-compose up&lt;/code&gt; command.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose up -d redis
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;2 - Open your Laravel&#39;s &lt;code&gt;.env&lt;/code&gt; file and set the &lt;code&gt;REDIS_HOST&lt;/code&gt; to &lt;code&gt;redis&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;2 - Open your Laravel&amp;rsquo;s &lt;code&gt;.env&lt;/code&gt; file and set the &lt;code&gt;REDIS_HOST&lt;/code&gt; to &lt;code&gt;redis&lt;/code&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-env&#34;&gt;REDIS_HOST=redis
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;If you don&#39;t find the &lt;code&gt;REDIS_HOST&lt;/code&gt; variable in your &lt;code&gt;.env&lt;/code&gt; file. Go to the database configuration file &lt;code&gt;config/database.php&lt;/code&gt; and replace the default &lt;code&gt;127.0.0.1&lt;/code&gt; IP with &lt;code&gt;redis&lt;/code&gt; for Redis like this:&lt;/p&gt;
&lt;p&gt;If you don&amp;rsquo;t find the &lt;code&gt;REDIS_HOST&lt;/code&gt; variable in your &lt;code&gt;.env&lt;/code&gt; file. Go to the database configuration file &lt;code&gt;config/database.php&lt;/code&gt; and replace the default &lt;code&gt;127.0.0.1&lt;/code&gt; IP with &lt;code&gt;redis&lt;/code&gt; for Redis like this:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-php&#34;&gt;&#39;redis&#39; =&amp;gt; [
&#39;cluster&#39; =&amp;gt; false,
@ -491,7 +491,7 @@ SESSION_DRIVER=redis
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-Mongo&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-mongo:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use Mongo&lt;/h2&gt;
&lt;h2 id=&#34;use-mongo&#34;&gt;Use Mongo&lt;/h2&gt;
&lt;p&gt;1 - First install &lt;code&gt;mongo&lt;/code&gt; in the Workspace and the PHP-FPM Containers:
&lt;br&gt;
@ -549,7 +549,7 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
],
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;5 - Open your Laravel&#39;s &lt;code&gt;.env&lt;/code&gt; file and update the following variables:&lt;/p&gt;
&lt;p&gt;5 - Open your Laravel&amp;rsquo;s &lt;code&gt;.env&lt;/code&gt; file and update the following variables:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;set the &lt;code&gt;DB_HOST&lt;/code&gt; to your &lt;code&gt;mongo&lt;/code&gt;.&lt;/li&gt;
@ -575,7 +575,7 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-phpMyAdmin&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-phpmyadmin:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use PhpMyAdmin&lt;/h2&gt;
&lt;h2 id=&#34;use-phpmyadmin&#34;&gt;Use PhpMyAdmin&lt;/h2&gt;
&lt;p&gt;1 - Run the phpMyAdmin Container (&lt;code&gt;phpmyadmin&lt;/code&gt;) with the &lt;code&gt;docker-compose up&lt;/code&gt; command. Example:&lt;/p&gt;
@ -591,7 +591,7 @@ docker-compose up -d mariadb phpmyadmin
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-pgAdmin&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-pgadmin:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use PgAdmin&lt;/h2&gt;
&lt;h2 id=&#34;use-pgadmin&#34;&gt;Use PgAdmin&lt;/h2&gt;
&lt;p&gt;1 - Run the pgAdmin Container (&lt;code&gt;pgadmin&lt;/code&gt;) with the &lt;code&gt;docker-compose up&lt;/code&gt; command. Example:&lt;/p&gt;
@ -603,7 +603,7 @@ docker-compose up -d mariadb phpmyadmin
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-Beanstalkd&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-beanstalkd:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use Beanstalkd&lt;/h2&gt;
&lt;h2 id=&#34;use-beanstalkd&#34;&gt;Use Beanstalkd&lt;/h2&gt;
&lt;p&gt;1 - Run the Beanstalkd Container:&lt;/p&gt;
@ -640,7 +640,7 @@ b. set the queue host to beanstalkd : &lt;code&gt;QUEUE_HOST=beanstalkd&lt;/code
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-ElasticSearch&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-elasticsearch:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use ElasticSearch&lt;/h2&gt;
&lt;h2 id=&#34;use-elasticsearch&#34;&gt;Use ElasticSearch&lt;/h2&gt;
&lt;p&gt;1 - Run the ElasticSearch Container (&lt;code&gt;elasticsearch&lt;/code&gt;) with the &lt;code&gt;docker-compose up&lt;/code&gt; command:&lt;/p&gt;
@ -649,7 +649,7 @@ b. set the queue host to beanstalkd : &lt;code&gt;QUEUE_HOST=beanstalkd&lt;/code
&lt;p&gt;2 - Open your browser and visit the localhost on port &lt;strong&gt;9200&lt;/strong&gt;: &lt;code&gt;http://localhost:9200&lt;/code&gt;&lt;/p&gt;
&lt;h3 id=&#34;install-elasticsearch-plugin:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install ElasticSearch Plugin&lt;/h3&gt;
&lt;h3 id=&#34;install-elasticsearch-plugin&#34;&gt;Install ElasticSearch Plugin&lt;/h3&gt;
&lt;p&gt;1 - Install the ElasticSearch plugin like &lt;a href=&#34;https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugins-delete-by-query.html&#34;&gt;delete-by-query&lt;/a&gt;.&lt;/p&gt;
@ -664,7 +664,7 @@ b. set the queue host to beanstalkd : &lt;code&gt;QUEUE_HOST=beanstalkd&lt;/code
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-Selenium&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-selenium:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use Selenium&lt;/h2&gt;
&lt;h2 id=&#34;use-selenium&#34;&gt;Use Selenium&lt;/h2&gt;
&lt;p&gt;1 - Run the Selenium Container (&lt;code&gt;selenium&lt;/code&gt;) with the &lt;code&gt;docker-compose up&lt;/code&gt; command. Example:&lt;/p&gt;
@ -676,7 +676,7 @@ b. set the queue host to beanstalkd : &lt;code&gt;QUEUE_HOST=beanstalkd&lt;/code
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-RethinkDB&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-rethinkdb:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use RethinkDB&lt;/h2&gt;
&lt;h2 id=&#34;use-rethinkdb&#34;&gt;Use RethinkDB&lt;/h2&gt;
&lt;p&gt;The RethinkDB is an open-source Database for Real-time Web (&lt;a href=&#34;https://rethinkdb.com/&#34;&gt;RethinkDB&lt;/a&gt;).
A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;Laravel RethinkDB&lt;/a&gt;) is being developed and was released a version for Laravel 5.2 (experimental).&lt;/p&gt;
@ -705,7 +705,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
],
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;4 - Open your Laravel&#39;s &lt;code&gt;.env&lt;/code&gt; file and update the following variables:&lt;/p&gt;
&lt;p&gt;4 - Open your Laravel&amp;rsquo;s &lt;code&gt;.env&lt;/code&gt; file and update the following variables:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;set the &lt;code&gt;DB_CONNECTION&lt;/code&gt; to your &lt;code&gt;rethinkdb&lt;/code&gt;.&lt;/li&gt;
@ -720,7 +720,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-CodeIgniter&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-codeigniter:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install CodeIgniter&lt;/h2&gt;
&lt;h2 id=&#34;install-codeigniter&#34;&gt;Install CodeIgniter&lt;/h2&gt;
&lt;p&gt;To install CodeIgniter 3 on LaraDock all you have to do is the following simple steps:&lt;/p&gt;
@ -733,12 +733,12 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Misc&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;miscellaneous:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Miscellaneous&lt;/h2&gt;
&lt;h2 id=&#34;miscellaneous&#34;&gt;Miscellaneous&lt;/h2&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Change-the-timezone&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;change-the-timezone:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Change the timezone&lt;/h2&gt;
&lt;h2 id=&#34;change-the-timezone&#34;&gt;Change the timezone&lt;/h2&gt;
&lt;p&gt;To change the timezone for the &lt;code&gt;workspace&lt;/code&gt; container, modify the &lt;code&gt;TZ&lt;/code&gt; build argument in the Docker Compose file to one in the &lt;a href=&#34;https://en.wikipedia.org/wiki/List_of_tz_database_time_zones&#34;&gt;TZ database&lt;/a&gt;.&lt;/p&gt;
@ -757,7 +757,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;CronJobs&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;adding-cron-jobs:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Adding cron jobs&lt;/h2&gt;
&lt;h2 id=&#34;adding-cron-jobs&#34;&gt;Adding cron jobs&lt;/h2&gt;
&lt;p&gt;You can add your cron jobs to &lt;code&gt;workspace/crontab/root&lt;/code&gt; after the &lt;code&gt;php artisan&lt;/code&gt; line.&lt;/p&gt;
@ -767,12 +767,12 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
* * * * * root echo &amp;quot;Every Minute&amp;quot; &amp;gt; /var/log/cron.log 2&amp;gt;&amp;amp;1
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Make sure you &lt;a href=&#34;#Change-the-timezone&#34;&gt;change the timezone&lt;/a&gt; if you don&#39;t want to use the default (UTC).&lt;/p&gt;
&lt;p&gt;Make sure you &lt;a href=&#34;#Change-the-timezone&#34;&gt;change the timezone&lt;/a&gt; if you don&amp;rsquo;t want to use the default (UTC).&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Workspace-ssh&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;access-workspace-via-ssh:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Access workspace via ssh&lt;/h2&gt;
&lt;h2 id=&#34;access-workspace-via-ssh&#34;&gt;Access workspace via ssh&lt;/h2&gt;
&lt;p&gt;You can access the &lt;code&gt;workspace&lt;/code&gt; container through &lt;code&gt;localhost:2222&lt;/code&gt; by setting the &lt;code&gt;INSTALL_WORKSPACE_SSH&lt;/code&gt; build argument to &lt;code&gt;true&lt;/code&gt;.&lt;/p&gt;
@ -787,7 +787,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;MySQL-access-from-host&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;mysql-access-from-host:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;MySQL access from host&lt;/h2&gt;
&lt;h2 id=&#34;mysql-access-from-host&#34;&gt;MySQL access from host&lt;/h2&gt;
&lt;p&gt;You can forward the MySQL/MariaDB port to your host by making sure these lines are added to the &lt;code&gt;mysql&lt;/code&gt; or &lt;code&gt;mariadb&lt;/code&gt; section of the &lt;code&gt;docker-compose.yml&lt;/code&gt; or in your &lt;a href=&#34;https://docs.docker.com/compose/extends/&#34;&gt;environment specific Compose&lt;/a&gt; file.&lt;/p&gt;
@ -798,7 +798,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;MySQL-root-access&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;mysql-root-access:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;MySQL root access&lt;/h2&gt;
&lt;h2 id=&#34;mysql-root-access&#34;&gt;MySQL root access&lt;/h2&gt;
&lt;p&gt;The default username and password for the root MySQL user are &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;root&lt;/code&gt;.&lt;/p&gt;
@ -813,7 +813,7 @@ A package (&lt;a href=&#34;https://github.com/duxet/laravel-rethinkdb&#34;&gt;La
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Change-MySQL-port&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;change-mysql-port:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Change MySQL port&lt;/h2&gt;
&lt;h2 id=&#34;change-mysql-port&#34;&gt;Change MySQL port&lt;/h2&gt;
&lt;p&gt;Modify the &lt;code&gt;mysql/my.cnf&lt;/code&gt; file to set your port number, &lt;code&gt;1234&lt;/code&gt; is used as an example.&lt;/p&gt;
@ -826,7 +826,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Use-custom-Domain&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;use-custom-domain-instead-of-the-docker-ip:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Use custom Domain (instead of the Docker IP)&lt;/h2&gt;
&lt;h2 id=&#34;use-custom-domain-instead-of-the-docker-ip&#34;&gt;Use custom Domain (instead of the Docker IP)&lt;/h2&gt;
&lt;p&gt;Assuming your custom domain is &lt;code&gt;laravel.dev&lt;/code&gt;&lt;/p&gt;
@ -845,7 +845,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Enable-Global-Composer-Build-Install&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;enable-global-composer-build-install:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Enable Global Composer Build Install&lt;/h2&gt;
&lt;h2 id=&#34;enable-global-composer-build-install&#34;&gt;Enable Global Composer Build Install&lt;/h2&gt;
&lt;p&gt;Enabling Global Composer Install during the build for the container allows you to get your composer requirements installed and available in the container after the build is done.&lt;/p&gt;
@ -870,7 +870,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Prestissimo&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-prestissimo:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Prestissimo&lt;/h2&gt;
&lt;h2 id=&#34;install-prestissimo&#34;&gt;Install Prestissimo&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/hirak/prestissimo&#34;&gt;Prestissimo&lt;/a&gt; is a plugin for composer which enables parallel install functionality.&lt;/p&gt;
@ -889,7 +889,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Node&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-node-nvm:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Node + NVM&lt;/h2&gt;
&lt;h2 id=&#34;install-node-nvm&#34;&gt;Install Node + NVM&lt;/h2&gt;
&lt;p&gt;To install NVM and NodeJS in the Workspace container&lt;/p&gt;
@ -912,7 +912,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Yarn&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-node-yarn:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Node + YARN&lt;/h2&gt;
&lt;h2 id=&#34;install-node-yarn&#34;&gt;Install Node + YARN&lt;/h2&gt;
&lt;p&gt;Yarn is a new package manager for JavaScript. It is so faster than npm, which you can find &lt;a href=&#34;http://yarnpkg.com/en/compare&#34;&gt;here&lt;/a&gt;.To install NodeJS and &lt;a href=&#34;https://yarnpkg.com/&#34;&gt;Yarn&lt;/a&gt; in the Workspace container:&lt;/p&gt;
@ -936,7 +936,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Linuxbrew&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-linuxbrew:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Linuxbrew&lt;/h2&gt;
&lt;h2 id=&#34;install-linuxbrew&#34;&gt;Install Linuxbrew&lt;/h2&gt;
&lt;p&gt;Linuxbrew is a package manager for Linux. It is the Linux version of MacOS Homebrew and can be found &lt;a href=&#34;http://linuxbrew.sh&#34;&gt;here&lt;/a&gt;. To install Linuxbrew in the Workspace container:&lt;/p&gt;
@ -960,7 +960,7 @@ port=1234
&lt;a name=&#34;Common-Aliases&#34;&gt;&lt;/a&gt;
&lt;br&gt;&lt;/p&gt;
&lt;h2 id=&#34;common-terminal-aliases:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Common Terminal Aliases&lt;/h2&gt;
&lt;h2 id=&#34;common-terminal-aliases&#34;&gt;Common Terminal Aliases&lt;/h2&gt;
&lt;p&gt;When you start your docker container, LaraDock will copy the &lt;code&gt;aliases.sh&lt;/code&gt; file located in the &lt;code&gt;laradock/workspace&lt;/code&gt; directory and add sourcing to the container &lt;code&gt;~/.bashrc&lt;/code&gt; file.&lt;/p&gt;
@ -969,7 +969,7 @@ port=1234
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Aerospike-Extension&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-aerospike-extension:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Aerospike extension&lt;/h2&gt;
&lt;h2 id=&#34;install-aerospike-extension&#34;&gt;Install Aerospike extension&lt;/h2&gt;
&lt;p&gt;1 - First install &lt;code&gt;aerospike&lt;/code&gt; in the Workspace and the PHP-FPM Containers:
&lt;br&gt;
@ -1004,7 +1004,7 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Install-Laravel-Envoy&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;install-laravel-envoy-envoy-task-runner:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Install Laravel Envoy (Envoy Task Runner)&lt;/h2&gt;
&lt;h2 id=&#34;install-laravel-envoy-envoy-task-runner&#34;&gt;Install Laravel Envoy (Envoy Task Runner)&lt;/h2&gt;
&lt;p&gt;1 - Open the &lt;code&gt;docker-compose.yml&lt;/code&gt; file
&lt;br&gt;
@ -1025,21 +1025,21 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;4 - Re-build the containers &lt;code&gt;docker-compose build workspace&lt;/code&gt;&lt;/p&gt;
&lt;h4 id=&#34;laravel-envoy-documentation-here-https-laravel-com-docs-5-3-envoy:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;&lt;a href=&#34;https://laravel.com/docs/5.3/envoy&#34;&gt;Laravel Envoy Documentation Here&lt;/a&gt;&lt;/h4&gt;
&lt;h4 id=&#34;laravel-envoy-documentation-here-https-laravel-com-docs-5-3-envoy&#34;&gt;&lt;a href=&#34;https://laravel.com/docs/5.3/envoy&#34;&gt;Laravel Envoy Documentation Here&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;phpstorm-debugging&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;phpstorm-debugging-guide:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;PHPStorm Debugging Guide&lt;/h2&gt;
&lt;h2 id=&#34;phpstorm-debugging-guide&#34;&gt;PHPStorm Debugging Guide&lt;/h2&gt;
&lt;p&gt;Remote debug Laravel web and phpunit tests.&lt;/p&gt;
&lt;h4 id=&#34;debugging-guide-here-https-github-com-laradock-laradock-blob-master-guides-phpstorm-md:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;&lt;a href=&#34;https://github.com/laradock/laradock/blob/master/_guides/phpstorm.md&#34;&gt;Debugging Guide Here&lt;/a&gt;&lt;/h4&gt;
&lt;h4 id=&#34;debugging-guide-here-https-github-com-laradock-laradock-blob-master-guides-phpstorm-md&#34;&gt;&lt;a href=&#34;https://github.com/laradock/laradock/blob/master/_guides/phpstorm.md&#34;&gt;Debugging Guide Here&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;keep-tracking-LaraDock&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;keep-track-of-your-laradock-changes:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Keep track of your LaraDock changes&lt;/h2&gt;
&lt;h2 id=&#34;keep-track-of-your-laradock-changes&#34;&gt;Keep track of your LaraDock changes&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Fork the LaraDock repository.&lt;/li&gt;
@ -1051,7 +1051,7 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;upgrading-laradock&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;upgrading-laradock:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Upgrading LaraDock&lt;/h2&gt;
&lt;h2 id=&#34;upgrading-laradock&#34;&gt;Upgrading LaraDock&lt;/h2&gt;
&lt;p&gt;Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading LaraDock from v3.* to v4.*:&lt;/p&gt;
@ -1064,12 +1064,12 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; If you face any problem with the last step above: rebuild all your containers
&lt;code&gt;docker-compose build --no-cache&lt;/code&gt;
&amp;quot;Warning Containers Data might be lost!&amp;quot;&lt;/p&gt;
&amp;ldquo;Warning Containers Data might be lost!&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Speed-MacOS&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;improve-speed-on-macos:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Improve speed on MacOS&lt;/h2&gt;
&lt;h2 id=&#34;improve-speed-on-macos&#34;&gt;Improve speed on MacOS&lt;/h2&gt;
&lt;p&gt;Sharing code into Docker containers with osxfs have very poor performance compared to Linux. You can get around this issue by using NFS to share your files betwen your host and your container.&lt;/p&gt;
@ -1104,7 +1104,7 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;~/d4m-nfs/d4m-nfs.sh
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;That&#39;s it! Run your containers.. Example:&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s it! Run your containers.. Example:&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose up -d nginx mysql
&lt;/code&gt;&lt;/pre&gt;
@ -1114,13 +1114,13 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
&lt;a name=&#34;Common-Problems&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;common-problems:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Common Problems&lt;/h2&gt;
&lt;h2 id=&#34;common-problems&#34;&gt;Common Problems&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Here&#39;s a list of the common problems you might face, and the possible solutions.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Here&amp;rsquo;s a list of the common problems you might face, and the possible solutions.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;i-see-a-blank-white-page-instead-of-the-laravel-welcome-page:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;I see a blank (white) page instead of the Laravel &#39;Welcome&#39; page!&lt;/h3&gt;
&lt;h3 id=&#34;i-see-a-blank-white-page-instead-of-the-laravel-welcome-page&#34;&gt;I see a blank (white) page instead of the Laravel &amp;lsquo;Welcome&amp;rsquo; page!&lt;/h3&gt;
&lt;p&gt;Run the following command from the Laravel root directory:&lt;/p&gt;
@ -1129,19 +1129,19 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;i-see-welcome-to-nginx-instead-of-the-laravel-app:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;I see &amp;quot;Welcome to nginx&amp;quot; instead of the Laravel App!&lt;/h3&gt;
&lt;h3 id=&#34;i-see-welcome-to-nginx-instead-of-the-laravel-app&#34;&gt;I see &amp;ldquo;Welcome to nginx&amp;rdquo; instead of the Laravel App!&lt;/h3&gt;
&lt;p&gt;Use &lt;code&gt;http://127.0.0.1&lt;/code&gt; instead of &lt;code&gt;http://localhost&lt;/code&gt; in your browser.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;i-see-an-error-message-containing-address-already-in-use-or-port-is-already-allocated:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;I see an error message containing &lt;code&gt;address already in use&lt;/code&gt; or &lt;code&gt;port is already allocated&lt;/code&gt;&lt;/h3&gt;
&lt;h3 id=&#34;i-see-an-error-message-containing-address-already-in-use-or-port-is-already-allocated&#34;&gt;I see an error message containing &lt;code&gt;address already in use&lt;/code&gt; or &lt;code&gt;port is already allocated&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Make sure the ports for the services that you are trying to run (22, 80, 443, 3306, etc.) are not being used already by other programs on the host, such as a built in &lt;code&gt;apache&lt;/code&gt;/&lt;code&gt;httpd&lt;/code&gt; service or other development tools you have installed.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;i-get-nginx-error-404-not-found-on-windows:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;I get NGINX error 404 Not Found on Windows.&lt;/h3&gt;
&lt;h3 id=&#34;i-get-nginx-error-404-not-found-on-windows&#34;&gt;I get NGINX error 404 Not Found on Windows.&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Go to docker Settings on your Windows machine.&lt;/li&gt;
@ -1152,18 +1152,18 @@ e) set it to &lt;code&gt;true&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;the-time-in-my-services-does-not-match-the-current-time:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;The time in my services does not match the current time&lt;/h3&gt;
&lt;h3 id=&#34;the-time-in-my-services-does-not-match-the-current-time&#34;&gt;The time in my services does not match the current time&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Make sure you&#39;ve &lt;a href=&#34;#Change-the-timezone&#34;&gt;changed the timezone&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Make sure you&amp;rsquo;ve &lt;a href=&#34;#Change-the-timezone&#34;&gt;changed the timezone&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Stop and rebuild the containers (&lt;code&gt;docker-compose up -d --build &amp;lt;services&amp;gt;&lt;/code&gt;)&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;h3 id=&#34;i-get-mysql-connection-refused:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;I get MySQL connection refused&lt;/h3&gt;
&lt;h3 id=&#34;i-get-mysql-connection-refused&#34;&gt;I get MySQL connection refused&lt;/h3&gt;
&lt;p&gt;This error sometimes happens because your Laravel application isn&#39;t running on the container localhost IP (Which is 127.0.0.1). Steps to fix it:&lt;/p&gt;
&lt;p&gt;This error sometimes happens because your Laravel application isn&amp;rsquo;t running on the container localhost IP (Which is 127.0.0.1). Steps to fix it:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Option A

66
docs/getting-started/index.html
View File

@ -9,7 +9,7 @@
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,user-scalable=no,initial-scale=1,maximum-scale=1">
<meta http-equiv="X-UA-Compatible" content="IE=10" />
<title>Getting started - Laradock Docs</title>
<title>Getting Started - Laradock Docs</title>
<meta name="generator" content="Hugo 0.18.1" />
@ -97,7 +97,7 @@
</div>
<div class="stretch">
<div class="title">
Getting started
Getting Started
</div>
</div>
@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a class="current" title="Getting started" href="http://laradock.io/getting-started/">
<a class="current" title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>
@ -332,30 +332,26 @@
<article class="article">
<div class="wrapper">
<h1>Getting started </h1>
<h1>Getting Started </h1>
<p><a name="Requirements"></a></p>
<h2 id="requirements:d680e8a854a7cbad6d490c445cba2eba">Requirements</h2>
<h2 id="requirements">Requirements</h2>
<ul>
<li><a href="https://git-scm.com/downloads">Git</a></li>
<li><a href="https://www.docker.com/products/docker/">Docker</a> <code>&gt;= 1.12</code></li>
</ul>
<p><a name="Installation"></a></p>
<h2 id="installation:d680e8a854a7cbad6d490c445cba2eba">Installation</h2>
<h2 id="installation">Installation</h2>
<p>Choose the setup the best suits your needs.</p>
<h4 id="a-setup-for-single-project:d680e8a854a7cbad6d490c445cba2eba">A) Setup for Single Project:</h4>
<h4 id="a-setup-for-single-project">A) Setup for Single Project:</h4>
<p><em>(In case you want a Docker environment for each project)</em></p>
<h5 id="a-1-setup-environment-in-existing-project:d680e8a854a7cbad6d490c445cba2eba">A.1) Setup environment in existing Project:</h5>
<h5 id="a-1-setup-environment-in-existing-project">A.1) Setup environment in existing Project:</h5>
<p><em>(In case you already have a project, and you want to setup an environment to run it)</em></p>
@ -376,9 +372,9 @@
- laradock
</code></pre>
<h5 id="a-2-setup-environment-first-then-create-project:d680e8a854a7cbad6d490c445cba2eba">A.2) Setup environment first then create project:</h5>
<h5 id="a-2-setup-environment-first-then-create-project">A.2) Setup environment first then create project:</h5>
<p><em>(In case you don't have a project, and you want to create your project inside the Docker environment)</em></p>
<p><em>(In case you don&rsquo;t have a project, and you want to create your project inside the Docker environment)</em></p>
<p>1 - Clone this repository anywhere on your machine:</p>
@ -399,7 +395,7 @@
<pre><code>docker-compose stop &amp;&amp; docker-compose up -d XXXX YYYY ZZZZ ....
</code></pre>
<h4 id="b-setup-for-multiple-projects:d680e8a854a7cbad6d490c445cba2eba">B) Setup for Multiple Projects:</h4>
<h4 id="b-setup-for-multiple-projects">B) Setup for Multiple Projects:</h4>
<p>1 - Clone this repository anywhere on your machine:</p>
@ -415,7 +411,7 @@
- ../project2/:/var/www/project2
</code></pre>
<p>3 - You can access all sites by visiting <code>http://localhost/project1/public</code> and <code>http://localhost/project2/public</code> but of course that's not very useful so let's setup NGINX quickly.</p>
<p>3 - You can access all sites by visiting <code>http://localhost/project1/public</code> and <code>http://localhost/project2/public</code> but of course that&rsquo;s not very useful so let&rsquo;s setup NGINX quickly.</p>
<p>4 - Go to <code>nginx/sites</code> and copy <code>sample.conf.example</code> to <code>project1.conf</code> then to <code>project2.conf</code></p>
@ -425,7 +421,7 @@
root /var/www/project1/public;
</code></pre>
<p>Do the same for each project <code>project2.conf</code>, <code>project3.conf</code>,...</p>
<p>Do the same for each project <code>project2.conf</code>, <code>project3.conf</code>,&hellip;</p>
<p>6 - Add the domains to the <strong>hosts</strong> files.</p>
@ -434,9 +430,7 @@
<p>7 - Create your project Databases. Right now you have to do it manually by entering your DB container, until we automate it soon.</p>
<p><a name="Usage"></a></p>
<h2 id="usage:d680e8a854a7cbad6d490c445cba2eba">Usage</h2>
<h2 id="usage">Usage</h2>
<p><strong>Read Before starting:</strong></p>
@ -450,7 +444,7 @@
<p><br></p>
<blockquote>
<p><strong>Warning:</strong> If you used an older version of LaraDock it's highly recommended to rebuild the containers you need to use <a href="#Build-Re-build-Containers">see how you rebuild a container</a> in order to prevent errors as much as possible.</p>
<p><strong>Warning:</strong> If you used an older version of LaraDock it&rsquo;s highly recommended to rebuild the containers you need to use <a href="#Build-Re-build-Containers">see how you rebuild a container</a> in order to prevent errors as much as possible.</p>
</blockquote>
<p><br></p>
@ -462,14 +456,14 @@
<pre><code class="language-bash">docker-compose up -d nginx mysql
</code></pre>
<p><strong>Note</strong>: The <code>workspace</code> and <code>php-fpm</code> will run automatically in most of the cases, so no need to specify them in the <code>up</code> command. If you couldn't find them running then you need specify them as follow: <code>docker-compose up -d nginx php-fpm mysql workspace</code>.</p>
<p><strong>Note</strong>: The <code>workspace</code> and <code>php-fpm</code> will run automatically in most of the cases, so no need to specify them in the <code>up</code> command. If you couldn&rsquo;t find them running then you need specify them as follow: <code>docker-compose up -d nginx php-fpm mysql workspace</code>.</p>
<p>You can select your own combination of Containers form the list below:</p>
<p><code>nginx</code>, <code>hhvm</code>, <code>php-fpm</code>, <code>mysql</code>, <code>redis</code>, <code>postgres</code>, <code>mariadb</code>, <code>neo4j</code>, <code>mongo</code>, <code>apache2</code>, <code>caddy</code>, <code>memcached</code>, <code>beanstalkd</code>, <code>beanstalkd-console</code>, <code>rabbitmq</code>, <code>workspace</code>, <code>phpmyadmin</code>, <code>aerospike</code>, <code>pgadmin</code>, <code>elasticsearch</code>, <code>rethinkdb</code>.</p>
<p><br>
2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, ...).</p>
2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, &hellip;).</p>
<pre><code class="language-bash">docker-compose exec workspace bash
</code></pre>
@ -479,7 +473,7 @@
<pre><code class="language-bash">docker exec -it {workspace-container-id} bash
</code></pre>
<p><strong>Note:</strong> You can add <code>--user=laradock</code> (example <code>docker-compose exec --user=laradock workspace bash</code>) to have files created as your host's user. (you can change the PUID (User id) and PGID (group id) variables from the <code>docker-compose.yml</code>).</p>
<p><strong>Note:</strong> You can add <code>--user=laradock</code> (example <code>docker-compose exec --user=laradock workspace bash</code>) to have files created as your host&rsquo;s user. (you can change the PUID (User id) and PGID (group id) variables from the <code>docker-compose.yml</code>).</p>
<p><br>
3 - Edit your project configurations.</p>
@ -489,7 +483,7 @@
<pre><code class="language-env">DB_HOST=mysql
</code></pre>
<p><em>If you want to use Laravel and you don't have it installed yet, see <a href="#Install-Laravel">How to Install Laravel in a Docker Container</a>.</em></p>
<p><em>If you want to use Laravel and you don&rsquo;t have it installed yet, see <a href="#Install-Laravel">How to Install Laravel in a Docker Container</a>.</em></p>
<p><br>
4 - Open your browser and visit your localhost address (<code>http://localhost/</code>).</p>
@ -514,6 +508,22 @@
<nav class="pagination" aria-label="Footer">
<div class="previous">
<a href="http://laradock.io/" title="Overview">
<span class="direction">
Previous
</span>
<div class="page">
<div class="button button-previous" role="button" aria-label="Previous">
<i class="icon icon-back"></i>
</div>
<div class="stretch">
<div class="title">
Overview
</div>
</div>
</div>
</a>
</div>
<div class="next">

38
docs/getting-started/index.xml
View File

@ -9,33 +9,29 @@
<atom:link href="http://laradock.io/getting-started/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Getting started</title>
<title>Getting Started</title>
<link>http://laradock.io/getting-started/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>http://laradock.io/getting-started/</guid>
<description>
&lt;p&gt;&lt;a name=&#34;Requirements&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;requirements:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Requirements&lt;/h2&gt;
&lt;h2 id=&#34;requirements&#34;&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://git-scm.com/downloads&#34;&gt;Git&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://www.docker.com/products/docker/&#34;&gt;Docker&lt;/a&gt; &lt;code&gt;&amp;gt;= 1.12&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a name=&#34;Installation&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;installation:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Installation&lt;/h2&gt;
&lt;h2 id=&#34;installation&#34;&gt;Installation&lt;/h2&gt;
&lt;p&gt;Choose the setup the best suits your needs.&lt;/p&gt;
&lt;h4 id=&#34;a-setup-for-single-project:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;A) Setup for Single Project:&lt;/h4&gt;
&lt;h4 id=&#34;a-setup-for-single-project&#34;&gt;A) Setup for Single Project:&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;(In case you want a Docker environment for each project)&lt;/em&gt;&lt;/p&gt;
&lt;h5 id=&#34;a-1-setup-environment-in-existing-project:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;A.1) Setup environment in existing Project:&lt;/h5&gt;
&lt;h5 id=&#34;a-1-setup-environment-in-existing-project&#34;&gt;A.1) Setup environment in existing Project:&lt;/h5&gt;
&lt;p&gt;&lt;em&gt;(In case you already have a project, and you want to setup an environment to run it)&lt;/em&gt;&lt;/p&gt;
@ -56,9 +52,9 @@
- laradock
&lt;/code&gt;&lt;/pre&gt;
&lt;h5 id=&#34;a-2-setup-environment-first-then-create-project:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;A.2) Setup environment first then create project:&lt;/h5&gt;
&lt;h5 id=&#34;a-2-setup-environment-first-then-create-project&#34;&gt;A.2) Setup environment first then create project:&lt;/h5&gt;
&lt;p&gt;&lt;em&gt;(In case you don&#39;t have a project, and you want to create your project inside the Docker environment)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;(In case you don&amp;rsquo;t have a project, and you want to create your project inside the Docker environment)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;1 - Clone this repository anywhere on your machine:&lt;/p&gt;
@ -79,7 +75,7 @@
&lt;pre&gt;&lt;code&gt;docker-compose stop &amp;amp;&amp;amp; docker-compose up -d XXXX YYYY ZZZZ ....
&lt;/code&gt;&lt;/pre&gt;
&lt;h4 id=&#34;b-setup-for-multiple-projects:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;B) Setup for Multiple Projects:&lt;/h4&gt;
&lt;h4 id=&#34;b-setup-for-multiple-projects&#34;&gt;B) Setup for Multiple Projects:&lt;/h4&gt;
&lt;p&gt;1 - Clone this repository anywhere on your machine:&lt;/p&gt;
@ -95,7 +91,7 @@
- ../project2/:/var/www/project2
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;3 - You can access all sites by visiting &lt;code&gt;http://localhost/project1/public&lt;/code&gt; and &lt;code&gt;http://localhost/project2/public&lt;/code&gt; but of course that&#39;s not very useful so let&#39;s setup NGINX quickly.&lt;/p&gt;
&lt;p&gt;3 - You can access all sites by visiting &lt;code&gt;http://localhost/project1/public&lt;/code&gt; and &lt;code&gt;http://localhost/project2/public&lt;/code&gt; but of course that&amp;rsquo;s not very useful so let&amp;rsquo;s setup NGINX quickly.&lt;/p&gt;
&lt;p&gt;4 - Go to &lt;code&gt;nginx/sites&lt;/code&gt; and copy &lt;code&gt;sample.conf.example&lt;/code&gt; to &lt;code&gt;project1.conf&lt;/code&gt; then to &lt;code&gt;project2.conf&lt;/code&gt;&lt;/p&gt;
@ -105,7 +101,7 @@
root /var/www/project1/public;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Do the same for each project &lt;code&gt;project2.conf&lt;/code&gt;, &lt;code&gt;project3.conf&lt;/code&gt;,...&lt;/p&gt;
&lt;p&gt;Do the same for each project &lt;code&gt;project2.conf&lt;/code&gt;, &lt;code&gt;project3.conf&lt;/code&gt;,&amp;hellip;&lt;/p&gt;
&lt;p&gt;6 - Add the domains to the &lt;strong&gt;hosts&lt;/strong&gt; files.&lt;/p&gt;
@ -114,9 +110,7 @@
&lt;p&gt;7 - Create your project Databases. Right now you have to do it manually by entering your DB container, until we automate it soon.&lt;/p&gt;
&lt;p&gt;&lt;a name=&#34;Usage&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;usage:d680e8a854a7cbad6d490c445cba2eba&#34;&gt;Usage&lt;/h2&gt;
&lt;h2 id=&#34;usage&#34;&gt;Usage&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Read Before starting:&lt;/strong&gt;&lt;/p&gt;
@ -130,7 +124,7 @@
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Warning:&lt;/strong&gt; If you used an older version of LaraDock it&#39;s highly recommended to rebuild the containers you need to use &lt;a href=&#34;#Build-Re-build-Containers&#34;&gt;see how you rebuild a container&lt;/a&gt; in order to prevent errors as much as possible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Warning:&lt;/strong&gt; If you used an older version of LaraDock it&amp;rsquo;s highly recommended to rebuild the containers you need to use &lt;a href=&#34;#Build-Re-build-Containers&#34;&gt;see how you rebuild a container&lt;/a&gt; in order to prevent errors as much as possible.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;br&gt;&lt;/p&gt;
@ -142,14 +136,14 @@
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose up -d nginx mysql
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: The &lt;code&gt;workspace&lt;/code&gt; and &lt;code&gt;php-fpm&lt;/code&gt; will run automatically in most of the cases, so no need to specify them in the &lt;code&gt;up&lt;/code&gt; command. If you couldn&#39;t find them running then you need specify them as follow: &lt;code&gt;docker-compose up -d nginx php-fpm mysql workspace&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: The &lt;code&gt;workspace&lt;/code&gt; and &lt;code&gt;php-fpm&lt;/code&gt; will run automatically in most of the cases, so no need to specify them in the &lt;code&gt;up&lt;/code&gt; command. If you couldn&amp;rsquo;t find them running then you need specify them as follow: &lt;code&gt;docker-compose up -d nginx php-fpm mysql workspace&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;You can select your own combination of Containers form the list below:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;nginx&lt;/code&gt;, &lt;code&gt;hhvm&lt;/code&gt;, &lt;code&gt;php-fpm&lt;/code&gt;, &lt;code&gt;mysql&lt;/code&gt;, &lt;code&gt;redis&lt;/code&gt;, &lt;code&gt;postgres&lt;/code&gt;, &lt;code&gt;mariadb&lt;/code&gt;, &lt;code&gt;neo4j&lt;/code&gt;, &lt;code&gt;mongo&lt;/code&gt;, &lt;code&gt;apache2&lt;/code&gt;, &lt;code&gt;caddy&lt;/code&gt;, &lt;code&gt;memcached&lt;/code&gt;, &lt;code&gt;beanstalkd&lt;/code&gt;, &lt;code&gt;beanstalkd-console&lt;/code&gt;, &lt;code&gt;rabbitmq&lt;/code&gt;, &lt;code&gt;workspace&lt;/code&gt;, &lt;code&gt;phpmyadmin&lt;/code&gt;, &lt;code&gt;aerospike&lt;/code&gt;, &lt;code&gt;pgadmin&lt;/code&gt;, &lt;code&gt;elasticsearch&lt;/code&gt;, &lt;code&gt;rethinkdb&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, ...).&lt;/p&gt;
2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, &amp;hellip;).&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker-compose exec workspace bash
&lt;/code&gt;&lt;/pre&gt;
@ -159,7 +153,7 @@
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;docker exec -it {workspace-container-id} bash
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; You can add &lt;code&gt;--user=laradock&lt;/code&gt; (example &lt;code&gt;docker-compose exec --user=laradock workspace bash&lt;/code&gt;) to have files created as your host&#39;s user. (you can change the PUID (User id) and PGID (group id) variables from the &lt;code&gt;docker-compose.yml&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; You can add &lt;code&gt;--user=laradock&lt;/code&gt; (example &lt;code&gt;docker-compose exec --user=laradock workspace bash&lt;/code&gt;) to have files created as your host&amp;rsquo;s user. (you can change the PUID (User id) and PGID (group id) variables from the &lt;code&gt;docker-compose.yml&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
3 - Edit your project configurations.&lt;/p&gt;
@ -169,7 +163,7 @@
&lt;pre&gt;&lt;code class=&#34;language-env&#34;&gt;DB_HOST=mysql
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;em&gt;If you want to use Laravel and you don&#39;t have it installed yet, see &lt;a href=&#34;#Install-Laravel&#34;&gt;How to Install Laravel in a Docker Container&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If you want to use Laravel and you don&amp;rsquo;t have it installed yet, see &lt;a href=&#34;#Install-Laravel&#34;&gt;How to Install Laravel in a Docker Container&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;br&gt;
4 - Open your browser and visit your localhost address (&lt;code&gt;http://localhost/&lt;/code&gt;).&lt;/p&gt;

8
docs/help/index.html
View File

@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a title="Getting started" href="http://laradock.io/getting-started/">
<a title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>

2918
docs/index.html
View File

File diff suppressed because it is too large Load Diff

3134
docs/index.xml
View File

File diff suppressed because it is too large Load Diff

8
docs/license/index.html
View File

@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a title="Getting started" href="http://laradock.io/getting-started/">
<a title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>

8
docs/related-projects/index.html
View File

@ -180,9 +180,9 @@
<a title="Introduction" href="http://laradock.io/">
<a title="Overview" href="http://laradock.io/">
Introduction
Overview
</a>
@ -198,9 +198,9 @@
<a title="Getting started" href="http://laradock.io/getting-started/">
<a title="Getting Started" href="http://laradock.io/getting-started/">
Getting started
Getting Started
</a>

8
docs/sitemap.xml
View File

@ -1,6 +1,10 @@
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>http://laradock.io/</loc>
</url>
<url>
<loc>http://laradock.io/getting-started/</loc>
</url>
@ -60,8 +64,4 @@
<priority>0</priority>
</url>
<url>
<loc>http://laradock.io/</loc>
</url>
</urlset>