deploy: a7600e844e
This commit is contained in:
bestlong
@@ -378,7 +378,8 @@ alias devdown="cd /PATH_TO_LARADOCK/laradock; ./sync.sh down"
|
||||
</code></pre><p>4) Create (or edit) the file <code>~/d4m-nfs/etc/d4m-nfs-mounts.txt</code>, and write the following configuration in it:</p><pre><code class=language-txt>/Users:/Users
|
||||
</code></pre><p>5) Create (or edit) the file <code>/etc/exports</code>, make sure it exists and is empty. (There may be collisions if you come from Vagrant or if you already executed the <code>d4m-nfs.sh</code> script before).</p><p>6) Run the <code>d4m-nfs.sh</code> script (might need Sudo):</p><pre><code class=language-bash>~/d4m-nfs/d4m-nfs.sh
|
||||
</code></pre><p>That’s it! Run your containers.. Example:</p><pre><code class=language-bash>docker-compose up ...
|
||||
</code></pre><p><em>Note: If you faced any errors, try restarting Docker, and make sure you have no spaces in the <code>d4m-nfs-mounts.txt</code> file, and your <code>/etc/exports</code> file is clear.</em></p><p><br><a name=upgrade-laradock></a></p><h2 id=upgrade-laradock>Upgrade Laradock</h2><p>Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading Laradock from v3.* to v4.*:</p><ol><li>Stop the docker VM <code>docker-machine stop {default}</code></li><li>Install Docker for <a href=https://docs.docker.com/docker-for-mac/>Mac</a> or <a href=https://docs.docker.com/docker-for-windows/>Windows</a>.</li><li>Upgrade Laradock to <code>v4.*.*</code> (<code>git pull origin master</code>)</li><li>Use Laradock as you used to do: <code>docker-compose up -d nginx mysql</code>.</li></ol><p><strong>Note:</strong> If you face any problem with the last step above: rebuild all your containers
|
||||
</code></pre><p><em>Note: If you faced any errors, try restarting Docker, and make sure you have no spaces in the <code>d4m-nfs-mounts.txt</code> file, and your <code>/etc/exports</code> file is clear.</em></p><p><br><a name=ca-certificates></a></p><h2 id=ca-certificates>ca-certificates</h2><p>To install your own CA certificates, you can add them to the <code>workspace/ca-certificates</code> folder.
|
||||
This way the certificates will be installed into the system ca store of the workspace container.</p><p><br><a name=upgrade-laradock></a></p><h2 id=upgrade-laradock>Upgrade Laradock</h2><p>Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading Laradock from v3.* to v4.*:</p><ol><li>Stop the docker VM <code>docker-machine stop {default}</code></li><li>Install Docker for <a href=https://docs.docker.com/docker-for-mac/>Mac</a> or <a href=https://docs.docker.com/docker-for-windows/>Windows</a>.</li><li>Upgrade Laradock to <code>v4.*.*</code> (<code>git pull origin master</code>)</li><li>Use Laradock as you used to do: <code>docker-compose up -d nginx mysql</code>.</li></ol><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>
|
||||
“Warning Containers Data might be lost!”</p><aside class=copyright role=note><br><br>Documentation built with
|
||||
<a href=https://www.gohugo.io target=_blank>Hugo</a>
|
||||
|
||||
@@ -515,7 +515,8 @@ alias devdown="cd /PATH_TO_LARADOCK/laradock; ./sync.sh down"
|
||||
</code></pre><p>4) Create (or edit) the file <code>~/d4m-nfs/etc/d4m-nfs-mounts.txt</code>, and write the following configuration in it:</p><pre><code class=language-txt>/Users:/Users
|
||||
</code></pre><p>5) Create (or edit) the file <code>/etc/exports</code>, make sure it exists and is empty. (There may be collisions if you come from Vagrant or if you already executed the <code>d4m-nfs.sh</code> script before).</p><p>6) Run the <code>d4m-nfs.sh</code> script (might need Sudo):</p><pre><code class=language-bash>~/d4m-nfs/d4m-nfs.sh
|
||||
</code></pre><p>That’s it! Run your containers.. Example:</p><pre><code class=language-bash>docker-compose up ...
|
||||
</code></pre><p><em>Note: If you faced any errors, try restarting Docker, and make sure you have no spaces in the <code>d4m-nfs-mounts.txt</code> file, and your <code>/etc/exports</code> file is clear.</em></p><p><br><a name=upgrade-laradock></a></p><h2 id=upgrade-laradock>Upgrade Laradock</h2><p>Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading Laradock from v3.* to v4.*:</p><ol><li>Stop the docker VM <code>docker-machine stop {default}</code></li><li>Install Docker for <a href=https://docs.docker.com/docker-for-mac/>Mac</a> or <a href=https://docs.docker.com/docker-for-windows/>Windows</a>.</li><li>Upgrade Laradock to <code>v4.*.*</code> (<code>git pull origin master</code>)</li><li>Use Laradock as you used to do: <code>docker-compose up -d nginx mysql</code>.</li></ol><p><strong>Note:</strong> If you face any problem with the last step above: rebuild all your containers
|
||||
</code></pre><p><em>Note: If you faced any errors, try restarting Docker, and make sure you have no spaces in the <code>d4m-nfs-mounts.txt</code> file, and your <code>/etc/exports</code> file is clear.</em></p><p><br><a name=ca-certificates></a></p><h2 id=ca-certificates>ca-certificates</h2><p>To install your own CA certificates, you can add them to the <code>workspace/ca-certificates</code> folder.
|
||||
This way the certificates will be installed into the system ca store of the workspace container.</p><p><br><a name=upgrade-laradock></a></p><h2 id=upgrade-laradock>Upgrade Laradock</h2><p>Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading Laradock from v3.* to v4.*:</p><ol><li>Stop the docker VM <code>docker-machine stop {default}</code></li><li>Install Docker for <a href=https://docs.docker.com/docker-for-mac/>Mac</a> or <a href=https://docs.docker.com/docker-for-windows/>Windows</a>.</li><li>Upgrade Laradock to <code>v4.*.*</code> (<code>git pull origin master</code>)</li><li>Use Laradock as you used to do: <code>docker-compose up -d nginx mysql</code>.</li></ol><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>
|
||||
“Warning Containers Data might be lost!”</p><br><br><br><br><br><br><hr><br><h1>Help & Questions</h1><p>Join the chat room on <a href=https://gitter.im/Laradock/laradock>Gitter</a> and get help and support from the community.</p><p><a href="https://gitter.im/Laradock/laradock?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge"><img src=https://badges.gitter.im/Laradock/laradock.svg alt=Gitter></a></p><p>You can as well can open an <a href=https://github.com/laradock/laradock/issues>issue</a> on Github (will be labeled as Question) and discuss it with people on <a href=https://gitter.im/Laradock/laradock>Gitter</a>.</p><p><br><a name=Common-Problems></a></p><h1 id=common-problems>Common Problems</h1><p><em>Here’s a list of the common problems you might face, and the possible solutions.</em></p><p><br></p><h2 id=i-see-a-blank-white-page-instead-of-the-laravel-welcome-page>I see a blank (white) page instead of the Laravel ‘Welcome’ page!</h2><p>Run the following command from the Laravel root directory:</p><pre><code class=language-bash>sudo chmod -R 777 storage bootstrap/cache
|
||||
</code></pre><p><br></p><h2 id=i-see-welcome-to-nginx-instead-of-the-laravel-app>I see “Welcome to nginx” instead of the Laravel App!</h2><p>Use <code>http://127.0.0.1</code> instead of <code>http://localhost</code> in your browser.</p><p><br></p><h2 id=i-see-an-error-message-containing-address-already-in-use-or-port-is-already-allocated>I see an error message containing (address already in use) or (port is already allocated)</h2><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><h2 id=i-get-nginx-error-404-not-found-on-windows>I get NGINX error 404 Not Found on Windows.</h2><ol><li>Go to docker Settings on your Windows machine.</li><li>Click on the <code>Shared Drives</code> tab and check the drive that contains your project files.</li><li>Enter your windows username and password.</li><li>Go to the <code>reset</code> tab and click restart docker.</li></ol><p><br></p><h2 id=the-time-in-my-services-does-not-match-the-current-time>The time in my services does not match the current time</h2><ol><li>Make sure you’ve <a href=#Change-the-timezone>changed the timezone</a>.</li><li>Stop and rebuild the containers (<code>docker-compose up -d --build <services></code>)</li></ol><p><br></p><h2 id=i-get-mysql-connection-refused>I get MySQL connection refused</h2><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><ul><li>Option A<ol><li>Check your running Laravel application IP by dumping <code>Request::ip()</code> variable using <code>dd(Request::ip())</code> anywhere on your application. The result is the IP of your Laravel container.</li><li>Change the <code>DB_HOST</code> variable on env with the IP that you received from previous step.</li></ol></li><li>Option B<ol><li>Change the <code>DB_HOST</code> value to the same name as the MySQL docker container. The Laradock docker-compose file currently has this as <code>mysql</code></li></ol></li></ul><h2 id=i-get-stuck-when-building-nginx-on-fetch-mirrors-aliyun-com-alpine-v3-5-main-x86-64-apkindex-tar-gz>I get stuck when building nginx on (fetch mirrors.aliyun.com/alpine/v3.5/main/x86_64/APKINDEX.tar.gz)</h2><p>As stated on <a href=https://github.com/laradock/laradock/issues/749#issuecomment-419652646>#749</a>, Already fixed，just set <code>CHANGE_SOURCE</code> to false.</p><h2 id=custom-composer-repo-packagist-url-and-npm-registry-url>Custom composer repo packagist url and npm registry url</h2><p>In China, the origin source of composer and npm is very slow. You can add <code>WORKSPACE_NPM_REGISTRY</code> and <code>WORKSPACE_COMPOSER_REPO_PACKAGIST</code> config in <code>.env</code> to use your custom source.</p><p>Example:</p><pre><code class=language-bash>WORKSPACE_NPM_REGISTRY=https://registry.npmmirror.com
|
||||
|
||||
Reference in New Issue
Block a user