Upgrade hugo to 0.20.2 and added uglyurls = true to fix issues we when upgrading from 0.19 to 0.20 recently, also fixed 404 photos*
This commit is contained in:
Diego Antunes
parent
a7624a7034
commit
7f540ed7e2
|
|
@ -8,7 +8,7 @@ env:
|
|||
- PHP_VERSION=56
|
||||
- PHP_VERSION=70
|
||||
- PHP_VERSION=71
|
||||
- HUGO_VERSION=0.19
|
||||
- HUGO_VERSION=0.20.2
|
||||
|
||||
script: ./_scripts/travis-build.sh
|
||||
|
||||
|
|
|
|||
|
|
@ -5,6 +5,7 @@ title = "Laradock"
|
|||
theme = "hugo-material-docs"
|
||||
metadataformat = "yaml"
|
||||
canonifyurls = true
|
||||
uglyurls = true
|
||||
# Enable Google Analytics by entering your tracking id
|
||||
googleAnalytics = "UA-37514928-9"
|
||||
|
||||
|
|
|
|||
|
|
@ -279,10 +279,10 @@ you should be able to adjust accordingly. This guide was written based on Docker
|
|||
## hosts
|
||||
- Add `laravel` to your hosts file located on Windows 10 at `C:\Windows\System32\drivers\etc\hosts`. It should be set to the IP of your running container. Mine is: `10.0.75.2`
|
||||
On Windows you can find it by opening Windows `Hyper-V Manager`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- [Hosts File Editor](https://github.com/scottlerch/HostsFileEditor) makes it easy to change your hosts file.
|
||||
- Set `laravel` to your docker host IP. See [Example](photos/SimpleHostsEditor/AddHost_laravel.png).
|
||||
- Set `laravel` to your docker host IP. See [Example](images/photos/SimpleHostsEditor/AddHost_laravel.png).
|
||||
|
||||
|
||||
<a name="FireWall"></a>
|
||||
|
|
@ -428,54 +428,54 @@ If you have enabled `xdebug=true` in `docker-compose.yml/php-fpm`, `xdebug` will
|
|||
## PHPStorm Settings
|
||||
- Here are some settings that are known to work:
|
||||
- `Settings/BuildDeploymentConnection`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/BuildDeploymentConnectionMappings`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/BuildDeploymentDebugger`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/EditRunConfigurationRemoteWebDebug`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/EditRunConfigurationRemoteExampleTestDebug`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/LangsPHPDebug`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/LangsPHPInterpreters`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/LangsPHPPHPUnit`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `Settings/LangsPHPServers`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `RemoteHost`
|
||||
To switch on this view, go to: `Menu/Tools/Deployment/Browse Remote Host`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- `RemoteWebDebug`
|
||||
- 
|
||||
- 
|
||||
|
||||
- `EditRunConfigurationRemoteWebDebug`
|
||||
Go to: `Menu/Run/Edit Configurations`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- `EditRunConfigurationRemoteExampleTestDebug`
|
||||
Go to: `Menu/Run/Edit Configurations`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- `WindowsFirewallAllowedApps`
|
||||
Go to: `Control Panel\All Control Panel Items\Windows Firewall\Allowed apps`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- `hosts`
|
||||
Edit: `C:\Windows\System32\drivers\etc\hosts`.
|
||||
- 
|
||||
- 
|
||||
|
||||
- [Enable xDebug on php-fpm](#enablePhpXdebug)
|
||||
|
||||
|
|
@ -497,7 +497,7 @@ If you have enabled `xdebug=true` in `docker-compose.yml/php-fpm`, `xdebug` will
|
|||
- right-click on `tests/ExampleTest.php`
|
||||
- Select: `Debug 'ExampleTest.php'`.
|
||||
- Should have stopped at the BreakPoint!! You are now debugging locally against a remote Laravel project via SSH!
|
||||
- 
|
||||
- 
|
||||
|
||||
|
||||
<a name="UsagePHPStormDebugSite"></a>
|
||||
|
|
@ -508,13 +508,13 @@ If you have enabled `xdebug=true` in `docker-compose.yml/php-fpm`, `xdebug` will
|
|||
`./xdebugPhpFpm stop`
|
||||
|
||||
- Start Remote Debugging
|
||||
- 
|
||||
- 
|
||||
|
||||
- Open to edit: `bootstrap/app.php`
|
||||
- Add a BreakPoint on line 14: `$app = new Illuminate\Foundation\Application(`
|
||||
- Reload [Laravel Site](http://laravel/)
|
||||
- Should have stopped at the BreakPoint!! You are now debugging locally against a remote Laravel project via SSH!
|
||||
- 
|
||||
- 
|
||||
|
||||
|
||||
<a name="SSHintoWorkspace"></a>
|
||||
|
|
@ -533,14 +533,14 @@ Assuming that you are in laradock folder, type:
|
|||
[Kitty](http://www.9bis.net/kitty/) KiTTY is a fork from version 0.67 of PuTTY.
|
||||
|
||||
- Here are some settings that are working for me:
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
- 
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,14 @@
|
|||
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Categories on Laradock</title>
|
||||
<link>http://laradock.io/categories.html</link>
|
||||
<description>Recent content in Categories on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
|
||||
<atom:link href="http://laradock.io/categories/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
</channel>
|
||||
</rss>
|
||||
|
|
@ -10,7 +10,7 @@
|
|||
<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>Contributing - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -215,9 +215,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Contributings on Laradock</title>
|
||||
<link>http://laradock.io/contributing/index.xml</link>
|
||||
<link>http://laradock.io/contributing.html</link>
|
||||
<description>Recent content in Contributings on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/contributing/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/contributing/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Contributing</title>
|
||||
|
|
@ -14,182 +16,9 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/contributing/</guid>
|
||||
<description>
|
||||
|
||||
<p>Your contribution is more than welcome.</p>
|
||||
|
||||
<h2 id="i-have-a-question-problem">I have a Question/Problem</h2>
|
||||
|
||||
<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 <code>Question</code>) And you can still seek help on Gitter for it.</p>
|
||||
|
||||
<h2 id="i-found-an-issue">I found an Issue</h2>
|
||||
|
||||
<p>If have an issue or you found a typo in the documentation, you can help us by
|
||||
opnening an <a href="https://github.com/laradock/laradock/issues">Issue</a>.</p>
|
||||
|
||||
<p><strong>Steps to do before opening an Issue:</strong></p>
|
||||
|
||||
<ol>
|
||||
<li><p>Before you submit your issue search the archive, maybe your question was already answered couple hours ago (search in the closed Issues as well).</p></li>
|
||||
|
||||
<li><p>Decide if the Issue belongs to this project or to <a href="https://github.com/docker">Docker</a> itself! or even the tool you are using such as Nginx or MongoDB&hellip;</p></li>
|
||||
</ol>
|
||||
|
||||
<p>If your issue appears to be a bug, and hasn&rsquo;t been reported, then open a new issue.</p>
|
||||
|
||||
<p><em>This Help us to maximize the effort we can spend fixing issues and adding new
|
||||
features, by not reporting duplicate issues.</em></p>
|
||||
|
||||
<h2 id="i-want-a-feature">I want a Feature</h2>
|
||||
|
||||
<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 <code>Feature Suggestion</code>). If you would like to implement a new feature then consider submitting a Pull Request yourself.</p>
|
||||
|
||||
<h2 id="i-want-to-update-the-documentation-site">I want to update the Documentation (Site)</h2>
|
||||
|
||||
<p>Laradock uses <a href="https://gohugo.io/">Hugo</a> as website generator tool, with the <a href="http://themes.gohugo.io/theme/material-docs/">Material Docs theme</a>. You might need to check their docs quickly.</p>
|
||||
|
||||
<p>Go the <code>DOCUMENTATION/content</code> and search for the markdown file you want to edit</p>
|
||||
|
||||
<p>Note: Every folder represents a section in the sidebar &ldquo;Menu&rdquo;. And every page and sidebar has a <code>weight</code> number to show it&rsquo;s position in the site.</p>
|
||||
|
||||
<p>To update the sidebar or add a new section to it, you can edit this <code>DOCUMENTATION/config.toml</code> toml file.</p>
|
||||
|
||||
<blockquote>
|
||||
<p>The site will be auto-generated in the <code>docs/</code> folder by <a href="https://travis-ci.org/laradock/laradock/">Travis CI</a>.</p>
|
||||
</blockquote>
|
||||
|
||||
<p><br></p>
|
||||
|
||||
<h3 id="to-host-the-website-locally">To Host the website locally</h3>
|
||||
|
||||
<ol>
|
||||
<li>Install <a href="https://gohugo.io/">Hugo</a> on your machine.</li>
|
||||
<li>Edit the <code>DOCUMENTATION/content</code>.</li>
|
||||
<li>Delete the <code>/docs</code> folder from the root.</li>
|
||||
<li>After you finish the editing, go to <code>DOCUMENTATION/</code> and run the <code>hugo</code> command to generate the HTML docs (inside a new <code>/docs</code> folder).</li>
|
||||
</ol>
|
||||
|
||||
<h2 id="how-to-support-new-software-add-new-container">How to support new Software (Add new Container)</h2>
|
||||
|
||||
<ul>
|
||||
<li><p>Create folder with the software name.</p></li>
|
||||
|
||||
<li><p>Add a <code>Dockerfile</code>, write your code there.</p></li>
|
||||
|
||||
<li><p>You may add additional files in the software folder.</p></li>
|
||||
|
||||
<li><p>Add the software to the <code>docker-compose.yml</code> file.</p></li>
|
||||
|
||||
<li><p>Make sure you follow our commenting style.</p></li>
|
||||
|
||||
<li><p>Add the software in the <code>Documentation</code>.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="edit-existing-software-edit-a-container">Edit existing Software (Edit a Container)</h2>
|
||||
|
||||
<ul>
|
||||
<li><p>Open the software (container) folder.</p></li>
|
||||
|
||||
<li><p>Edit the files you want to update.</p></li>
|
||||
|
||||
<li><p><strong>Note:</strong> If you want to edit the base image of the <code>Workspace</code> or the <code>php-fpm</code> Containers,
|
||||
you need to edit their Docker-files from their GitHub repositories. For more info read their Dockerfiles comment on the Laradock repository.</p></li>
|
||||
|
||||
<li><p>Make sure to update the <code>Documentation</code> in case you made any changes.</p></li>
|
||||
</ul>
|
||||
|
||||
<h2 id="pull-request">Pull Request</h2>
|
||||
|
||||
<h3 id="1-before-submitting-a-pull-request-pr">1. Before Submitting a Pull Request (PR)</h3>
|
||||
|
||||
<p>Always Test everything and make sure its working:</p>
|
||||
|
||||
<ul>
|
||||
<li>Pull the latest updates (or fork of you don’t have permission)</li>
|
||||
<li>Before editing anything:
|
||||
|
||||
<ul>
|
||||
<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)
|
||||
|
||||
<ul>
|
||||
<li>Testing building the container (docker-compose build container-name) with no errors.</li>
|
||||
<li>Test it in a real App if possible.</li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
|
||||
<h3 id="2-submitting-a-pr">2. 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&rsquo;t want to duplicate efforts.</p></li>
|
||||
|
||||
<li><p>Make your changes in a new git branch:</p>
|
||||
|
||||
<pre><code class="language-shell"> git checkout -b my-fix-branch master
|
||||
</code></pre></li>
|
||||
|
||||
<li><p>Commit your changes using a descriptive commit message.</p></li>
|
||||
|
||||
<li><p>Push your branch to GitHub:</p>
|
||||
|
||||
<pre><code class="language-shell">git push origin my-fix-branch
|
||||
</code></pre></li>
|
||||
|
||||
<li><p>In GitHub, send a pull request to <code>laradock:master</code>.</p></li>
|
||||
|
||||
<li><p>If we suggest changes then:</p>
|
||||
|
||||
<ul>
|
||||
<li>Make the required updates.</li>
|
||||
<li>Commit your changes to your branch (e.g. <code>my-fix-branch</code>).</li>
|
||||
<li>Push the changes to your GitHub repository (this will update your Pull Request).</li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
|
||||
<blockquote>
|
||||
<p>If the PR gets too outdated we may ask you to rebase and force push to update the PR:</p>
|
||||
</blockquote>
|
||||
|
||||
<pre><code class="language-shell">git rebase master -i
|
||||
git push origin my-fix-branch -f
|
||||
</code></pre>
|
||||
|
||||
<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="3-after-your-pr-is-merged">3. 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>
|
||||
|
||||
<ul>
|
||||
<li><p>Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:</p>
|
||||
|
||||
<pre><code class="language-shell">git push origin --delete my-fix-branch
|
||||
</code></pre></li>
|
||||
|
||||
<li><p>Check out the master branch:</p>
|
||||
|
||||
<pre><code class="language-shell">git checkout master -f
|
||||
</code></pre></li>
|
||||
|
||||
<li><p>Delete the local branch:</p>
|
||||
|
||||
<pre><code class="language-shell">git branch -D my-fix-branch
|
||||
</code></pre></li>
|
||||
|
||||
<li><p>Update your master with the latest upstream version:</p>
|
||||
|
||||
<pre><code class="language-shell">git pull --ff upstream master
|
||||
</code></pre></li>
|
||||
</ul>
|
||||
|
||||
<p><br></p>
|
||||
|
||||
<h4 id="happy-coding">Happy Coding :)</h4>
|
||||
</description>
|
||||
<description>Your contribution is more than welcome.
|
||||
I have a Question/Problem If you have questions about how to use Laradock, please direct your questions to the discussion on Gitter. If you believe your question could help others, then consider opening an Issue (it will be labeled as Question) And you can still seek help on Gitter for it.
|
||||
I found an Issue If have an issue or you found a typo in the documentation, you can help us by opnening an Issue.</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
<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>Documentation - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -218,9 +218,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -10,7 +10,7 @@
|
|||
<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</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -218,9 +218,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Getting-starteds on Laradock</title>
|
||||
<link>http://laradock.io/getting-started/index.xml</link>
|
||||
<link>http://laradock.io/getting-started.html</link>
|
||||
<description>Recent content in Getting-starteds on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/getting-started/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/getting-started/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Getting Started</title>
|
||||
|
|
@ -14,207 +16,11 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/getting-started/</guid>
|
||||
<description>
|
||||
<description>Requirements Git Docker &gt;= 1.12 Installation Choose the setup the best suits your needs.
|
||||
A) Setup for Single Project A.1) Already have a PHP project A.2) Don&rsquo;t have a PHP project yet B) Setup for Multiple Projects
|
||||
A) Setup for Single Project (Follow these steps if you want a separate Docker environment for each project)
|
||||
|
||||
<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>
|
||||
|
||||
<h2 id="installation">Installation</h2>
|
||||
|
||||
<p>Choose the setup the best suits your needs.</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="#A">A) Setup for Single Project</a>
|
||||
|
||||
<ul>
|
||||
<li><a href="#A1">A.1) Already have a PHP project</a></li>
|
||||
<li><a href="#A2">A.2) Don&rsquo;t have a PHP project yet</a></li>
|
||||
</ul></li>
|
||||
<li><a href="#B">B) Setup for Multiple Projects</a></li>
|
||||
</ul>
|
||||
|
||||
<p><a name="A"></a></p>
|
||||
|
||||
<h3 id="a-setup-for-single-project">A) Setup for Single Project</h3>
|
||||
|
||||
<blockquote>
|
||||
<p>(Follow these steps if you want a separate Docker environment for each project)</p>
|
||||
</blockquote>
|
||||
|
||||
<p><a name="A1"></a></p>
|
||||
|
||||
<h3 id="a-1-already-have-a-php-project">A.1) Already have a PHP project:</h3>
|
||||
|
||||
<p>1 - Clone laradock on your project root directory:</p>
|
||||
|
||||
<pre><code class="language-bash">git submodule add https://github.com/Laradock/laradock.git
|
||||
</code></pre>
|
||||
|
||||
<p><strong>Notes:</strong></p>
|
||||
|
||||
<ul>
|
||||
<li><p>If you are not using Git yet for your project, you can use <code>git clone</code> instead of <code>git submodule</code>.</p></li>
|
||||
|
||||
<li><p>Note 2: To keep track of your Laradock changes, between your projects and also keep Laradock updated. <a href="http://laradock.io/documentation/#keep-track-of-your-laradock-changes">Check this</a></p></li>
|
||||
</ul>
|
||||
|
||||
<p>Your folder structure should look like this:</p>
|
||||
|
||||
<pre><code>+ project-a
|
||||
+ laradock-a
|
||||
+ project-b
|
||||
+ laradock-b
|
||||
</code></pre>
|
||||
|
||||
<p>(It&rsquo;s important to rename the folders differently in each project.)</p>
|
||||
|
||||
<blockquote>
|
||||
<p><strong>Now jump to the <a href="#Usage">Usage</a> section.</strong></p>
|
||||
</blockquote>
|
||||
|
||||
<p><a name="A2"></a></p>
|
||||
|
||||
<h3 id="a-2-don-t-have-a-php-project-yet">A.2) Don&rsquo;t have a PHP project yet:</h3>
|
||||
|
||||
<p>1 - Clone this repository anywhere on your machine:</p>
|
||||
|
||||
<pre><code class="language-bash">git clone https://github.com/laradock/laradock.git
|
||||
</code></pre>
|
||||
|
||||
<p>Your folder structure should look like this:</p>
|
||||
|
||||
<pre><code>+ laradock
|
||||
+ project-z
|
||||
</code></pre>
|
||||
|
||||
<p>2 - Edit your web server sites configuration.</p>
|
||||
|
||||
<p><strong>In case of NGINX:</strong> open <code>nginx/sites/default.conf</code> and change the <code>root</code> from <code>/var/www/public</code> to <code>/var/www/{my-project-folder-name}/public</code>.</p>
|
||||
|
||||
<p><em>Or you can keep <code>default.conf</code> as it is, and create a separate config <code>my-site.conf</code> file for it.</em></p>
|
||||
|
||||
<p><strong>In case of Apache:</strong> :P</p>
|
||||
|
||||
<p><br></p>
|
||||
|
||||
<blockquote>
|
||||
<p><strong>Now jump to the <a href="#Usage">Usage</a> section.</strong></p>
|
||||
</blockquote>
|
||||
|
||||
<p><a name="B"></a></p>
|
||||
|
||||
<h3 id="b-setup-for-multiple-projects">B) Setup for Multiple Projects:</h3>
|
||||
|
||||
<blockquote>
|
||||
<p>(Follow these steps if you want a single Docker environment for all your project)</p>
|
||||
</blockquote>
|
||||
|
||||
<p>1 - Clone this repository anywhere on your machine (similar to <a href="#A2">Steps A.2. from above</a>):</p>
|
||||
|
||||
<pre><code class="language-bash">git clone https://github.com/laradock/laradock.git
|
||||
</code></pre>
|
||||
|
||||
<p>Your folder structure should look like this:</p>
|
||||
|
||||
<pre><code>+ laradock
|
||||
+ project-1
|
||||
+ project-2
|
||||
</code></pre>
|
||||
|
||||
<p>2 - Go to <code>nginx/sites</code> and create config files to point to different project directory when visiting different domains.</p>
|
||||
|
||||
<p>Laradock by default includes <code>project-1.conf</code> and <code>project-2.conf</code> as working samples.</p>
|
||||
|
||||
<p>3 - change the default names <code>project-n</code>:</p>
|
||||
|
||||
<p>You can rename the config files, project folders and domains as you like, just make sure the <code>root</code> in the config files, is pointing to the correct project folder name.</p>
|
||||
|
||||
<p>4 - Add the domains to the <strong>hosts</strong> files.</p>
|
||||
|
||||
<pre><code>127.0.0.1 project-1.dev
|
||||
127.0.0.1 project-2.dev
|
||||
</code></pre>
|
||||
|
||||
<blockquote>
|
||||
<p><strong>Now jump to the <a href="#Usage">Usage</a> section.</strong></p>
|
||||
</blockquote>
|
||||
|
||||
<p><a name="Usage"></a></p>
|
||||
|
||||
<h2 id="usage">Usage</h2>
|
||||
|
||||
<p><strong>Read Before starting:</strong></p>
|
||||
|
||||
<p>If you are using <strong>Docker Toolbox</strong> (VM), do one of the following:</p>
|
||||
|
||||
<ul>
|
||||
<li>Upgrade to Docker <a href="https://www.docker.com/products/docker">Native</a> for Mac/Windows (Recommended). Check out <a href="http://laradock.io/documentation/#upgrading-laradock">Upgrading Laradock</a></li>
|
||||
<li>Use Laradock v3.*. Visit the <a href="https://github.com/laradock/laradock/tree/LaraDock-ToolBox">LaraDock-ToolBox</a> branch. <em>(outdated)</em></li>
|
||||
</ul>
|
||||
|
||||
<p><br></p>
|
||||
|
||||
<blockquote>
|
||||
<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 as much errors as possible.</p>
|
||||
</blockquote>
|
||||
|
||||
<p><br></p>
|
||||
|
||||
<p>1 - Enter the laradock folder and rename <code>env-example</code> to <code>.env</code></p>
|
||||
|
||||
<pre><code class="language-shell">cp env-example .env
|
||||
</code></pre>
|
||||
|
||||
<p>You can edit the <code>.env</code> file to chose which software&rsquo;s you want to be installed in your environment. You can always refer to the <code>docker-compose.yml</code> file to see how those variables are been used.</p>
|
||||
|
||||
<p>2 - Build the enviroment and run it using <code>docker-compose</code></p>
|
||||
|
||||
<p>In this example we&rsquo;ll see how to run NGINX (web server) and MySQL (database engine) to host a PHP Web Scripts:</p>
|
||||
|
||||
<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&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 <a href="http://laradock.io/introduction/#supported-software-images">this list</a>.</p>
|
||||
|
||||
<p><em>(Please note that sometimes we forget to update the docs, so check the <code>docker-compose.yml</code> file to see an updated list of all available containers).</em></p>
|
||||
|
||||
<p><br>
|
||||
3 - 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>
|
||||
|
||||
<p><em>Alternatively, for Windows PowerShell users: execute the following command to enter any running container:</em></p>
|
||||
|
||||
<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> to have files created as your host&rsquo;s user. Example:</p>
|
||||
|
||||
<pre><code class="language-shell">docker-compose exec --user=laradock workspace bash
|
||||
</code></pre>
|
||||
|
||||
<p><em>You can change the PUID (User id) and PGID (group id) variables from the <code>.env</code> file)</em></p>
|
||||
|
||||
<p><br>
|
||||
4 - Update your project configurations to use the database host</p>
|
||||
|
||||
<p>Open your PHP project&rsquo;s <code>.env</code> file or whichever configuration file you are reading from, and set the database host <code>DB_HOST</code> to <code>mysql</code>:</p>
|
||||
|
||||
<pre><code class="language-env">DB_HOST=mysql
|
||||
</code></pre>
|
||||
|
||||
<p><em>If you want to install Laravel as PHP project, see <a href="#Install-Laravel">How to Install Laravel in a Docker Container</a>.</em></p>
|
||||
|
||||
<p><br>
|
||||
5 - Open your browser and visit your localhost address <code>http://localhost/</code>. If you followed the multiple projects setup, you can visit <code>http://project-1.dev/</code> and <code>http://project-2.dev/</code>. But first don&rsquo;t</p>
|
||||
</description>
|
||||
A.1) Already have a PHP project: 1 - Clone laradock on your project root directory:</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -0,0 +1,24 @@
|
|||
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Guides on Laradock</title>
|
||||
<link>http://laradock.io/guides.html</link>
|
||||
<description>Recent content in Guides on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
|
||||
<atom:link href="http://laradock.io/guides/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Guides</title>
|
||||
<link>http://laradock.io/guides/</link>
|
||||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/guides/</guid>
|
||||
<description>Production Setup on Digital Ocean PHPStorm XDebug Setup
|
||||
Production Setup on Digital Ocean Install Docker Visit DigitalOcean and login. Click the Create Droplet button. Open the One-click apps tab. Select Docker with your preferred version. Continue creating the droplet as you normally would. If needed, check your e-mail for the droplet root password. SSH to your Server Find the IP address of the droplet in the DigitalOcean interface.</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
</rss>
|
||||
|
|
@ -10,7 +10,7 @@
|
|||
<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>Help & Questions - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -215,9 +215,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Helps on Laradock</title>
|
||||
<link>http://laradock.io/help/index.xml</link>
|
||||
<link>http://laradock.io/help.html</link>
|
||||
<description>Recent content in Helps on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/help/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/help/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Help & Questions</title>
|
||||
|
|
@ -14,10 +16,8 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/help/</guid>
|
||||
<description><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>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>
|
||||
</description>
|
||||
<description>Join the chat room on Gitter and get help and support from the community.
|
||||
You can as well can open an issue on Github (will be labeled as Question) and discuss it with people on Gitter.</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 22 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.3 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 9.5 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
|
|
@ -10,7 +10,7 @@
|
|||
<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>Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -218,9 +218,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
@ -405,7 +405,7 @@ You can turn On/Off as many instances of as any container without worrying about
|
|||
|
||||
<ul>
|
||||
<li><strong>Database Engines:</strong>
|
||||
MySQL - MariaDB - MongoDB - Neo4j - RethinkDB - MSSQL - PostgreSQL - Postgres Postgis.</li>
|
||||
MySQL - MariaDB - Percona - MongoDB - Neo4j - RethinkDB - MSSQL - PostgreSQL - Postgres Postgis.</li>
|
||||
<li><strong>Cache Engines:</strong>
|
||||
Redis - Memcached - Aerospike</li>
|
||||
<li><strong>PHP Servers:</strong>
|
||||
|
|
|
|||
2458
docs/index.xml
2458
docs/index.xml
File diff suppressed because it is too large
Load Diff
|
|
@ -10,7 +10,7 @@
|
|||
<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>Introduction - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -218,9 +218,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
@ -404,7 +404,7 @@ You can turn On/Off as many instances of as any container without worrying about
|
|||
|
||||
<ul>
|
||||
<li><strong>Database Engines:</strong>
|
||||
MySQL - MariaDB - MongoDB - Neo4j - RethinkDB - MSSQL - PostgreSQL - Postgres Postgis.</li>
|
||||
MySQL - MariaDB - Percona - MongoDB - Neo4j - RethinkDB - MSSQL - PostgreSQL - Postgres Postgis.</li>
|
||||
<li><strong>Cache Engines:</strong>
|
||||
Redis - Memcached - Aerospike</li>
|
||||
<li><strong>PHP Servers:</strong>
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Introductions on Laradock</title>
|
||||
<link>http://laradock.io/introduction/index.xml</link>
|
||||
<link>http://laradock.io/introduction.html</link>
|
||||
<description>Recent content in Introductions on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/introduction/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/introduction/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Introduction</title>
|
||||
|
|
@ -14,144 +16,10 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/introduction/</guid>
|
||||
<description>
|
||||
|
||||
<p>A full PHP development environment for Docker.</p>
|
||||
|
||||
<p>Includes pre-packaged Docker Images, all pre-configured to provide a wonderful PHP development environment.</p>
|
||||
|
||||
<p>Laradock is well known in the Laravel community, as the project started with single focus on running Laravel projects on Docker. Later and due to the large adoption from the PHP community, it started supporting other PHP projects like Symfony, CodeIgniter, WordPress, Drupal&hellip;</p>
|
||||
|
||||
<p><img src="https://s19.postimg.org/jblfytw9f/laradock-logo.jpg" alt="" /></p>
|
||||
|
||||
<h2 id="quick-overview">Quick Overview</h2>
|
||||
|
||||
<p>Let&rsquo;s see how easy it is to install <code>NGINX</code>, <code>PHP</code>, <code>Composer</code>, <code>MySQL</code>, <code>Redis</code> and <code>Beanstalkd</code>:</p>
|
||||
|
||||
<p>1 - Clone Laradock inside your PHP project:</p>
|
||||
|
||||
<pre><code class="language-shell">git clone https://github.com/Laradock/laradock.git
|
||||
</code></pre>
|
||||
|
||||
<p>2 - Enter the laradock folder and rename <code>env-example</code> to <code>.env</code>.</p>
|
||||
|
||||
<pre><code class="language-shell">cp env-example .env
|
||||
</code></pre>
|
||||
|
||||
<p>3 - Run your containers:</p>
|
||||
|
||||
<pre><code class="language-shell">docker-compose up -d nginx mysql redis beanstalkd
|
||||
</code></pre>
|
||||
|
||||
<p>4 - Open your project&rsquo;s <code>.env</code> file and set the following:</p>
|
||||
|
||||
<pre><code class="language-shell">DB_HOST=mysql
|
||||
REDIS_HOST=redis
|
||||
QUEUE_HOST=beanstalkd
|
||||
</code></pre>
|
||||
|
||||
<p>5 - Open your browser and visit localhost: <code>http://localhost</code>.</p>
|
||||
|
||||
<pre><code class="language-shell">That's it! enjoy :)
|
||||
</code></pre>
|
||||
|
||||
<p><a name="features"></a></p>
|
||||
|
||||
<h2 id="features">Features</h2>
|
||||
|
||||
<ul>
|
||||
<li>Easy switch between PHP versions: 7.1, 7.0, 5.6&hellip;</li>
|
||||
<li>Choose your favorite database engine: MySQL, Postgres, MariaDB&hellip;</li>
|
||||
<li>Run your own combination of software: Memcached, HHVM, Beanstalkd&hellip;</li>
|
||||
<li>Every software runs on a separate container: PHP-FPM, NGINX, PHP-CLI&hellip;</li>
|
||||
<li>Easy to customize any container, with simple edit to the <code>Dockerfile</code>.</li>
|
||||
<li>All Images extends from an official base Image. (Trusted base Images).</li>
|
||||
<li>Pre-configured NGINX to host any code at your root directory.</li>
|
||||
<li>Can use Laradock per project, or single Laradock for all projects.</li>
|
||||
<li>Easy to install/remove software&rsquo;s in Containers using environment variables.</li>
|
||||
<li>Clean and well structured Dockerfiles (<code>Dockerfile</code>).</li>
|
||||
<li>Latest version of the Docker Compose file (<code>docker-compose</code>).</li>
|
||||
<li>Everything is visible and editable.</li>
|
||||
<li>Fast Images Builds.</li>
|
||||
<li>More to come every week..</li>
|
||||
</ul>
|
||||
|
||||
<p><a name="Supported-Containers"></a></p>
|
||||
|
||||
<h2 id="supported-software-images">Supported Software (Images)</h2>
|
||||
|
||||
<p>In adhering to the separation of concerns principle as promoted by Docker, Laradock runs each software on its own Container.
|
||||
You can turn On/Off as many instances of as any container without worrying about the configurations, everything works like a charm.</p>
|
||||
|
||||
<ul>
|
||||
<li><strong>Database Engines:</strong>
|
||||
MySQL - MariaDB - MongoDB - Neo4j - RethinkDB - MSSQL - PostgreSQL - Postgres Postgis.</li>
|
||||
<li><strong>Cache Engines:</strong>
|
||||
Redis - Memcached - Aerospike</li>
|
||||
<li><strong>PHP Servers:</strong>
|
||||
NGINX - Apache2 - Caddy</li>
|
||||
<li><strong>PHP Compilers:</strong>
|
||||
PHP FPM - HHVM</li>
|
||||
<li><strong>Message Queuing:</strong>
|
||||
Beanstalkd - Beanstalkd Console - RabbitMQ - RabbitMQ Console - PHP Worker</li>
|
||||
<li><strong>Tools:</strong>
|
||||
HAProxy - Jenkins - ElasticSearch - Selenium - Certbot - Mailhog - Minio - Varnish - PhpMyAdmin - Adminer - PgAdmin - MailHog&hellip;</li>
|
||||
</ul>
|
||||
|
||||
<p>Laradock introduces the <strong>Workspace</strong> Image, as a development environment.
|
||||
It contains a rich set of helpful tools, all pre-configured to work and integrate with almost any combination of Containers and tools you may choose.</p>
|
||||
|
||||
<p><strong>Workspace Image Tools</strong>
|
||||
PHP CLI - Composer - Git - Linuxbrew - Node - V8JS - Gulp - SQLite - xDebug - Envoy - Deployer - Vim - Yarn - SOAP - Drush&hellip;</p>
|
||||
|
||||
<p>You can choose, which tools to install in your workspace container and other containers, from the <code>.env</code> file.</p>
|
||||
|
||||
<blockquote>
|
||||
<p>If you modify <code>docker-compose.yml</code>, <code>.env</code> or any <code>dockerfile</code> file, you must re-build your containers, to see those effects in the running instance.</p>
|
||||
</blockquote>
|
||||
|
||||
<p>If you can&rsquo;t find your Software in the list, build it yourself and sumit it. Contributions are welcomed :)</p>
|
||||
|
||||
<p><a name="what-is-docker"></a></p>
|
||||
|
||||
<h2 id="what-is-docker">What is Docker?</h2>
|
||||
|
||||
<p><a href="https://www.docker.com">Docker</a> is an open-source project that automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of <a href="https://en.wikipedia.org/wiki/Operating-system-level_virtualization">operating-system-level virtualization</a> on Linux, Mac OS and Windows.</p>
|
||||
|
||||
<p><a name="why-docker-not-vagrant"></a></p>
|
||||
|
||||
<h2 id="why-docker-not-vagrant">Why Docker not Vagrant!?</h2>
|
||||
|
||||
<p><a href="https://www.vagrantup.com">Vagrant</a> creates Virtual Machines in minutes while Docker creates Virtual Containers in seconds.</p>
|
||||
|
||||
<p>Instead of providing a full Virtual Machines, like you get with Vagrant, Docker provides you <strong>lightweight</strong> Virtual Containers, that share the same kernel and allow to safely execute independent processes.</p>
|
||||
|
||||
<p>In addition to the speed, Docker gives tons of features that cannot be achieved with Vagrant.</p>
|
||||
|
||||
<p>Most importantly Docker can run on Development and on Production (same environment everywhere). While Vagrant is designed for Development only, (so you have to re-provision your server on Production every time).</p>
|
||||
|
||||
<p><a name="Demo"></a></p>
|
||||
|
||||
<h2 id="demo-video">Demo Video</h2>
|
||||
|
||||
<p>What&rsquo;s better than a <strong>Demo Video</strong>:</p>
|
||||
|
||||
<ul>
|
||||
<li>Laradock v5.* (soon or never)</li>
|
||||
<li>Laradock <a href="https://www.youtube.com/watch?v=TQii1jDa96Y">v4.*</a></li>
|
||||
<li>Laradock <a href="https://www.youtube.com/watch?v=-DamFMczwDA">v2.*</a></li>
|
||||
<li>Laradock <a href="https://www.youtube.com/watch?v=jGkyO6Is_aI">v0.3</a></li>
|
||||
<li>Laradock <a href="https://www.youtube.com/watch?v=3YQsHe6oF80">v0.1</a></li>
|
||||
</ul>
|
||||
|
||||
<p><a name="Chat"></a></p>
|
||||
|
||||
<h2 id="chat-with-us">Chat with us</h2>
|
||||
|
||||
<p>You are welcome to join our chat room on Gitter.</p>
|
||||
|
||||
<p><a href="https://gitter.im/Laradock/laradock?utm_source=badge&amp;utm_medium=badge&amp;utm_campaign=pr-badge"><img src="https://badges.gitter.im/Laradock/laradock.svg" alt="Gitter" /></a></p>
|
||||
</description>
|
||||
<description>A full PHP development environment for Docker.
|
||||
Includes pre-packaged Docker Images, all pre-configured to provide a wonderful PHP development environment.
|
||||
Laradock is well known in the Laravel community, as the project started with single focus on running Laravel projects on Docker. Later and due to the large adoption from the PHP community, it started supporting other PHP projects like Symfony, CodeIgniter, WordPress, Drupal&hellip;
|
||||
Quick Overview Let&rsquo;s see how easy it is to install NGINX, PHP, Composer, MySQL, Redis and Beanstalkd:</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
<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>License - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -215,9 +215,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
@ -370,14 +370,14 @@
|
|||
|
||||
<div class="next">
|
||||
|
||||
<a href="http://laradock.io/contributing/" title="Contributings">
|
||||
<a href="http://laradock.io/" title="Welcome">
|
||||
<span class="direction">
|
||||
Next
|
||||
</span>
|
||||
<div class="page">
|
||||
<div class="stretch">
|
||||
<div class="title">
|
||||
Contributings
|
||||
Welcome
|
||||
</div>
|
||||
</div>
|
||||
<div class="button button-next" role="button" aria-label="Next">
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Licenses on Laradock</title>
|
||||
<link>http://laradock.io/license/index.xml</link>
|
||||
<link>http://laradock.io/license.html</link>
|
||||
<description>Recent content in Licenses on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/license/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/license/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>License</title>
|
||||
|
|
@ -14,8 +16,7 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/license/</guid>
|
||||
<description><p><a href="https://github.com/laradock/laradock/blob/master/LICENSE">MIT License</a> (MIT)</p>
|
||||
</description>
|
||||
<description>MIT License (MIT)</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
<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>Related Projects - Laradock</title>
|
||||
<meta name="generator" content="Hugo 0.19" />
|
||||
<meta name="generator" content="Hugo 0.20.2" />
|
||||
|
||||
|
||||
<meta name="description" content="Full PHP development environment for Docker.">
|
||||
|
|
@ -215,9 +215,9 @@
|
|||
|
||||
|
||||
|
||||
<a title="Giudes" href="http://laradock.io/guides/">
|
||||
<a title="Guides" href="http://laradock.io/guides/">
|
||||
|
||||
Giudes
|
||||
Guides
|
||||
</a>
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,11 +2,13 @@
|
|||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Related-projects on Laradock</title>
|
||||
<link>http://laradock.io/related-projects/index.xml</link>
|
||||
<link>http://laradock.io/related-projects.html</link>
|
||||
<description>Recent content in Related-projects on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
<atom:link href="http://laradock.io/related-projects/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
<atom:link href="http://laradock.io/related-projects/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
<item>
|
||||
<title>Related Projects</title>
|
||||
|
|
@ -14,21 +16,8 @@
|
|||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||||
|
||||
<guid>http://laradock.io/related-projects/</guid>
|
||||
<description><p>Laradock related projects:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://github.com/lorinlee/laradock-cli">Laradock CLI</a> by <a href="https://github.com/lorinlee">LorinLee</a></li>
|
||||
<li><a href="https://github.com/bagart/laradock_env">Laradock Env</a> by <a href="https://github.com/bagart">BAGArt</a></li>
|
||||
<li><a href="https://github.com/poyhsiao/Klaradock">Klaradock</a> by <a href="https://github.com/poyhsiao">Kim Hsiao</a></li>
|
||||
<li><a href="https://github.com/sifat-rahim/ansible-laradock-kubernetes">Ansible Laradock Kubernetes</a> by <a href="https://github.com/sifat-rahim">Sifat Rahim</a>
|
||||
These Docker Compose projects have piqued our interest:</li>
|
||||
<li><a href="https://github.com/ojhaujjwal/magedock">MageDock</a> by <a href="https://github.com/ojhaujjwal">Ujjwal Ojha</a></li>
|
||||
<li><a href="https://github.com/scudelletti/rubydev-dock">RubyDev-Dock</a> by <a href="https://github.com/scudelletti">Diogo Scudelletti</a></li>
|
||||
<li><a href="https://github.com/Osedea/nodock">NoDock</a> by <a href="https://github.com/Osedea">Osedea</a></li>
|
||||
</ul>
|
||||
|
||||
<p>If you want your project listed here, please open an issue.</p>
|
||||
</description>
|
||||
<description>Laradock related projects:
|
||||
Laradock CLI by LorinLee Laradock Env by BAGArt Klaradock by Kim Hsiao Ansible Laradock Kubernetes by Sifat Rahim These Docker Compose projects have piqued our interest: MageDock by Ujjwal Ojha RubyDev-Dock by Diogo Scudelletti NoDock by Osedea If you want your project listed here, please open an issue.</description>
|
||||
</item>
|
||||
|
||||
</channel>
|
||||
|
|
|
|||
|
|
@ -34,32 +34,37 @@
|
|||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/contributing/</loc>
|
||||
<loc>http://laradock.io/categories.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/documentation/</loc>
|
||||
<loc>http://laradock.io/contributing.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/getting-started/</loc>
|
||||
<loc>http://laradock.io/documentation.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/guides/</loc>
|
||||
<loc>http://laradock.io/getting-started.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/help/</loc>
|
||||
<loc>http://laradock.io/guides.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/introduction/</loc>
|
||||
<loc>http://laradock.io/help.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/introduction.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
|
|
@ -69,12 +74,17 @@
|
|||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/license/</loc>
|
||||
<loc>http://laradock.io/license.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/related-projects/</loc>
|
||||
<loc>http://laradock.io/related-projects.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>http://laradock.io/tags.html</loc>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,14 @@
|
|||
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>Tags on Laradock</title>
|
||||
<link>http://laradock.io/tags.html</link>
|
||||
<description>Recent content in Tags on Laradock</description>
|
||||
<generator>Hugo -- gohugo.io</generator>
|
||||
<language>en-us</language>
|
||||
|
||||
<atom:link href="http://laradock.io/tags/index.xml" rel="self" type="application/rss+xml" />
|
||||
|
||||
|
||||
</channel>
|
||||
</rss>
|
||||
Loading…
Reference in New Issue