diff --git a/.env b/.env
new file mode 100644
index 0000000..accd09a
--- /dev/null
+++ b/.env
@@ -0,0 +1 @@
+COMPOSE_CONVERT_WINDOWS_PATHS=1
diff --git a/.gitignore b/.gitignore
index 00571d7..7c6f11b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,3 @@
.idea
/logs
/data
-.env
diff --git a/README-zh.md b/README-zh.md
index e0853fb..f4f3912 100644
--- a/README-zh.md
+++ b/README-zh.md
@@ -7,9 +7,7 @@
LaraDock能够帮你在**Docker**上快速搭建**Laravel**应用。
就像Laravel Homestead一样,但是Docker替换了Vagrant。
->先在Docker上使用LaraDock,然后再学习它们。
-
-![](https://s31.postimg.org/nbettdki3/lara_dock_poster_new.jpg)
+> 先在使用 LaraDock,然后再学习它们。
## 目录
@@ -69,7 +67,7 @@ LaraDock努力简化创建开发环境过程。
1. 将LaraDock放到你的Laravel项目中:
-`git clone https://github.com/LaraDock/laradock.git`.
+`git clone https://github.com/laradock/laradock.git`.
2. 进入LaraDock目录,然后运行这些容器。
`docker-compose up -d nginx mysql redis`
@@ -155,7 +153,7 @@ Homestead 是一个工具,为你控制虚拟机(使用Homestead特殊命令)。V
## 演示视频
还有什么比**演示视频**好:
-- LaraDock v4.0 (即将到来的...)
+- LaraDock [v4.0](https://www.youtube.com/watch?v=TQii1jDa96Y)
- LaraDock [v2.2](https://www.youtube.com/watch?v=-DamFMczwDA)
- LaraDock [v0.3](https://www.youtube.com/watch?v=jGkyO6Is_aI)
- LaraDock [v0.1](https://www.youtube.com/watch?v=3YQsHe6oF80)
@@ -179,7 +177,7 @@ Homestead 是一个工具,为你控制虚拟机(使用Homestead特殊命令)。V
**A)** 如果你已经有一个Laravel项目,克隆这个仓库在到`Laravel`根目录
```bash
-git submodule add https://github.com/LaraDock/laradock.git
+git submodule add https://github.com/laradock/laradock.git
```
>如果你不是使用Git管理Laravel项目,您可以使用 `git clone` 而不是`git submodule`。
@@ -187,7 +185,7 @@ git submodule add https://github.com/LaraDock/laradock.git
**B)** 如果你没有一个Laravel项目,你想Docker安装Laravel,克隆这个源在您的机器任何地方上:
```bash
-git clone https://github.com/LaraDock/laradock.git
+git clone https://github.com/laradock/laradock.git
```
@@ -198,8 +196,8 @@ git clone https://github.com/LaraDock/laradock.git
**请在开始之前阅读:**
如果你正在使用**Docker Toolbox** (VM),选择以下任何一个方法:
-- 更新到Docker [Native](https://www.docker.com/products/docker) Mac/Windows版本 (建议). 查看 [Upgrading Laradock](#upgrading-laradock)
-- 使用 LaraDock v3.* (访问 `LaraDock-ToolBox` [分支](https://github.com/LaraDock/laradock/tree/LaraDock-ToolBox)).
+- 更新到Docker [Native](https://www.docker.com/products/docker) Mac/Windows版本 (建议). 查看 [Upgrading LaraDock](#upgrading-laradock)
+- 使用 LaraDock v3.* (访问 `LaraDock-ToolBox` [分支](https://github.com/laradock/laradock/tree/LaraDock-ToolBox)).
如果您使用的是**Docker Native**(Mac / Windows版本)甚至是Linux版本,通常可以继续阅读这个文档,LaraDock v4以上版本将仅支持**Docker Native**。
@@ -471,7 +469,7 @@ composer create-project laravel/laravel my-cool-app "5.2.*"
系统默认LaraDock假定Laravel应用在LaraDock的父级目录中
By default LaraDock assumes the Laravel application is living in the parent directory of the laradock folder.
-自新Laravel应用在 `my-cool-app` 目录中, 我们需要用 `../my-cool-app/:/var/www`替换 `../:/var/www` , 如下:
+更新Laravel应用在 `my-cool-app` 目录中, 我们需要用 `../my-cool-app/:/var/www`替换 `../:/var/www` , 如下:
```yaml
application:
@@ -722,7 +720,7 @@ docker-compose build php
#### B) 切换版本 PHP `7.0` 或 `5.6` 到 PHP `5.5`
我们已不在本地支持PHP5.5,但是你按照以下步骤获取:
-1 - 克隆 `https://github.com/LaraDock/php-fpm`.
+1 - 克隆 `https://github.com/laradock/php-fpm`.
3 - 重命名 `Dockerfile-56` 为 `Dockerfile-55`.
@@ -940,7 +938,7 @@ sudo chmod -R 777 storage bootstrap/cache
## 贡献
这个小项目是由一个有一个全职工作和很多的职责的人建立的,所以如果你喜欢这个项目,并且发现它需要一个bug修复或支持或新软件或升级任何容器,或其他任何. . 你是非常欢迎,欢迎毫不不犹豫地贡献吧:)
-#### 阅读我们的 [贡献说明](https://github.com/LaraDock/laradock/blob/master/CONTRIBUTING.md)
+#### 阅读我们的 [贡献说明](https://github.com/laradock/laradock/blob/master/CONTRIBUTING.md)
## 帮助 & 问题
@@ -959,8 +957,8 @@ Docker或Laravel的特别帮助,你可以在[Codementor.io](https://www.codeme
**优秀的人:**
-- [Contributors](https://github.com/LaraDock/laradock/graphs/contributors)
-- [Supporters](https://github.com/LaraDock/laradock/issues?utf8=%E2%9C%93&q=)
+- [Contributors](https://github.com/laradock/laradock/graphs/contributors)
+- [Supporters](https://github.com/laradock/laradock/issues?utf8=%E2%9C%93&q=)
## 许可证
diff --git a/README.md b/README.md
index 0df8bc9..9cad0e8 100644
--- a/README.md
+++ b/README.md
@@ -1,1440 +1,28 @@
# Laradock
+> Use Docker first and learn about it later.
+
[![forthebadge](http://forthebadge.com/images/badges/built-by-developers.svg)](http://zalt.me)
-[![Gitter](https://badges.gitter.im/LaraDock/laradock.svg)](https://gitter.im/LaraDock/laradock?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
+Laradock is a Docker PHP development environment that facilitate running **PHP** Apps on **Docker**.
-Laradock is a Docker PHP development environment. It facilitate running **PHP** Apps on **Docker**.
-
-Laradock is configured to run Laravel Apps by default, and it can be modifyed to run all kinds of PHP Apps (Symfony, Codeigniter, Wordpress, Drupal...).
-
->Use Docker first and learn about it later.
-
-## Contents
-
-- [Readme Languages](#)
- - [English (Default)](#)
- - [Chinese](https://github.com/LaraDock/laradock/blob/master/README-zh.md)
-- [Intro](#Intro)
- - [Features](#features)
- - [Supported Software](#Supported-Containers)
- - [What is Docker](#what-is-docker)
- - [Why Docker not Vagrant](#why-docker-not-vagrant)
- - [Laradock VS Homestead](#laradock-vs-homestead)
-- [Demo Video](#Demo)
-- [Requirements](#Requirements)
-- [Installation](#Installation)
-- [Usage](#Usage)
-- [Documentation](#Documentation)
- - [Docker](#Docker)
- - [List current running Containers](#List-current-running-Containers)
- - [Close all running Containers](#Close-all-running-Containers)
- - [Delete all existing Containers](#Delete-all-existing-Containers)
- - [Enter a Container (run commands in a running Container)](#Enter-Container)
- - [Edit default container configuration](#Edit-Container)
- - [Edit a Docker Image](#Edit-a-Docker-Image)
- - [Build/Re-build Containers](#Build-Re-build-Containers)
- - [Add more Software (Docker Images)](#Add-Docker-Images)
- - [View the Log files](#View-the-Log-files)
- - [PHP](#PHP)
- - [Install PHP Extensions](#Install-PHP-Extensions)
- - [Change the PHP-FPM Version](#Change-the-PHP-FPM-Version)
- - [Change the PHP-CLI Version](#Change-the-PHP-CLI-Version)
- - [Install xDebug](#Install-xDebug)
- - [Start/Stop xDebug](#Controll-xDebug)
- - [Production](#Production)
- - [Prepare LaraDock for Production](#LaraDock-for-Production)
- - [Setup Laravel and Docker on Digital Ocean](#Digital-Ocean)
- - [Laravel](#Laravel):
- - [Install Laravel from a Docker Container](#Install-Laravel)
- - [Run Artisan Commands](#Run-Artisan-Commands)
- - [Use Redis](#Use-Redis)
- - [Use Mongo](#Use-Mongo)
- - [Use phpMyAdmin](#Use-phpMyAdmin)
- - [Use pgAdmin](#Use-pgAdmin)
- - [Use ElasticSearch](#Use-ElasticSearch)
- - [Codeigniter](#Codeigniter):
- - [Install Codeigniter](#Install-Codeigniter)
- - [Misc](#Misc)
- - [Change the timezone](#Change-the-timezone)
- - [Cron jobs](#CronJobs)
- - [Access workspace via ssh](#Workspace-ssh)
- - [MySQL access from host](#MySQL-access-from-host)
- - [MySQL root access](#MySQL-root-access)
- - [Use custom Domain](#Use-custom-Domain)
- - [Enable Global Composer Build Install](#Enable-Global-Composer-Build-Install)
- - [Install Prestissimo](#Install-Prestissimo)
- - [Install Node + NVM](#Install-Node)
- - [Install Node + YARN](#Install-Yarn)
- - [Debugging](#debugging)
- - [Upgrading LaraDock](#upgrading-laradock)
-- [Help & Questions](#Help)
-
-
-
-
-## Intro
-
-Laradock strives to make the PHP development experience easier and faster.
-
-It contains pre-packaged Docker Images that provides you a wonderful *development* environment without requiring you to install PHP, NGINX, MySQL, REDIS, and any other software on your machines.
-
-
-**Usage Overview:**
-
-Let's see how easy it is to install `NGINX`, `PHP`, `Composer`, `MySQL` and `Redis`. Then run `Laravel`.
-
-1. Get LaraDock inside your Laravel project:
-
-`git clone https://github.com/LaraDock/laradock.git`.
-2. Enter the laradock folder and run only these Containers:
-
-`docker-compose up -d nginx mysql redis`
-3. Open your `.env` file and set `DB_HOST` to `mysql` and `REDIS_HOST` to `redis`.
-4. Open your browser and visit the localhost: `http://localdock`
-
-
-
-
-### Features
-
-- Easy switch between PHP versions: 7.0, 5.6, 5.5...
-- Choose your favorite database engine: MySQL, Postgres, MariaDB...
-- Run your own combination of software: Memcached, HHVM, Beanstalkd...
-- Every software runs on a separate container: PHP-FPM, NGINX, PHP-CLI...
-- Easy to customize any container, with simple edit to the `dockerfile`.
-- All Images extends from an official base Image. (Trusted base Images).
-- Pre-configured Nginx for Laravel.
-- Easy to apply configurations inside containers.
-- Clean and well structured Dockerfiles (`dockerfile`).
-- Latest version of the Docker Compose file (`docker-compose`).
-- Everything is visible and editable.
-- Fast Images Builds.
-- More to come every week..
-
-
-
-### Supported Software (Containers)
-
-- **Database Engines:**
- - MySQL
- - PostgreSQL
- - MariaDB
- - MongoDB
- - Neo4j
-- **Cache Engines:**
- - Redis
- - Memcached
- - Aerospike
-- **PHP Servers:**
- - NGINX
- - Apache2
- - Caddy
-- **PHP Compilers:**
- - PHP-FPM
- - HHVM
-- **Message Queueing Systems:**
- - Beanstalkd (+ Beanstalkd Console)
- - RabbitMQ (+ RabbitMQ Console)
-- **Tools:**
- - Workspace (PHP7-CLI, Composer, Git, Node, Gulp, SQLite, xDebug, Vim...)
- - PhpMyAdmin
- - PgAdmin
- - ElasticSearch
-
-
->If you can't find your Software, build it yourself and add it to this list. Contributions are welcomed :)
-
-
-
-
-
-
-### What is Docker?
-
-[Docker](https://www.docker.com) is an open-source project that automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of [operating-system-level virtualization](https://en.wikipedia.org/wiki/Operating-system-level_virtualization) on Linux, Mac OS and Windows.
-
-
-
-### Why Docker not Vagrant!?
-
-[Vagrant](https://www.vagrantup.com) creates Virtual Machines in minutes while Docker creates Virtual Containers in seconds.
-
-Instead of providing a full Virtual Machines, like you get with Vagrant, Docker provides you **lightweight** Virtual Containers, that share the same kernel and allow to safely execute independent processes.
-
-In addition to the speed, Docker gives tons of features that cannot be achieved with Vagrant.
-
-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).
-
-
-
-### Laradock VS Homestead (For Laravel Developers)
-
-> Laradock It's like Laravel Homestead but for Docker instead of Vagrant.
-
-Laradock and [Homestead](https://laravel.com/docs/master/homestead) both gives you a complete virtual development environments. (Without the need to install and configure every single software on your own Operating System).
-
-- Homestead is a tool that controls Vagrant for you (using Homestead special commands). And Vagrant manages your Virtual Machine.
-
-- LaraDock is a tool that controls Docker for you (using Docker & Docker Compose official commands). And Docker manages your Virtual Containers.
-
-Running a virtual Container is much faster than running a full virtual Machine. Thus **LaraDock is much faster than Homestead**.
-
-
-
-
-
-
-## Demo Video
-
-What's better than a **Demo Video**:
-
-- LaraDock [v4.*](https://www.youtube.com/watch?v=TQii1jDa96Y)
-- LaraDock [v2.*](https://www.youtube.com/watch?v=-DamFMczwDA)
-- LaraDock [v0.3](https://www.youtube.com/watch?v=jGkyO6Is_aI)
-- LaraDock [v0.1](https://www.youtube.com/watch?v=3YQsHe6oF80)
-
-
-
-
-## Requirements
-
-- [Git](https://git-scm.com/downloads)
-- [Docker](https://www.docker.com/products/docker/) `>= 1.12`
-
-
-
-
-## Installation
-
-Choose the setup the best suits your needs.
-
-#### A) Setup for Single Project:
-*(In case you want a Docker environment for each project)*
-
-##### A.1) Setup environment in existing Project:
-*(In case you already have a project, and you want to setup an environemnt to run it)*
-
-1 - Clone this repository on your project root directory:
-
-```bash
-git submodule add https://github.com/LaraDock/laradock.git
-```
->If you are not already using Git for your PHP project, you can use `git clone` instead of `git submodule`.
-
-Note: In this case the folder structure will be like this:
-
-```
-- project1
- - laradock
-- project2
- - laradock
-```
-
-##### A.2) Setup environment first then create project:
-*(In case you don't have a project, and you want to create your project inside the Docker environment)*
-
-1 - Clone this repository anywhere on your machine:
-
-```bash
-git clone https://github.com/LaraDock/laradock.git
-```
-Note: In this case the folder structure will be like this:
-
-```
-- projects
- - laradock
- - myProject
-```
-
-2 - Edit the `docker-compose.yml` file to map to your project directory once you have it (example: `- ../myProject:/var/www`).
-
-3 - Stop and re-run your docker-compose command for the changes to take place.
-
-```
-docker-compose stop && docker-compose up -d XXXX YYYY ZZZZ ....
-```
-
-
-#### B) Setup for Multiple Projects:
-
-1 - Clone this repository anywhere on your machine:
-
-```bash
-git clone https://github.com/LaraDock/laradock.git
-```
-
-2 - Edit the `docker-compose.yml` file to map to your projects directories:
-
-```
- applications:
- image: tianon/true
- volumes:
- - ../project1/:/var/www/project1
- - ../project2/:/var/www/project2
-```
-
-3 - You can access all sites by visiting `http://localhost/project1/public` and `http://localhost/project2/public` but of course that's not very useful so let's setup nginx quickly.
-
-
-4 - Go to `nginx/sites` and copy `sample.conf.example` to `project1.conf` then to `project2.conf`
-
-5 - Open the `project1.conf` file and edit the `server_name` and the `root` as follow:
-
-```
- server_name project1.dev;
- root /var/www/project1/public;
-```
-Do the same for each project `project2.conf`, `project3.conf`,...
-
-6 - Create your project Databases **To Be Continue..**
-
-
-
-
-
-
-## Usage
-
-
-**Read Before starting:**
-
-If you are using **Docker Toolbox** (VM), do one of the following:
-
-- Upgrade to Docker [Native](https://www.docker.com/products/docker) for Mac/Windows (Recommended). Check out [Upgrading Laradock](#upgrading-laradock)
-- Use LaraDock v3.* (Visit the `LaraDock-ToolBox` [Branch](https://github.com/LaraDock/laradock/tree/LaraDock-ToolBox)).
-
-
-
->**Warning:** If you used an older version of LaraDock it's highly recommended to rebuild the containers you need to use [see how you rebuild a container](#Build-Re-build-Containers) in order to prevent errors as much as possible.
-
-
-
-1 - Run Containers: *(Make sure you are in the `laradock` folder before running the `docker-compose` commands).*
-
-
-
-**Example:** Running NGINX and MySQL:
-
-```bash
-docker-compose up -d nginx mysql
-```
-
-**Note**: The `workspace` and `php-fpm` will run automatically in most of the cases, so no need to specify them in the `up` command. If you couldn't find them running then you need specify them as follow: `docker-compose up -d nginx php-fpm mysql workspace`.
-
-
-You can select your own combination of Containers form the list below:
-
-`nginx`, `hhvm`, `php-fpm`, `mysql`, `redis`, `postgres`, `mariadb`, `neo4j`, `mongo`, `apache2`, `caddy`, `memcached`, `beanstalkd`, `beanstalkd-console`, `rabbitmq`, `workspace`, `phpmyadmin`, `aerospike`, `pgadmin`, `elasticsearch`.
-
-
-
-
-
-2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, ...).
-
-```bash
-docker-compose exec workspace bash
-```
-Alternatively, for Windows Powershell users: execute the following command to enter any running container:
-
-```bash
-docker exec -it {workspace-container-id} bash
-```
-
-**Note:** You can add `--user=laradock` (example `docker-compose exec --user=laradock workspace bash`) to have files created as your host's user. (you can change the PUID (User id) and PGID (group id) variables from the `docker-compose.yml`).
-
-
-
-
-3 - Edit your project configurations.
-
-Open your `.env` file and set the `DB_HOST` to `mysql`:
-
-```env
-DB_HOST=mysql
-```
-
-*If you want to use Laravel and you don't have it installed yet, see [How to Install Laravel in a Docker Container](#Install-Laravel).*
-
-
-
-
-
-4 - Open your browser and visit your localhost address (`http://localhost/`).
-
-
-
-
-**Debugging**: if you are facing any problem here check the [Debugging](#debugging) section.
-
-If you need a special support. Contact me, more details in the [Help & Questions](#Help) section.
-
-
-
-
## Documentation
-
-
-
-
-
-
-
-### List current running Containers
-```bash
-docker ps
-```
-You can also use the this command if you want to see only this project containers:
-
-```bash
-docker-compose ps
-```
-
-
-
-
-
-
-
-### Close all running Containers
-```bash
-docker-compose stop
-```
-
-To stop single container do:
-
-```bash
-docker-compose stop {container-name}
-```
-
-
-
-
-
-
-
-
-### Delete all existing Containers
-```bash
-docker-compose down
-```
-
-
-
-
-
-
-
-
-
-### Enter a Container (run commands in a running Container)
-
-1 - first list the current running containers with `docker ps`
-
-2 - enter any container using:
-
-```bash
-docker-compose exec {container-name} bash
-```
-
-*Example: enter MySQL container*
-
-```bash
-docker-compose exec mysql bash
-```
-
-3 - to exit a container, type `exit`.
-
-
-
-
-
-
-
-
-
-### Edit default container configuration
-Open the `docker-compose.yml` and change anything you want.
-
-Examples:
-
-Change MySQL Database Name:
-
-```yml
- environment:
- MYSQL_DATABASE: laradock
- ...
-```
-
-Change Redis defaut port to 1111:
-
-```yml
- ports:
- - "1111:6379"
- ...
-```
-
-
-
-
-
-
-
-
-
-
-### Edit a Docker Image
-
-1 - Find the `dockerfile` of the image you want to edit,
-
-example for `mysql` it will be `mysql/Dockerfile`.
-
-2 - Edit the file the way you want.
-
-3 - Re-build the container:
-
-```bash
-docker-compose build mysql
-```
-More info on Containers rebuilding [here](#Build-Re-build-Containers).
-
-
-
-
-
-
-
-
-
-
-### Build/Re-build Containers
-
-If you do any change to any `dockerfile` make sure you run this command, for the changes to take effect:
-
-```bash
-docker-compose build
-```
-Optionally you can specify which container to rebuild (instead of rebuilding all the containers):
-
-```bash
-docker-compose build {container-name}
-```
-
-You might use the `--no-cache` option if you want full rebuilding (`docker-compose build --no-cache {container-name}`).
-
-
-
-
-
-
-
-### Add more Software (Docker Images)
-
-To add an image (software), just edit the `docker-compose.yml` and add your container details, to do so you need to be familiar with the [docker compose file syntax](https://docs.docker.com/compose/compose-file/).
-
-
-
-
-
-
-
-
-
-
-
-### View the Log files
-The Nginx Log file is stored in the `logs/nginx` directory.
-
-However to view the logs of all the other containers (MySQL, PHP-FPM,...) you can run this:
-
-```bash
-docker logs {container-name}
-```
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Install PHP Extensions
-
-Before installing PHP extensions, you have to decide whether you need for the `FPM` or `CLI` because each lives on a different container, if you need it for both you have to edit both containers.
-
-The PHP-FPM extensions should be installed in `php-fpm/Dockerfile-XX`. *(replace XX with your default PHP version number)*.
-
-The PHP-CLI extensions should be installed in `workspace/Dockerfile`.
-
-
-
-
-
-
-
-
-
-
-
-### Change the (PHP-FPM) Version
-By default **PHP-FPM 7.0** is running.
-
->The PHP-FPM is responsible of serving your application code, you don't have to change the PHP-CLI version if you are planing to run your application on different PHP-FPM version.
-
-#### A) Switch from PHP `7.0` to PHP `5.6`
-
-1 - Open the `docker-compose.yml`.
-
-2 - Search for `Dockerfile-70` in the PHP container section.
-
-3 - Change the version number, by replacing `Dockerfile-70` with `Dockerfile-56`, like this:
-
-```yml
- php-fpm:
- build:
- context: ./php-fpm
- dockerfile: Dockerfile-70
- ...
-```
-
-4 - Finally rebuild the container
-
-```bash
-docker-compose build php
-```
-
-> For more details about the PHP base image, visit the [official PHP docker images](https://hub.docker.com/_/php/).
-
-
-#### B) Switch from PHP `7.0` or `5.6` to PHP `5.5`
-
-We do not natively support PHP 5.5 anymore, but you can get it in few steps:
-
-1 - Clone `https://github.com/LaraDock/php-fpm`.
-
-3 - Rename `Dockerfile-56` to `Dockerfile-55`.
-
-3 - Edit the file `FROM php:5.6-fpm` to `FROM php:5.5-fpm`.
-
-4 - Build an image from `Dockerfile-55`.
-
-5 - Open the `docker-compose.yml` file.
-
-6 - Point `php-fpm` to your `Dockerfile-55` file.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Change the PHP-CLI Version
-By default **PHP-CLI 7.0** is running.
-
->Note: it's not very essential to edit the PHP-CLI verion. The PHP-CLI is only used for the Artisan Commands & Composer. It doesn't serve your Application code, this is the PHP-FPM job.
-
-The PHP-CLI is installed in the Workspace container. To change the PHP-CLI version you need to edit the `workspace/Dockerfile`.
-
-Right now you have to manually edit the `Dockerfile` or create a new one like it's done for the PHP-FPM. (consider contributing).
-
-
-
-
-
-
-### Install xDebug
-
-1 - First install `xDebug` in the Workspace and the PHP-FPM Containers:
-
-a) open the `docker-compose.yml` file
-
-b) search for the `INSTALL_XDEBUG` argument under the Workspace Container
-
-c) set it to `true`
-
-d) search for the `INSTALL_XDEBUG` argument under the PHP-FPM Container
-
-e) set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - INSTALL_XDEBUG=true
- ...
- php-fpm:
- build:
- context: ./php-fpm
- args:
- - INSTALL_XDEBUG=true
- ...
-```
-
-2 - Re-build the containers `docker-compose build workspace php-fpm`
-
-3 - Open `laradock/workspace/xdebug.ini` and/or `laradock/php-fpm/xdebug.ini` and enable at least the following configs:
-
-```
-xdebug.remote_autostart=1
-xdebug.remote_enable=1
-xdebug.remote_connect_back=1
-```
-
-For information on how to configure xDebug with your IDE and work it out, check this [Repository](https://github.com/LarryEitel/laravel-laradock-phpstorm).
-
-
-
-
-### Start/Stop xDebug:
-
-By installing xDebug, you are enabling it to run on startup by default.
-
-To controll the behavior of xDebug (in the `php-fpm` Container), you can run the following commands from the LaraDock root folder, (at the same prompt where you run docker-compose):
-
-- Stop xDebug from running by default: `./xdebugPhpFpm stop`.
-- Start xDebug by default: `./xdebugPhpFpm start`.
-- See the status: `./xdebugPhpFpm status`.
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Prepare LaraDock for Production
-
-It's recommended for production to create a custom `docker-compose.yml` file. For that reason LaraDock is shipped with `production-docker-compose.yml` which should contain only the containers you are planning to run on production (usage exampe: `docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...`).
-
-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:
-
-```
-ports:
- - "3306:3306"
-```
-
-To learn more about how Docker publishes ports, please read [this excellent post on the subject](https://fralef.me/docker-and-iptables.html).
-
-
-
-
-
-
-
-
-### Setup Laravel and Docker on Digital Ocean
-
-####[Full Guide Here](https://github.com/LaraDock/laradock/blob/master/_guides/digital_ocean.md)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Install Laravel from a Docker Container
-
-1 - First you need to enter the Workspace Container.
-
-2 - Install Laravel.
-
-Example using Composer
-
-```bash
-composer create-project laravel/laravel my-cool-app "5.2.*"
-```
-
-> We recommend using `composer create-project` instead of the Laravel installer, to install Laravel.
-
-For more about the Laravel installation click [here](https://laravel.com/docs/master#installing-laravel).
-
-
-3 - Edit `docker-compose.yml` to Map the new application path:
-
-By default LaraDock assumes the Laravel application is living in the parent directory of the laradock folder.
-
-Since the new Laravel application is in the `my-cool-app` folder, we need to replace `../:/var/www` with `../my-cool-app/:/var/www`, as follow:
-
-```yaml
- application:
- image: tianon/true
- volumes:
- - ../my-cool-app/:/var/www
- ...
-```
-4 - Go to that folder and start working..
-
-```bash
-cd my-cool-app
-```
-
-5 - Go back to the laraDock installation steps to see how to edit the `.env` file.
-
-
-
-
-
-### Run Artisan Commands
-
-You can run artisan commands and many other Terminal commands from the Workspace container.
-
-1 - Make sure you have the workspace container running.
-
-```bash
-docker-compose up -d workspace // ..and all your other containers
-```
-
-2 - Find the Workspace container name:
-
-```bash
-docker-compose ps
-```
-
-3 - Enter the Workspace container:
-
-```bash
-docker-compose exec workspace bash
-```
-
-Add `--user=laradock` (example `docker-compose exec --user=laradock workspace bash`) to have files created as your host's user.
-
-
-4 - Run anything you want :)
-
-```bash
-php artisan
-```
-```bash
-Composer update
-```
-```bash
-phpunit
-```
-
-
-
-### Use Redis
-
-1 - First make sure you run the Redis Container (`redis`) with the `docker-compose up` command.
-
-```bash
-docker-compose up -d redis
-```
-
-2 - Open your Laravel's `.env` file and set the `REDIS_HOST` to `redis`
-
-```env
-REDIS_HOST=redis
-```
-
-If you don't find the `REDIS_HOST` variable in your `.env` file. Go to the database config file `config/database.php` and replace the default `127.0.0.1` IP with `redis` for Redis like this:
-
-```php
-'redis' => [
- 'cluster' => false,
- 'default' => [
- 'host' => 'redis',
- 'port' => 6379,
- 'database' => 0,
- ],
-],
-```
-
-3 - To enable Redis Caching and/or for Sessions Management. Also from the `.env` file set `CACHE_DRIVER` and `SESSION_DRIVER` to `redis` instead of the default `file`.
-
-```env
-CACHE_DRIVER=redis
-SESSION_DRIVER=redis
-```
-
-4 - Finally make sure you have the `predis/predis` package `(~1.0)` installed via Composer:
-
-```bash
-composer require predis/predis:^1.0
-```
-
-5 - You can manually test it from Laravel with this code:
-
-```php
-\Cache::store('redis')->put('LaraDock', 'Awesome', 10);
-```
-
-
-
-
-
-
-
-### Use Mongo
-
-1 - First install `mongo` in the Workspace and the PHP-FPM Containers:
-
-a) open the `docker-compose.yml` file
-
-b) search for the `INSTALL_MONGO` argument under the Workspace Container
-
-c) set it to `true`
-
-d) search for the `INSTALL_MONGO` argument under the PHP-FPM Container
-
-e) set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - INSTALL_MONGO=true
- ...
- php-fpm:
- build:
- context: ./php-fpm
- args:
- - INSTALL_MONGO=true
- ...
-```
-
-2 - Re-build the containers `docker-compose build workspace php-fpm`
-
-
-
-3 - Run the MongoDB Container (`mongo`) with the `docker-compose up` command.
-
-```bash
-docker-compose up -d mongo
-```
-
-
-4 - Add the MongoDB configurations to the `config/database.php` config file:
-
-```php
-'connections' => [
-
- 'mongodb' => [
- 'driver' => 'mongodb',
- 'host' => env('DB_HOST', 'localhost'),
- 'port' => env('DB_PORT', 27017),
- 'database' => env('DB_DATABASE', 'database'),
- 'username' => '',
- 'password' => '',
- 'options' => [
- 'database' => '',
- ]
- ],
-
- // ...
-
-],
-```
-
-5 - Open your Laravel's `.env` file and update the following variables:
-
-- set the `DB_HOST` to your `mongo`.
-- set the `DB_PORT` to `27017`.
-- set the `DB_DATABASE` to `database`.
-
-
-6 - Finally make sure you have the `jenssegers/mongodb` package installed via Composer and its Service Provider is added.
-
-```bash
-composer require jenssegers/mongodb
-```
-More details about this [here](https://github.com/jenssegers/laravel-mongodb#installation).
-
-7 - Test it:
-
-- First let your Models extend from the Mongo Eloquent Model. Check the [documentation](https://github.com/jenssegers/laravel-mongodb#eloquent).
-- Enter the Workspace Container.
-- Migrate the Database `php artisan migrate`.
-
-
-
-
-
-
-
-
-### Use phpMyAdmin
-
-1 - Run the phpMyAdmin Container (`phpmyadmin`) with the `docker-compose up` command. Example:
-
-```bash
-# use with mysql
-docker-compose up -d mysql phpmyadmin
-
-# use with mariadb
-docker-compose up -d mariadb phpmyadmin
-```
-
-2 - Open your browser and visit the localhost on port **8080**: `http://localhost:8080`
-
-
-
-
-### Use pgAdmin
-
-1 - Run the pgAdmin Container (`pgadmin`) with the `docker-compose up` command. Example:
-
-```bash
-docker-compose up -d postgres pgadmin
-```
-
-2 - Open your browser and visit the localhost on port **5050**: `http://localhost:5050`
-
-
-
-
-### Use ElasticSearch
-
-1 - Run the ElasticSearch Container (`elasticsearch`) with the `docker-compose up` command. Example:
-
-```bash
-docker-compose up -d elasticsearch
-```
-
-2 - Open your browser and visit the localhost on port **9200**: `http://localhost:9200`
-
-### Install ElasticSearch Plugin
-
-1 - Install the ElasticSearch plugin like [delete-by-query](https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugins-delete-by-query.html).
-
-```bash
-docker exec {container-name} /usr/share/elasticsearch/bin/plugin install delete-by-query
-```
-
-2 - Restart elasticsearch container
-
-```bash
-docker restart {container-name}
-```
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Install Codeigniter
-
-To install Codeigniter 3 on Laradock all you have to do is the following simple steps:
-
-1 - Open the `docker-compose.yml` file.
-
-2 - Change `CODEIGNITER=false` to `CODEIGNITER=true`.
-
-3 - Re-build your PHP-FPM Container `docker-compose build php-fpm`.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-### Change the timezone
-
-To change the timezone for the `workspace` container, modify the `TZ` build argument in the Docker Compose file to one in the [TZ database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
-
-For example, if I want the timezone to be `New York`:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - TZ=America/New_York
- ...
-```
-
-We also recommend [setting the timezone in Laravel](http://www.camroncade.com/managing-timezones-with-laravel/).
-
-
-### Adding cron jobs
-
-You can add your cron jobs to `workspace/crontab/root` after the `php artisan` line.
-
-```
-* * * * * php /var/www/artisan schedule:run >> /dev/null 2>&1
-
-# Custom cron
-* * * * * root echo "Every Minute" > /var/log/cron.log 2>&1
-```
-
-Make sure you [change the timezone](#Change-the-timezone) if you don't want to use the default (UTC).
-
-
-### Access workspace via ssh
-
-You can access the `workspace` container through `localhost:2222` by setting the `INSTALL_WORKSPACE_SSH` build argument to `true`.
-
-To change the default forwarded port for ssh:
-
-```yml
- workspace:
- ports:
- - "2222:22" # Edit this line
- ...
-```
-
-
-### MySQL access from host
-
-You can forward the MySQL/MariaDB port to your host by making sure these lines are added to the `mysql` or `mariadb` section of the `docker-compose.yml` or in your [environment specific Compose](https://docs.docker.com/compose/extends/) file.
-
-```
-ports:
- - "3306:3306"
-```
-
-
-### MySQL root access
-
-The default username and password for the root mysql user are `root` and `root `.
-
-1 - Enter the mysql contaier: `docker-compose exec mysql bash`.
-
-2 - Enter mysql: `mysql -uroot -proot` for non root access use `mysql -uhomestead -psecret`.
-
-3 - See all users: `SELECT User FROM mysql.user;`
-
-4 - Run any commands `show databases`, `show tables`, `select * from.....`.
-
-
-
-
-### Use custom Domain (instead of the Docker IP)
-
-Assuming your custom domain is `laravel.dev`
-
-1 - Open your `/etc/hosts` file and map your localhost address `127.0.0.1` to the `laravel.dev` domain, by adding the following:
-
-```bash
-127.0.0.1 laravel.dev
-```
-
-2 - Open your browser and visit `{http://laravel.dev}`
-
-
-Optionally you can define the server name in the nginx config file, like this:
-
-```conf
-server_name laravel.dev;
-```
-
-
-
-
-
-### Enable Global Composer Build Install
-
-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.
-
-1 - open the `docker-compose.yml` file
-
-2 - search for the `COMPOSER_GLOBAL_INSTALL` argument under the Workspace Container and set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - COMPOSER_GLOBAL_INSTALL=true
- ...
-```
-3 - now add your dependencies to `workspace/composer.json`
-
-4 - rebuild the Workspace Container `docker-compose build workspace`
-
-
-
-
-
-
-### Install Prestissimo
-
-[Prestissimo](https://github.com/hirak/prestissimo) is a plugin for composer which enables parallel install functionality.
-
-1 - Enable Running Global Composer Install during the Build:
-
-Click on this [Enable Global Composer Build Install](#Enable-Global-Composer-Build-Install) and do steps 1 and 2 only then continue here.
-
-2 - Add prestissimo as requirement in Composer:
-
-a - now open the `workspace/composer.json` file
-
-b - add `"hirak/prestissimo": "^0.3"` as requirement
-
-c - rebuild the Workspace Container `docker-compose build workspace`
-
-
-
-
-
-
-### Install Node + NVM
-
-To install NVM and NodeJS in the Workspace container
-
-1 - Open the `docker-compose.yml` file
-
-2 - Search for the `INSTALL_NODE` argument under the Workspace Container and set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - INSTALL_NODE=true
- ...
-```
-
-3 - Re-build the container `docker-compose build workspace`
-
-
-
-### Install Node + YARN
-
-Yarn is a new package manager for JavaScript. It is so faster than npm, which you can find [here](http://yarnpkg.com/en/compare).To install NodeJS and [Yarn](https://yarnpkg.com/) in the Workspace container:
-
-1 - Open the `docker-compose.yml` file
-
-2 - Search for the `INSTALL_NODE` and `INSTALL_YARN` argument under the Workspace Container and set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - INSTALL_NODE=true
- - INSTALL_YARN=true
- ...
-```
-
-3 - Re-build the container `docker-compose build workspace`
-
-
-
-### Install Aerospike extension
-
-1 - First install `aerospike` in the Workspace and the PHP-FPM Containers:
-
-a) open the `docker-compose.yml` file
-
-b) search for the `INSTALL_AEROSPIKE_EXTENSION` argument under the Workspace Container
-
-c) set it to `true`
-
-d) search for the `INSTALL_AEROSPIKE_EXTENSION` argument under the PHP-FPM Container
-
-e) set it to `true`
-
-It should be like this:
-
-```yml
- workspace:
- build:
- context: ./workspace
- args:
- - INSTALL_AEROSPIKE_EXTENSION=true
- ...
- php-fpm:
- build:
- context: ./php-fpm
- args:
- - INSTALL_AEROSPIKE_EXTENSION=true
- ...
-```
-
-2 - Re-build the containers `docker-compose build workspace php-fpm`
-
-
-
-### Debugging
-
-*Here's a list of the common problems you might face, and the possible solutions.*
-
-
-
-#### I see a blank (white) page instead of the Laravel 'Welcome' page!
-
-Run the following command from the Laravel root directory:
-
-```bash
-sudo chmod -R 777 storage bootstrap/cache
-```
-
-
-#### I see "Welcome to nginx" instead of the Laravel App!
-
-Use `http://127.0.0.1` instead of `http://localhost` in your browser.
-
-
-
-#### I see an error message containing `address already in use`
-
-Make sure the ports for the services that you are trying to run (80, 3306, etc.) are not being used already by other programs, such as a built in `apache`/`httpd` service or other development tools you have installed.
-
-
-
-#### I get Nginx error 404 Not Found on Windows.
-
-1. Go to docker Settings on your Windows machine.
-2. Click on the `Shared Drives` tab and check the drive that contains your project files.
-3. Enter your windows username and password.
-4. Go to the `reset` tab and click restart docker.
-
-#### I get Mysql connection refused
-
-This error is sometimes happens because your Laravel application isn't running on the container localhost IP (Which is 127.0.0.1). Steps to fix it:
-
-1. Check your running Laravel application IP by dumping `Request::ip()` variable using `dd(Request::ip())` anywhere on your application. The result is the IP of your Laravel container.
-2. Change the `DB_HOST` variable on env with the IP that you received from previous step.
-
-
-
-
-
-
-### Upgrading LaraDock
-
-
-Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading LaraDock from v3.* to v4.*:
-
-1. Stop the docker vm `docker-machine stop {default}`
-2. Install Docker for [Mac](https://docs.docker.com/docker-for-mac/) or [Windows](https://docs.docker.com/docker-for-windows/).
-3. Upgrade LaraDock to `v4.*.*` (`git pull origin master`)
-4. Use LaraDock as you used to do: `docker-compose up -d nginx mysql`.
-
-**Note:** If you face any problem with the last step above: rebuild all your containers
-`docker-compose build --no-cache`
-"Warnning Containers Data might be lost!"
-
-
-
-
-
-
-
-
-## Contributing
-
-This little project was built by one man who has a full time job and many responsibilities, so if you like this project and you find that it needs a bug fix or support for new software or upgrade any container, or anything else.. Do not hesitate to contribute, you are more than welcome :)
-
-#### Read the [Contribution Guidelines](https://github.com/LaraDock/laradock/blob/master/CONTRIBUTING.md).
-
-
-
-
-
-## Help & Questions
-
-Join the chat room on [Gitter](https://gitter.im/LaraDock/laradock) and get help and support from the community.
-
-You can as well can open an [issue](https://github.com/laradock/laradock/issues) on Github (will be labeled as Question) and discuss it with people on [Gitter](https://gitter.im/LaraDock/laradock).
-
-For special help with Docker and/or Laravel, you can schedule a live call with the creator of this project at [Codementor.io](https://www.codementor.io/mahmoudz).
-
-
-
+[**Full Documentation Here**](http://laradock.io)
## Credits
-**Creator:**
+**Super Admins:**
-- [Mahmoud Zalt](https://github.com/Mahmoudz) [ [Twitter](https://twitter.com/Mahmoud_Zalt) | [Personal Site](http://zalt.me) | [Linkedin](https://www.linkedin.com/in/mahmoudzalt) ]
-
-**Admins:**
-
-- [Bo-Yi Wu](https://github.com/appleboy) (appleboy)
+- [Mahmoud Zalt](https://github.com/Mahmoudz) (mahmoudz) [ [Twitter](https://twitter.com/Mahmoud_Zalt) | [Personal Site](http://zalt.me) | [LinkedIn](https://www.linkedin.com/in/mahmoudzalt) ]
+- [Bo-Yi Wu](https://github.com/appleboy) (appleboy) [ [Twitter](https://twitter.com/appleboy) ]
- [Philippe Trépanier](https://github.com/philtrep) (philtrep)
+- [Mike Erickson](https://github.com/mikeerickson) (mikeerickson)
+- Join Us!
-**Main Contributors:**
+**Amazing Contributors:**
-- [Francis Lavoie](https://github.com/francislavoie) (francislavoie)
-- [luciano-jr](https://github.com/luciano-jr)
-- [Zhqagp](https://github.com/zhqagp)
-- [Tim B.](https://github.com/tjb328) (tjb328)
-- [MidasCodeBreaker](https://github.com/midascodebreaker)
-- [Larry Eitel](https://github.com/LarryEitel)
-- [Suteepat](https://github.com/tianissimo) (tianissimo)
-- [David](https://github.com/davidavz) (davidavz)
-- [Lialosiu](https://github.com/lialosiu)
-- [Eric Pfeiffer](https://github.com/computerfr33k) (computerfr33k)
-- [Orette](https://github.com/orette)
-- [Jack Fletcher](https://github.com/Kauhat) (Kauhat)
-- [Amin Mkh](https://github.com/AminMkh)
-- [Matthew Tonkin Dunn](https://github.com/mattythebatty) (mattythebatty)
-- [Zhivitsa Kirill](https://github.com/zhikiri) (zhikiri)
-- [Benmag](https://github.com/benmag)
-
-**Other Contributors & Supporters:**
-
-- [Contributors](https://github.com/LaraDock/laradock/graphs/contributors)
-- [Supporters](https://github.com/LaraDock/laradock/issues?utf8=%E2%9C%93&q=)
+- [Contributors](https://github.com/laradock/laradock/graphs/contributors)
## License
diff --git a/_guides/photos/KiTTY/Connection.png b/_guides/photos/KiTTY/Connection.png
new file mode 100644
index 0000000..83c30a4
Binary files /dev/null and b/_guides/photos/KiTTY/Connection.png differ
diff --git a/_guides/photos/KiTTY/ConnectionData.png b/_guides/photos/KiTTY/ConnectionData.png
new file mode 100644
index 0000000..983f67f
Binary files /dev/null and b/_guides/photos/KiTTY/ConnectionData.png differ
diff --git a/_guides/photos/KiTTY/ConnectionSSH.png b/_guides/photos/KiTTY/ConnectionSSH.png
new file mode 100644
index 0000000..89892c9
Binary files /dev/null and b/_guides/photos/KiTTY/ConnectionSSH.png differ
diff --git a/_guides/photos/KiTTY/ConnectionSSHAuth.png b/_guides/photos/KiTTY/ConnectionSSHAuth.png
new file mode 100644
index 0000000..5f36d1e
Binary files /dev/null and b/_guides/photos/KiTTY/ConnectionSSHAuth.png differ
diff --git a/_guides/photos/KiTTY/Session.png b/_guides/photos/KiTTY/Session.png
new file mode 100644
index 0000000..78e1f84
Binary files /dev/null and b/_guides/photos/KiTTY/Session.png differ
diff --git a/_guides/photos/KiTTY/Terminal.png b/_guides/photos/KiTTY/Terminal.png
new file mode 100644
index 0000000..3486cf4
Binary files /dev/null and b/_guides/photos/KiTTY/Terminal.png differ
diff --git a/_guides/photos/KiTTY/TerminalKeyboard.png b/_guides/photos/KiTTY/TerminalKeyboard.png
new file mode 100644
index 0000000..262c6e1
Binary files /dev/null and b/_guides/photos/KiTTY/TerminalKeyboard.png differ
diff --git a/_guides/photos/KiTTY/TerminalShell.png b/_guides/photos/KiTTY/TerminalShell.png
new file mode 100644
index 0000000..19ec53b
Binary files /dev/null and b/_guides/photos/KiTTY/TerminalShell.png differ
diff --git a/_guides/photos/KiTTY/Window.png b/_guides/photos/KiTTY/Window.png
new file mode 100644
index 0000000..3b80559
Binary files /dev/null and b/_guides/photos/KiTTY/Window.png differ
diff --git a/_guides/photos/KiTTY/WindowAppearance.png b/_guides/photos/KiTTY/WindowAppearance.png
new file mode 100644
index 0000000..6491aa7
Binary files /dev/null and b/_guides/photos/KiTTY/WindowAppearance.png differ
diff --git a/_guides/photos/PHPStorm/DebugRemoteOn.png b/_guides/photos/PHPStorm/DebugRemoteOn.png
new file mode 100644
index 0000000..26e20e5
Binary files /dev/null and b/_guides/photos/PHPStorm/DebugRemoteOn.png differ
diff --git a/_guides/photos/PHPStorm/RemoteDebuggingSuccess.png b/_guides/photos/PHPStorm/RemoteDebuggingSuccess.png
new file mode 100644
index 0000000..665b642
Binary files /dev/null and b/_guides/photos/PHPStorm/RemoteDebuggingSuccess.png differ
diff --git a/_guides/photos/PHPStorm/RemoteHost.png b/_guides/photos/PHPStorm/RemoteHost.png
new file mode 100644
index 0000000..974003f
Binary files /dev/null and b/_guides/photos/PHPStorm/RemoteHost.png differ
diff --git a/_guides/photos/PHPStorm/RemoteTestDebuggingSuccess.png b/_guides/photos/PHPStorm/RemoteTestDebuggingSuccess.png
new file mode 100644
index 0000000..73d2f7f
Binary files /dev/null and b/_guides/photos/PHPStorm/RemoteTestDebuggingSuccess.png differ
diff --git a/_guides/photos/PHPStorm/RemoteWebDebuggingSuccess.png b/_guides/photos/PHPStorm/RemoteWebDebuggingSuccess.png
new file mode 100644
index 0000000..d4f0fc3
Binary files /dev/null and b/_guides/photos/PHPStorm/RemoteWebDebuggingSuccess.png differ
diff --git a/_guides/photos/PHPStorm/Settings/BuildDeploymentConnection.png b/_guides/photos/PHPStorm/Settings/BuildDeploymentConnection.png
new file mode 100644
index 0000000..3c0c864
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/BuildDeploymentConnection.png differ
diff --git a/_guides/photos/PHPStorm/Settings/BuildDeploymentConnectionMappings.png b/_guides/photos/PHPStorm/Settings/BuildDeploymentConnectionMappings.png
new file mode 100644
index 0000000..1388a7c
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/BuildDeploymentConnectionMappings.png differ
diff --git a/_guides/photos/PHPStorm/Settings/BuildDeploymentDebugger.png b/_guides/photos/PHPStorm/Settings/BuildDeploymentDebugger.png
new file mode 100644
index 0000000..cef9ec1
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/BuildDeploymentDebugger.png differ
diff --git a/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteExampleTestDebug.png b/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteExampleTestDebug.png
new file mode 100644
index 0000000..2a5faf5
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteExampleTestDebug.png differ
diff --git a/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteWebDebug.png b/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteWebDebug.png
new file mode 100644
index 0000000..ced9653
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/EditRunConfigurationRemoteWebDebug.png differ
diff --git a/_guides/photos/PHPStorm/Settings/LangsPHPDebug.png b/_guides/photos/PHPStorm/Settings/LangsPHPDebug.png
new file mode 100644
index 0000000..a6b9d14
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/LangsPHPDebug.png differ
diff --git a/_guides/photos/PHPStorm/Settings/LangsPHPInterpreters.png b/_guides/photos/PHPStorm/Settings/LangsPHPInterpreters.png
new file mode 100644
index 0000000..1acbc87
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/LangsPHPInterpreters.png differ
diff --git a/_guides/photos/PHPStorm/Settings/LangsPHPPHPUnit.png b/_guides/photos/PHPStorm/Settings/LangsPHPPHPUnit.png
new file mode 100644
index 0000000..8b09f2f
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/LangsPHPPHPUnit.png differ
diff --git a/_guides/photos/PHPStorm/Settings/LangsPHPServers.png b/_guides/photos/PHPStorm/Settings/LangsPHPServers.png
new file mode 100644
index 0000000..38ea9d2
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/LangsPHPServers.png differ
diff --git a/_guides/photos/PHPStorm/Settings/WindowsFirewallAllowedApps.png b/_guides/photos/PHPStorm/Settings/WindowsFirewallAllowedApps.png
new file mode 100644
index 0000000..813493a
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/WindowsFirewallAllowedApps.png differ
diff --git a/_guides/photos/PHPStorm/Settings/WindowsHyperVManager.png b/_guides/photos/PHPStorm/Settings/WindowsHyperVManager.png
new file mode 100644
index 0000000..d449e42
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/WindowsHyperVManager.png differ
diff --git a/_guides/photos/PHPStorm/Settings/hosts.png b/_guides/photos/PHPStorm/Settings/hosts.png
new file mode 100644
index 0000000..332a837
Binary files /dev/null and b/_guides/photos/PHPStorm/Settings/hosts.png differ
diff --git a/_guides/photos/SimpleHostsEditor/AddHost_laravel.png b/_guides/photos/SimpleHostsEditor/AddHost_laravel.png
new file mode 100644
index 0000000..f879282
Binary files /dev/null and b/_guides/photos/SimpleHostsEditor/AddHost_laravel.png differ
diff --git a/_guides/phpstorm.md b/_guides/phpstorm.md
new file mode 100644
index 0000000..8dad1a2
--- /dev/null
+++ b/_guides/phpstorm.md
@@ -0,0 +1,302 @@
+# PHPStorm Debugging Guide
+
+- [Intro](#Intro)
+- [Installation](#Installation)
+ - [Customize laradock/docker-compose.yml](#CustomizeDockerCompose)
+ - [Clean House](#InstallCleanHouse)
+ - [LaraDock Dial Tone](#InstallLaraDockDialTone)
+ - [hosts](#AddToHosts)
+ - [Firewall](#FireWall)
+ - [Enable xDebug on php-fpm](#enablePhpXdebug)
+ - [PHPStorm Settings](#InstallPHPStorm)
+ - [Configs](#InstallPHPStormConfigs)
+- [Usage](#Usage)
+ - [Laravel](#UsageLaravel)
+ - [Run ExampleTest](#UsagePHPStormRunExampleTest)
+ - [Debug ExampleTest](#UsagePHPStormDebugExampleTest)
+ - [Debug Web Site](#UsagePHPStormDebugSite)
+- [SSH into workspace](#SSHintoWorkspace)
+ - [KiTTY](#InstallKiTTY)
+
+
+## Intro
+
+Wiring up [Laravel](https://laravel.com/), [LaraDock](https://github.com/LaraDock/laradock) [Laravel+Docker] and [PHPStorm](https://www.jetbrains.com/phpstorm/) to play nice together complete with remote xdebug'ing as icing on top! Although this guide is based on `PHPStorm Windows`,
+you should be able to adjust accordingly. This guide was written based on Docker for Windows Native.
+
+
+## Installation
+
+- This guide assumes the following:
+ - you have already installed and are familiar with Laravel, LaraDock and PHPStorm.
+ - you have installed Laravel as a parent of `laradock`. This guide assumes `/c/_dk/laravel`.
+
+
+## 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`.
+ - ![Windows Hyper-V Manager](photos/PHPStorm/Settings/WindowsHyperVManager.png)
+
+- [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).
+
+
+
+## Firewall
+Your PHPStorm will need to be able to receive a connection from PHP xdebug either your running workspace or php-fpm containers on port 9000. This means that your Windows Firewall should either enable connections from the Application PHPStorm OR the port.
+
+- It is important to note that if the Application PHPStorm is NOT enabled in the firewall, you will not be able to recreate a rule to override that.
+- Also be aware that if you are installing/upgrade different versions of PHPStorm, you MAY have orphaned references to PHPStorm in your Firewall! You may decide to remove orphaned references however in either case, make sure that they are set to receive public TCP traffic.
+
+### Edit laradock/docker-compose.yml
+Set the following variables:
+```
+### Workspace Utilities Container ###########################
+
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_XDEBUG=true
+ - INSTALL_WORKSPACE_SSH=true
+ ...
+
+
+### PHP-FPM Container #######################################
+
+ php-fpm:
+ build:
+ context: ./php-fpm
+ args:
+ - INSTALL_XDEBUG=true
+ ...
+
+```
+
+### Edit xdebug.ini files
+- `laradock/workspace/xdebug.ini`
+- `laradock/php-fpm/xdebug.ini`
+
+Set the following variables:
+```
+xdebug.remote_autostart=1
+xdebug.remote_enable=1
+xdebug.remote_connect_back=1
+xdebug.cli_color=1
+```
+
+
+
+### Need to clean house first?
+Make sure you are starting with a clean state. For example, do you have other LaraDock containers and images?
+Here are a few things I use to clean things up.
+
+- Delete all containers using `grep laradock_` on the names, see: [Remove all containers based on docker image name](https://linuxconfig.org/remove-all-containners-based-on-docker-image-name).
+`docker ps -a | awk '{ print $1,$2 }' | grep laradock_ | awk '{print $1}' | xargs -I {} docker rm {}`
+
+- Delete all images containing `laradock`.
+`docker images | awk '{print $1,$2,$3}' | grep laradock_ | awk '{print $3}' | xargs -I {} docker rmi {}`
+**Note:** This will only delete images that were built with `LaraDock`, **NOT** `laradock/*` which are pulled down by `LaraDock` such as `laradock/workspace`, etc.
+**Note:** Some may fail with:
+`Error response from daemon: conflict: unable to delete 3f38eaed93df (cannot be forced) - image has dependent child images`
+
+- I added this to my `.bashrc` to remove orphaned images.
+ ```
+ dclean() {
+ processes=`docker ps -q -f status=exited`
+ if [ -n "$processes" ]; thend
+ docker rm $processes
+ fi
+
+ images=`docker images -q -f dangling=true`
+ if [ -n "$images" ]; then
+ docker rmi $images
+ fi
+ }
+ ```
+
+- If you frequently switch configurations for LaraDock, you may find that adding the following and added to your `.bashrc` or equivalent useful:
+```
+# remove laravel* containers
+# remove laravel_* images
+dcleanlaradockfunction()
+{
+ echo 'Removing ALL containers associated with laradock'
+ docker ps -a | awk '{ print $1,$2 }' | grep laradock | awk '{print $1}' | xargs -I {} docker rm {}
+
+ # remove ALL images associated with laradock_
+ # does NOT delete laradock/* which are hub images
+ echo 'Removing ALL images associated with laradock_'
+ docker images | awk '{print $1,$2,$3}' | grep laradock_ | awk '{print $3}' | xargs -I {} docker rmi {}
+
+ echo 'Listing all laradock docker hub images...'
+ docker images | grep laradock
+
+ echo 'dcleanlaradock completed'
+}
+# associate the above function with an alias
+# so can recall/lookup by typing 'alias'
+alias dcleanlaradock=dcleanlaradockfunction
+```
+
+
+#### Let's get a dial-tone with Laravel
+
+```
+# barebones at this point
+docker-compose up -d nginx mysql
+
+# run
+docker-compose ps
+
+# Should see:
+ Name Command State Ports
+-----------------------------------------------------------------------------------------------------------
+laradock_mysql_1 docker-entrypoint.sh mysqld Up 0.0.0.0:3306->3306/tcp
+laradock_nginx_1 nginx Up 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp
+laradock_php-fpm_1 php-fpm Up 9000/tcp
+laradock_volumes_data_1 true Exit 0
+laradock_volumes_source_1 true Exit 0
+laradock_workspace_1 /sbin/my_init Up 0.0.0.0:2222->22/tcp
+
+
+```
+
+
+#### Enable xDebug on php-fpm
+In a host terminal sitting in the laradock folder, run: `./xdebugPhpFpm status`
+You should see something like the following:
+```
+xDebug status
+laradock_php-fpm_1
+PHP 7.0.9 (cli) (built: Aug 10 2016 19:45:48) ( NTS )
+Copyright (c) 1997-2016 The PHP Group
+Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies
+ with Xdebug v2.4.1, Copyright (c) 2002-2016, by Derick Rethans
+```
+Other commands include `./xdebugPhpFpm start | stop`.
+
+If you have enabled `xdebug=true` in `docker-compose.yml/php-fpm`, `xdebug` will already be running when
+`php-fpm` is started and listening for debug info on port 9000.
+
+
+
+#### PHPStorm Settings
+- Here are some settings that are known to work:
+ - `Settings/BuildDeploymentConnection`
+ - ![Settings/BuildDeploymentConnection](photos/PHPStorm/Settings/BuildDeploymentConnection.png)
+
+ - `Settings/BuildDeploymentConnectionMappings`
+ - ![Settings/BuildDeploymentConnectionMappings](photos/PHPStorm/Settings/BuildDeploymentConnectionMappings.png)
+
+ - `Settings/BuildDeploymentDebugger`
+ - ![Settings/BuildDeploymentDebugger](photos/PHPStorm/Settings/BuildDeploymentDebugger.png)
+
+ - `Settings/EditRunConfigurationRemoteWebDebug`
+ - ![Settings/EditRunConfigurationRemoteWebDebug](photos/PHPStorm/Settings/EditRunConfigurationRemoteWebDebug.png)
+
+ - `Settings/EditRunConfigurationRemoteExampleTestDebug`
+ - ![Settings/EditRunConfigurationRemoteExampleTestDebug](photos/PHPStorm/Settings/EditRunConfigurationRemoteExampleTestDebug.png)
+
+ - `Settings/LangsPHPDebug`
+ - ![Settings/LangsPHPDebug](photos/PHPStorm/Settings/LangsPHPDebug.png)
+
+ - `Settings/LangsPHPInterpreters`
+ - ![Settings/LangsPHPInterpreters](photos/PHPStorm/Settings/LangsPHPInterpreters.png)
+
+ - `Settings/LangsPHPPHPUnit`
+ - ![Settings/LangsPHPPHPUnit](photos/PHPStorm/Settings/LangsPHPPHPUnit.png)
+
+ - `Settings/LangsPHPServers`
+ - ![Settings/LangsPHPServers](photos/PHPStorm/Settings/LangsPHPServers.png)
+
+ - `RemoteHost`
+ To switch on this view, go to: `Menu/Tools/Deployment/Browse Remote Host`.
+ - ![RemoteHost](photos/PHPStorm/RemoteHost.png)
+
+ - `RemoteWebDebug`
+ - ![DebugRemoteOn](photos/PHPStorm/DebugRemoteOn.png)
+
+ - `EditRunConfigurationRemoteWebDebug`
+ Go to: `Menu/Run/Edit Configurations`.
+ - ![EditRunConfigurationRemoteWebDebug](photos/PHPStorm/Settings/EditRunConfigurationRemoteWebDebug.png)
+
+ - `EditRunConfigurationRemoteExampleTestDebug`
+ Go to: `Menu/Run/Edit Configurations`.
+ - ![EditRunConfigurationRemoteExampleTestDebug](photos/PHPStorm/Settings/EditRunConfigurationRemoteExampleTestDebug.png)
+
+ - `WindowsFirewallAllowedApps`
+ Go to: `Control Panel\All Control Panel Items\Windows Firewall\Allowed apps`.
+ - ![WindowsFirewallAllowedApps.png](photos/PHPStorm/Settings/WindowsFirewallAllowedApps.png)
+
+ - `hosts`
+ Edit: `C:\Windows\System32\drivers\etc\hosts`.
+ - ![WindowsFirewallAllowedApps.png](photos/PHPStorm/Settings/hosts.png)
+
+ - [Enable xDebug on php-fpm](#enablePhpXdebug)
+
+
+
+
+## Usage
+
+
+### Run ExampleTest
+- right-click on `tests/ExampleTest.php`
+ - Select: `Run 'ExampleTest.php'` or `Ctrl+Shift+F10`.
+ - Should pass!! You just ran a remote test via SSH!
+
+
+### Debug ExampleTest
+- Open to edit: `tests/ExampleTest.php`
+- Add a BreakPoint on line 16: `$this->visit('/')`
+- 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!
+ - ![Remote Test Debugging Success](photos/PHPStorm/RemoteTestDebuggingSuccess.png)
+
+
+
+### Debug WebSite
+- In case xDebug is disabled, from the `laradock` folder run:
+`./xdebugPhpFpm start`.
+ - To switch xdebug off, run:
+`./xdebugPhpFpm stop`
+
+- Start Remote Debugging
+ - ![DebugRemoteOn](photos/PHPStorm/DebugRemoteOn.png)
+
+- 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!
+ - ![Remote Debugging Success](photos/PHPStorm/RemoteDebuggingSuccess.png)
+
+
+
+#### Let's shell into workspace
+Assuming that you are in laradock folder, type:
+`ssh -i workspace/insecure_id_rsa -p2222 root@laravel`
+**Cha Ching!!!!**
+- `workspace/insecure_id_rsa.ppk` may become corrupted. In which case:
+ - fire up `puttygen`
+ - import `workspace/insecure_id_rsa`
+ - save private key to `workspace/insecure_id_rsa.ppk`
+
+
+
+##### KiTTY
+[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:
+ - ![Session](photos/KiTTY/Session.png)
+ - ![Terminal](photos/KiTTY/Terminal.png)
+ - ![Window](photos/KiTTY/Window.png)
+ - ![WindowAppearance](photos/KiTTY/WindowAppearance.png)
+ - ![Connection](photos/KiTTY/Connection.png)
+ - ![ConnectionData](photos/KiTTY/ConnectionData.png)
+ - ![ConnectionSSH](photos/KiTTY/ConnectionSSH.png)
+ - ![ConnectionSSHAuth](photos/KiTTY/ConnectionSSHAuth.png)
+ - ![TerminalShell](photos/KiTTY/TerminalShell.png)
+
+
diff --git a/caddy/Caddyfile b/caddy/Caddyfile
index 4f0212a..269b62a 100644
--- a/caddy/Caddyfile
+++ b/caddy/Caddyfile
@@ -4,6 +4,10 @@ root /var/www/public
fastcgi / php-fpm:9000 php {
index index.php
}
+
+# To handle .html extensions with laravel change ext to
+# ext / .html
+
rewrite {
r .*
ext /
@@ -16,3 +20,9 @@ errors /var/log/caddy/error.log
# Uncomment to enable TLS (HTTPS)
# Change the first list to listen on port 443 when enabling TLS
#tls self_signed
+
+# To use Lets encrpt tls with a DNS provider uncomment these
+# lines and change the provider as required
+#tls {
+# dns cloudflare
+#}
diff --git a/caddy/Dockerfile b/caddy/Dockerfile
index 9579d15..b6cfffd 100644
--- a/caddy/Dockerfile
+++ b/caddy/Dockerfile
@@ -2,7 +2,7 @@ FROM alpine:3.4
MAINTAINER Eric Pfeiffer
-ENV caddy_version=0.9.3
+ENV caddy_version=0.9.5
LABEL caddy_version="$caddy_version" architecture="amd64"
@@ -12,13 +12,13 @@ RUN apk update \
RUN curl --silent --show-error --fail --location \
--header "Accept: application/tar+gzip, application/x-gzip, application/octet-stream" -o - \
- "https://github.com/mholt/caddy/releases/download/v$caddy_version/caddy_linux_amd64.tar.gz" \
- | tar --no-same-owner -C /usr/bin/ -xz caddy_linux_amd64 \
- && mv /usr/bin/caddy_linux_amd64 /usr/bin/caddy \
+ "https://caddyserver.com/download/build?os=linux&arch=amd64&features=cloudflare%2Cdigitalocean%2Cdnsimple%2Cdyn%2Cgooglecloud%2Clinode%2Croute53" \
+ | tar --no-same-owner -C /usr/bin/ -xz caddy \
+ && mv /usr/bin/caddy /usr/bin/caddy \
&& chmod 0755 /usr/bin/caddy
EXPOSE 80 443 2015
WORKDIR /var/www/public
-CMD ["/usr/bin/caddy", "-conf", "/etc/Caddyfile"]
+CMD ["/usr/bin/caddy", "-conf", "/etc/Caddyfile"]
\ No newline at end of file
diff --git a/docker-compose.yml b/docker-compose.yml
index dd73145..fd53681 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -17,16 +17,22 @@ services:
context: ./workspace
args:
- INSTALL_XDEBUG=false
+ - INSTALL_SOAP=false
- INSTALL_MONGO=false
- INSTALL_NODE=false
- INSTALL_YARN=false
- INSTALL_DRUSH=false
- INSTALL_AEROSPIKE_EXTENSION=false
+ - INSTALL_V8JS_EXTENSION=false
- COMPOSER_GLOBAL_INSTALL=false
- INSTALL_WORKSPACE_SSH=false
+ - INSTALL_LARAVEL_ENVOY=false
+ - INSTALL_DEPLOYER=false
+ - INSTALL_LINUXBREW=false
- PUID=1000
- PGID=1000
- NODE_VERSION=stable
+ - YARN_VERSION=latest
- TZ=UTC
volumes_from:
- applications
@@ -44,10 +50,14 @@ services:
context: ./php-fpm
args:
- INSTALL_XDEBUG=false
+ - INSTALL_SOAP=false
- INSTALL_MONGO=false
- INSTALL_ZIP_ARCHIVE=false
+ - INSTALL_BCMATH=false
+ - INSTALL_PHPREDIS=false
- INSTALL_MEMCACHED=false
- INSTALL_OPCACHE=false
+ - INSTALL_EXIF=false
- INSTALL_AEROSPIKE_EXTENSION=false
- CODEIGNITER=false
dockerfile: Dockerfile-70
@@ -75,6 +85,7 @@ services:
- applications
volumes:
- ./logs/nginx/:/var/log/nginx
+ - ./nginx/sites/:/etc/nginx/sites-available
ports:
- "80:80"
- "443:443"
@@ -112,23 +123,24 @@ services:
### MySQL Container #########################################
mysql:
- build: ./mysql
+ build:
+ context: ./mysql
+ args:
+ - MYSQL_DATABASE=homestead
+ - MYSQL_USER=homestead
+ - MYSQL_PASSWORD=secret
+ - MYSQL_ROOT_PASSWORD=root
volumes:
- mysql:/var/lib/mysql
ports:
- "3306:3306"
- environment:
- MYSQL_DATABASE: homestead
- MYSQL_USER: homestead
- MYSQL_PASSWORD: secret
- MYSQL_ROOT_PASSWORD: root
### MariaDB Container #######################################
mariadb:
build: ./mariadb
volumes:
- - mariadb
+ - mariadb:/var/lib/mysql
ports:
- "3306:3306"
environment:
@@ -150,6 +162,19 @@ services:
POSTGRES_USER: homestead
POSTGRES_PASSWORD: secret
+### PostgreSQL PostGis Container ############################
+
+ postgres-postgis:
+ build: ./postgres-postgis
+ volumes:
+ - postgres:/var/lib/postgresql/data
+ ports:
+ - "5432:5432"
+ environment:
+ POSTGRES_DB: homestead
+ POSTGRES_USER: homestead
+ POSTGRES_PASSWORD: secret
+
### Neo4j Container #########################################
neo4j:
@@ -171,6 +196,15 @@ services:
volumes:
- mongo:/data/db
+### RethinkDB Container #######################################
+
+ rethinkdb:
+ build: ./rethinkdb
+ ports:
+ - "8090:8080"
+ volumes:
+ - rethinkdb:/data/rethinkdb_data
+
### Redis Container #########################################
redis:
@@ -244,17 +278,16 @@ services:
caddy:
build: ./caddy
- volumes_from:
- - applications
- volumes:
- - caddy:/root/.caddy
ports:
- "80:80"
- "443:443"
- "2015:2015"
+ volumes_from:
+ - applications
volumes:
- ./caddy/Caddyfile:/etc/Caddyfile
- ./logs/caddy:/var/log/caddy
+ - caddy:/root/.caddy
links:
- php-fpm
@@ -267,8 +300,6 @@ services:
MYSQL_USER: homestead
MYSQL_PASSWORD: secret
MYSQL_ROOT_PASSWORD: root
- volumes:
- - phpmyadmin
ports:
- "8080:80"
links:
@@ -292,19 +323,28 @@ services:
build: ./elasticsearch
volumes:
- elasticsearch-data:/usr/share/elasticsearch/data
- - elasticsearch-pkugins:/usr/share/elasticsearch/data
+ - elasticsearch-plugins:/usr/share/elasticsearch/data
ports:
- "9200:9200"
- "9300:9300"
links:
- php-fpm
+### Mailhog Container #########################################
+
mailhog:
build: ./mailhog
ports:
- "1025:1025"
- "8025:8025"
+### Selenium Container #########################################
+
+ selenium:
+ build: ./selenium
+ ports:
+ - "4444:4444"
+
### Volumes Setup ###########################################
volumes:
@@ -322,6 +362,8 @@ volumes:
driver: "local"
mongo:
driver: "local"
+ rethinkdb:
+ driver: "local"
phpmyadmin:
driver: "local"
aerospike:
@@ -330,7 +372,7 @@ volumes:
driver: "local"
elasticsearch-data:
driver: "local"
- elasticsearch-pkugins:
+ elasticsearch-plugins:
driver: "local"
sessions: ## nothing is connected to this (- ./data/sessions:/sessions)
driver: "local"
diff --git a/docs/.gitkeep b/docs/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/docs/CNAME b/docs/CNAME
new file mode 100644
index 0000000..df75fb6
--- /dev/null
+++ b/docs/CNAME
@@ -0,0 +1 @@
+laradock.io
\ No newline at end of file
diff --git a/docs/_settings/config.toml b/docs/_settings/config.toml
new file mode 100644
index 0000000..67fda54
--- /dev/null
+++ b/docs/_settings/config.toml
@@ -0,0 +1,91 @@
+baseurl = "http://laradock.io/"
+languageCode = "en-us"
+publishDir = "../"
+title = "Laradock Docs"
+theme = "hugo-material-docs"
+metadataformat = "yaml"
+canonifyurls = true
+# Enable Google Analytics by entering your tracking id
+googleAnalytics = "UA-37514928-9"
+
+[params]
+ # General information
+ author = "Mahmoud Zalt"
+ description = "Laradock documentations."
+ copyright = ""
+
+ # Repository
+ provider = "GitHub"
+ repo_url = "https://github.com/laradock/laradock"
+
+ version = ""
+ logo = ""
+ favicon = ""
+
+ permalink = "#"
+
+ # Custom assets
+ custom_css = []
+ custom_js = []
+
+ # Syntax highlighting theme
+ highlight_css = ""
+
+ [params.palette]
+ primary = "purple"
+ accent = "deep-purple"
+
+ [params.font]
+ text = "Doctarine"
+ code = "Source Code Pro"
+
+[social]
+ twitter = ""
+ github = "laradock"
+ email = ""
+
+# ------- MENU START -----------------------------------------
+
+[[menu.main]]
+ name = "Introduction"
+ url = "introduction/"
+ weight = 1
+
+[[menu.main]]
+ name = "Getting Started"
+ url = "getting-started/"
+ weight = 2
+
+[[menu.main]]
+ name = "Documentation"
+ url = "documentation/"
+ weight = 3
+
+[[menu.main]]
+ name = "Related Projects"
+ url = "related-projects/"
+ weight = 4
+
+[[menu.main]]
+ name = "Help & Questions"
+ url = "help/"
+ weight = 5
+
+[[menu.main]]
+ name = "Contributing"
+ url = "contributing/"
+ weight = 6
+
+[[menu.main]]
+ name = "License"
+ url = "license/"
+ weight = 7
+
+# ------- MENU END -----------------------------------------
+
+[blackfriday]
+ smartypants = true
+ fractions = true
+ smartDashes = true
+ plainIDAnchors = true
+
diff --git a/CONTRIBUTING.md b/docs/_settings/content/contributing/index.md
similarity index 69%
rename from CONTRIBUTING.md
rename to docs/_settings/content/contributing/index.md
index b6cb9d4..7e8c8df 100644
--- a/CONTRIBUTING.md
+++ b/docs/_settings/content/contributing/index.md
@@ -1,23 +1,47 @@
-# Contributing to LaraDock
-
-Your contribution is more than welcome. Let's keep LaraDock amazing.
+---
+title: Contributing
+type: index
+weight: 6
+---
-### Got a Question or Problem?
+Your contribution is more than welcome.
-If you have questions about how to use LaraDock, please direct your questions to the discussion on [Gitter](https://gitter.im/LaraDock/laradock). If you beleave your question could help others, then consider opening an [Issue](https://github.com/laradock/laradock/issues) (it will be labeled as Question).
+## Got a Question or Problem?
-### Found an Issue?
+If you have questions about how to use LaraDock, please direct your questions to the discussion on [Gitter](https://gitter.im/LaraDock/laradock). If you believe your question could help others, then consider opening an [Issue](https://github.com/laradock/laradock/issues) (it will be labeled as Question).
+
+## Found an Issue?
If you find a bug in the source code or a mistake in the documentation, you can help us by
submitting an [Issue](https://github.com/laradock/laradock/issues). Even better you can submit a Pull Request with a fix.
-### Want a Feature?
+## Want a Feature?
You can request a new feature by submitting an [Issue](https://github.com/laradock/laradock/issues) (it will be labeled as Feature Suggestion). If you would like to implement a new feature then consider submitting a Pull Request.
+## Edit the documentation
+
+Laradock uses [Hugo](https://gohugo.io/) as website generator tool, with the [Material Docs theme](http://themes.gohugo.io/theme/material-docs/). You might need to check their docs quickly.
+
+
+1. Install [Hugo](https://gohugo.io/) on your machine.
+2. Clone laradock.
+3. Go to `/docs`.
+4. Delete everything except the `_settings` folder & the `CNAME` file.
+5. Open `docs/_settings` from your terminal and run `hugo serve` to host the website locally.
+6. Open the `docs/_settings/content` and search for the folder of the section you want to edit.
+7. In each secion there's an `index.md` file, that's the file you need to edit.
+8. To edit the sidebar (in case you are adding new section) go to `docs/_settings/config.toml` and add the section there.
+9. After done editing, run the this command `hugo` to generate the updated site inside the `docs` folder.
+10. Go back to the project root directory, commit and push..
+
+
+
+
+
## Coding Guidelines
-### Support new Software
+## Support new Software
* Create folder with the software name.
@@ -31,20 +55,20 @@ You can request a new feature by submitting an [Issue](https://github.com/larado
* Add the software in the `Readme`.
-### Edit existing Software
+## Edit existing Software
* Open the software (container) folder.
* Edit the files you want to update.
* **Note:** If you want to edit the base image of the `Workspace` or the `php-fpm` Containers,
-you need to edit their Dockerfiles from their Github repositories. For more info read their Dockerfiles comment on the LaraDock repository.
+you need to edit their Docker-files from their GitHub repositories. For more info read their Dockerfiles comment on the LaraDock repository.
-* Make sure to update the `Readme` incase you made any changes.
+* Make sure to update the `Readme` in case you made any changes.
## Issue/PR Submission Guidelines
-### Submitting an Issue
+## Submitting an Issue
Before you submit your issue search the archive, maybe your question was already answered.
If your issue appears to be a bug, and hasn't been reported, open a new issue.
@@ -52,7 +76,7 @@ Help us to maximize the effort we can spend fixing issues and adding new
features, by not reporting duplicate issues.
-### Before Submitting a Pull Request (PR)
+## Before Submitting a Pull Request (PR)
Always Test everything and make sure its working:
@@ -65,10 +89,10 @@ Always Test everything and make sure its working:
- Test it in real App.
-### Submitting a PR
+## Submitting a PR
Consider the following guidelines:
-* Search [GitHub](https://github.com/LaraDock/laradock/pulls) for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
+* Search [GitHub](https://github.com/laradock/laradock/pulls) for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
* Make your changes in a new git branch:
@@ -103,7 +127,7 @@ git push origin my-fix-branch -f
-### After your PR is merged
+## After your PR is merged
After your pull request is merged, you can safely delete your branch and pull the changes
from the main (upstream) repository:
@@ -137,4 +161,4 @@ from the main (upstream) repository:
-### Happy Coding :)
+## Happy Coding :)
diff --git a/docs/_settings/content/documentation/index.md b/docs/_settings/content/documentation/index.md
new file mode 100644
index 0000000..3494b1a
--- /dev/null
+++ b/docs/_settings/content/documentation/index.md
@@ -0,0 +1,1430 @@
+---
+title: Documentation
+type: index
+weight: 3
+---
+
+
+
+## List current running Containers
+```bash
+docker ps
+```
+You can also use the following command if you want to see only this project containers:
+
+```bash
+docker-compose ps
+```
+
+
+
+
+
+
+
+
+## Close all running Containers
+```bash
+docker-compose stop
+```
+
+To stop single container do:
+
+```bash
+docker-compose stop {container-name}
+```
+
+
+
+
+
+
+
+
+## Delete all existing Containers
+```bash
+docker-compose down
+```
+
+
+
+
+
+
+
+
+## Enter a Container (run commands in a running Container)
+
+1 - First list the current running containers with `docker ps`
+
+2 - Enter any container using:
+
+```bash
+docker-compose exec {container-name} bash
+```
+
+*Example: enter MySQL container*
+
+```bash
+docker-compose exec mysql bash
+```
+
+*Example: enter to MySQL prompt within MySQL container*
+
+```bash
+docker-compose exec mysql mysql -u homestead -psecret
+```
+
+3 - To exit a container, type `exit`.
+
+
+
+
+
+
+
+
+## Edit default container configuration
+Open the `docker-compose.yml` and change anything you want.
+
+Examples:
+
+Change MySQL Database Name:
+
+```yml
+ environment:
+ MYSQL_DATABASE: laradock
+ ...
+```
+
+Change Redis default port to 1111:
+
+```yml
+ ports:
+ - "1111:6379"
+ ...
+```
+
+
+
+
+
+
+
+
+## Edit a Docker Image
+
+1 - Find the `Dockerfile` of the image you want to edit,
+
+example for `mysql` it will be `mysql/Dockerfile`.
+
+2 - Edit the file the way you want.
+
+3 - Re-build the container:
+
+```bash
+docker-compose build mysql
+```
+More info on Containers rebuilding [here](#Build-Re-build-Containers).
+
+
+
+
+
+
+
+
+## Build/Re-build Containers
+
+If you do any change to any `Dockerfile` make sure you run this command, for the changes to take effect:
+
+```bash
+docker-compose build
+```
+Optionally you can specify which container to rebuild (instead of rebuilding all the containers):
+
+```bash
+docker-compose build {container-name}
+```
+
+You might use the `--no-cache` option if you want full rebuilding (`docker-compose build --no-cache {container-name}`).
+
+
+
+
+
+
+
+
+## Add more Software (Docker Images)
+
+To add an image (software), just edit the `docker-compose.yml` and add your container details, to do so you need to be familiar with the [docker compose file syntax](https://docs.docker.com/compose/compose-file/).
+
+
+
+
+
+
+
+
+## View the Log files
+The NGINX Log file is stored in the `logs/nginx` directory.
+
+However to view the logs of all the other containers (MySQL, PHP-FPM,...) you can run this:
+
+```bash
+docker logs {container-name}
+```
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Install PHP Extensions
+
+Before installing PHP extensions, you have to decide whether you need for the `FPM` or `CLI` because each lives on a different container, if you need it for both you have to edit both containers.
+
+The PHP-FPM extensions should be installed in `php-fpm/Dockerfile-XX`. *(replace XX with your default PHP version number)*.
+
+The PHP-CLI extensions should be installed in `workspace/Dockerfile`.
+
+
+
+
+
+
+
+
+## Change the (PHP-FPM) Version
+By default **PHP-FPM 7.0** is running.
+
+>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.
+
+
+### A) Switch from PHP `7.0` to PHP `5.6`
+
+1 - Open the `docker-compose.yml`.
+
+2 - Search for `Dockerfile-70` in the PHP container section.
+
+3 - Change the version number, by replacing `Dockerfile-70` with `Dockerfile-56`, like this:
+
+```yml
+ php-fpm:
+ build:
+ context: ./php-fpm
+ dockerfile: Dockerfile-70
+ ...
+```
+
+4 - Finally rebuild the container
+
+```bash
+docker-compose build php-fpm
+```
+
+> For more details about the PHP base image, visit the [official PHP docker images](https://hub.docker.com/_/php/).
+
+
+### B) Switch from PHP `7.0` or `5.6` to PHP `5.5`
+
+We do not natively support PHP 5.5 anymore, but you can get it in few steps:
+
+1 - Clone `https://github.com/laradock/php-fpm`.
+
+3 - Rename `Dockerfile-56` to `Dockerfile-55`.
+
+3 - Edit the file `FROM php:5.6-fpm` to `FROM php:5.5-fpm`.
+
+4 - Build an image from `Dockerfile-55`.
+
+5 - Open the `docker-compose.yml` file.
+
+6 - Point `php-fpm` to your `Dockerfile-55` file.
+
+
+
+
+
+
+
+
+## Change the PHP-CLI Version
+By default **PHP-CLI 7.0** is running.
+
+>Note: it's not very essential to edit the PHP-CLI version. The PHP-CLI is only used for the Artisan Commands & Composer. It doesn't serve your Application code, this is the PHP-FPM job.
+
+The PHP-CLI is installed in the Workspace container. To change the PHP-CLI version you need to edit the `workspace/Dockerfile`.
+
+Right now you have to manually edit the `Dockerfile` or create a new one like it's done for the PHP-FPM. (consider contributing).
+
+
+
+
+
+
+
+
+## Install xDebug
+
+1 - First install `xDebug` in the Workspace and the PHP-FPM Containers:
+
+a) open the `docker-compose.yml` file
+
+b) search for the `INSTALL_XDEBUG` argument under the Workspace Container
+
+c) set it to `true`
+
+d) search for the `INSTALL_XDEBUG` argument under the PHP-FPM Container
+
+e) set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_XDEBUG=true
+ ...
+ php-fpm:
+ build:
+ context: ./php-fpm
+ args:
+ - INSTALL_XDEBUG=true
+ ...
+```
+
+2 - Re-build the containers `docker-compose build workspace php-fpm`
+
+3 - Open `laradock/workspace/xdebug.ini` and/or `laradock/php-fpm/xdebug.ini` and enable at least the following configurations:
+
+```
+xdebug.remote_autostart=1
+xdebug.remote_enable=1
+xdebug.remote_connect_back=1
+```
+
+For information on how to configure xDebug with your IDE and work it out, check this [Repository](https://github.com/LarryEitel/laravel-laradock-phpstorm).
+
+
+
+
+
+
+
+
+## Start/Stop xDebug:
+
+By installing xDebug, you are enabling it to run on startup by default.
+
+To control the behavior of xDebug (in the `php-fpm` Container), you can run the following commands from the LaraDock root folder, (at the same prompt where you run docker-compose):
+
+- Stop xDebug from running by default: `./xdebugPhpFpm stop`.
+- Start xDebug by default: `./xdebugPhpFpm start`.
+- See the status: `./xdebugPhpFpm status`.
+
+Note: If `./xdebugPhpFpm` doesn't execute and gives `Permission Denied` error the problem can be that file `xdebugPhpFpm` doesn't have execution access. This can be fixed by running `chmod` command with desired access permissions.
+
+
+
+
+
+
+
+
+## Install Deployer (Deployment tool for PHP)
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `INSTALL_DEPLOYER` argument under the Workspace Container
+
+3 - Set it to `true`
+
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_DEPLOYER=true
+ ...
+```
+
+4 - Re-build the containers `docker-compose build workspace`
+
+[**Deployer Documentation Here**](https://deployer.org/docs)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Prepare LaraDock for Production
+
+It's recommended for production to create a custom `docker-compose.yml` file. For that reason, LaraDock is shipped with `production-docker-compose.yml` which should contain only the containers you are planning to run on production (usage example: `docker-compose -f production-docker-compose.yml up -d nginx mysql redis ...`).
+
+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:
+
+```
+ports:
+ - "3306:3306"
+```
+
+To learn more about how Docker publishes ports, please read [this excellent post on the subject](https://fralef.me/docker-and-iptables.html).
+
+
+
+
+
+
+
+
+## Setup Laravel and Docker on Digital Ocean
+
+### [Full Guide Here](https://github.com/laradock/laradock/blob/master/_guides/digital_ocean.md)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Install Laravel from a Docker Container
+
+1 - First you need to enter the Workspace Container.
+
+2 - Install Laravel.
+
+Example using Composer
+
+```bash
+composer create-project laravel/laravel my-cool-app "5.2.*"
+```
+
+> We recommend using `composer create-project` instead of the Laravel installer, to install Laravel.
+
+For more about the Laravel installation click [here](https://laravel.com/docs/master#installing-laravel).
+
+
+3 - Edit `docker-compose.yml` to Map the new application path:
+
+By default, LaraDock assumes the Laravel application is living in the parent directory of the laradock folder.
+
+Since the new Laravel application is in the `my-cool-app` folder, we need to replace `../:/var/www` with `../my-cool-app/:/var/www`, as follow:
+
+```yaml
+ application:
+ image: tianon/true
+ volumes:
+ - ../my-cool-app/:/var/www
+ ...
+```
+4 - Go to that folder and start working..
+
+```bash
+cd my-cool-app
+```
+
+5 - Go back to the LaraDock installation steps to see how to edit the `.env` file.
+
+
+
+
+
+
+
+
+## Run Artisan Commands
+
+You can run artisan commands and many other Terminal commands from the Workspace container.
+
+1 - Make sure you have the workspace container running.
+
+```bash
+docker-compose up -d workspace // ..and all your other containers
+```
+
+2 - Find the Workspace container name:
+
+```bash
+docker-compose ps
+```
+
+3 - Enter the Workspace container:
+
+```bash
+docker-compose exec workspace bash
+```
+
+Add `--user=laradock` (example `docker-compose exec --user=laradock workspace bash`) to have files created as your host's user.
+
+
+4 - Run anything you want :)
+
+```bash
+php artisan
+```
+```bash
+Composer update
+```
+```bash
+phpunit
+```
+
+
+
+
+
+
+
+
+## Run Laravel Queue Worker
+
+1 - First add `php-worker` container. It will be similar as like PHP-FPM Container.
+
+a) open the `docker-compose.yml` file
+
+b) add a new service container by simply copy-paste this section below PHP-FPM container
+
+```yaml
+ php-worker:
+ build:
+ context: ./php-fpm
+ dockerfile: Dockerfile-70 # or Dockerfile-56, choose your PHP-FPM container setting
+ volumes_from:
+ - applications
+ command: php artisan queue:work
+```
+2 - Start everything up
+
+```bash
+docker-compose up -d php-worker
+```
+
+
+
+
+
+
+
+## Use Redis
+
+1 - First make sure you run the Redis Container (`redis`) with the `docker-compose up` command.
+
+```bash
+docker-compose up -d redis
+```
+
+2 - Open your Laravel's `.env` file and set the `REDIS_HOST` to `redis`
+
+```env
+REDIS_HOST=redis
+```
+
+If you don't find the `REDIS_HOST` variable in your `.env` file. Go to the database configuration file `config/database.php` and replace the default `127.0.0.1` IP with `redis` for Redis like this:
+
+```php
+'redis' => [
+ 'cluster' => false,
+ 'default' => [
+ 'host' => 'redis',
+ 'port' => 6379,
+ 'database' => 0,
+ ],
+],
+```
+
+3 - To enable Redis Caching and/or for Sessions Management. Also from the `.env` file set `CACHE_DRIVER` and `SESSION_DRIVER` to `redis` instead of the default `file`.
+
+```env
+CACHE_DRIVER=redis
+SESSION_DRIVER=redis
+```
+
+4 - Finally make sure you have the `predis/predis` package `(~1.0)` installed via Composer:
+
+```bash
+composer require predis/predis:^1.0
+```
+
+5 - You can manually test it from Laravel with this code:
+
+```php
+\Cache::store('redis')->put('LaraDock', 'Awesome', 10);
+```
+
+
+
+
+
+
+
+
+## Use Mongo
+
+1 - First install `mongo` in the Workspace and the PHP-FPM Containers:
+
+a) open the `docker-compose.yml` file
+
+b) search for the `INSTALL_MONGO` argument under the Workspace Container
+
+c) set it to `true`
+
+d) search for the `INSTALL_MONGO` argument under the PHP-FPM Container
+
+e) set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_MONGO=true
+ ...
+ php-fpm:
+ build:
+ context: ./php-fpm
+ args:
+ - INSTALL_MONGO=true
+ ...
+```
+
+2 - Re-build the containers `docker-compose build workspace php-fpm`
+
+
+
+3 - Run the MongoDB Container (`mongo`) with the `docker-compose up` command.
+
+```bash
+docker-compose up -d mongo
+```
+
+
+4 - Add the MongoDB configurations to the `config/database.php` configuration file:
+
+```php
+'connections' => [
+
+ 'mongodb' => [
+ 'driver' => 'mongodb',
+ 'host' => env('DB_HOST', 'localhost'),
+ 'port' => env('DB_PORT', 27017),
+ 'database' => env('DB_DATABASE', 'database'),
+ 'username' => '',
+ 'password' => '',
+ 'options' => [
+ 'database' => '',
+ ]
+ ],
+
+ // ...
+
+],
+```
+
+5 - Open your Laravel's `.env` file and update the following variables:
+
+- set the `DB_HOST` to your `mongo`.
+- set the `DB_PORT` to `27017`.
+- set the `DB_DATABASE` to `database`.
+
+
+6 - Finally make sure you have the `jenssegers/mongodb` package installed via Composer and its Service Provider is added.
+
+```bash
+composer require jenssegers/mongodb
+```
+More details about this [here](https://github.com/jenssegers/laravel-mongodb#installation).
+
+7 - Test it:
+
+- First let your Models extend from the Mongo Eloquent Model. Check the [documentation](https://github.com/jenssegers/laravel-mongodb#eloquent).
+- Enter the Workspace Container.
+- Migrate the Database `php artisan migrate`.
+
+
+
+
+
+
+
+
+## Use PhpMyAdmin
+
+1 - Run the phpMyAdmin Container (`phpmyadmin`) with the `docker-compose up` command. Example:
+
+```bash
+# use with mysql
+docker-compose up -d mysql phpmyadmin
+
+# use with mariadb
+docker-compose up -d mariadb phpmyadmin
+```
+
+2 - Open your browser and visit the localhost on port **8080**: `http://localhost:8080`
+
+
+
+
+
+
+
+
+## Use PgAdmin
+
+1 - Run the pgAdmin Container (`pgadmin`) with the `docker-compose up` command. Example:
+
+```bash
+docker-compose up -d postgres pgadmin
+```
+
+2 - Open your browser and visit the localhost on port **5050**: `http://localhost:5050`
+
+
+
+
+
+
+
+
+## Use Beanstalkd
+
+1 - Run the Beanstalkd Container:
+
+```bash
+docker-compose up -d beanstalkd
+```
+
+2 - Configure Laravel to connect to that container by editing the `config/queue.php` config file.
+
+a. first set `beanstalkd` as default queue driver
+b. set the queue host to beanstalkd : `QUEUE_HOST=beanstalkd`
+
+*beanstalkd is now available on default port `11300`.*
+
+3 - Require the dependency package [pda/pheanstalk](https://github.com/pda/pheanstalk) using composer.
+
+
+Optionally you can use the Beanstalkd Console Container to manage your Queues from a web interface.
+
+1 - Run the Beanstalkd Console Container:
+
+```bash
+docker-compose up -d beanstalkd-console
+```
+
+2 - Open your browser and visit `http://localhost:2080/`
+
+3 - Add the server
+
+- Host: beanstalkd
+- Port: 11300
+
+4 - Done.
+
+
+
+
+
+
+
+
+## Use ElasticSearch
+
+1 - Run the ElasticSearch Container (`elasticsearch`) with the `docker-compose up` command:
+
+```bash
+docker-compose up -d elasticsearch
+```
+
+2 - Open your browser and visit the localhost on port **9200**: `http://localhost:9200`
+
+
+### Install ElasticSearch Plugin
+
+1 - Install the ElasticSearch plugin like [delete-by-query](https://www.elastic.co/guide/en/elasticsearch/plugins/current/plugins-delete-by-query.html).
+
+```bash
+docker exec {container-name} /usr/share/elasticsearch/bin/plugin install delete-by-query
+```
+
+2 - Restart elasticsearch container
+
+```bash
+docker restart {container-name}
+```
+
+
+
+
+
+
+
+
+## Use Selenium
+
+1 - Run the Selenium Container (`selenium`) with the `docker-compose up` command. Example:
+
+```bash
+docker-compose up -d selenium
+```
+
+2 - Open your browser and visit the localhost on port **4444** at the following URL: `http://localhost:4444/wd/hub`
+
+
+
+
+
+
+
+
+## Use RethinkDB
+
+The RethinkDB is an open-source Database for Real-time Web ([RethinkDB](https://rethinkdb.com/)).
+A package ([Laravel RethinkDB](https://github.com/duxet/laravel-rethinkdb)) is being developed and was released a version for Laravel 5.2 (experimental).
+
+1 - Run the RethinkDB Container (`rethinkdb`) with the `docker-compose up` command.
+
+```bash
+docker-compose up -d rethinkdb
+```
+
+2 - Access the RethinkDB Administration Console [http://localhost:8090/#tables](http://localhost:8090/#tables) for create a database called `database`.
+
+3 - Add the RethinkDB configurations to the `config/database.php` configuration file:
+
+```php
+'connections' => [
+
+ 'rethinkdb' => [
+ 'name' => 'rethinkdb',
+ 'driver' => 'rethinkdb',
+ 'host' => env('DB_HOST', 'rethinkdb'),
+ 'port' => env('DB_PORT', 28015),
+ 'database' => env('DB_DATABASE', 'test'),
+ ]
+
+ // ...
+
+],
+```
+
+4 - Open your Laravel's `.env` file and update the following variables:
+
+- set the `DB_CONNECTION` to your `rethinkdb`.
+- set the `DB_HOST` to `rethinkdb`.
+- set the `DB_PORT` to `28015`.
+- set the `DB_DATABASE` to `database`.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## Install CodeIgniter
+
+To install CodeIgniter 3 on LaraDock all you have to do is the following simple steps:
+
+1 - Open the `docker-compose.yml` file.
+
+2 - Change `CODEIGNITER=false` to `CODEIGNITER=true`.
+
+3 - Re-build your PHP-FPM Container `docker-compose build php-fpm`.
+
+
+
+
+
+
+
+
+## Miscellaneous
+
+
+
+
+
+
+
+
+## Change the timezone
+
+To change the timezone for the `workspace` container, modify the `TZ` build argument in the Docker Compose file to one in the [TZ database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+
+For example, if I want the timezone to be `New York`:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - TZ=America/New_York
+ ...
+```
+
+We also recommend [setting the timezone in Laravel](http://www.camroncade.com/managing-timezones-with-laravel/).
+
+
+
+
+
+
+
+
+## Adding cron jobs
+
+You can add your cron jobs to `workspace/crontab/root` after the `php artisan` line.
+
+```
+* * * * * php /var/www/artisan schedule:run >> /dev/null 2>&1
+
+# Custom cron
+* * * * * root echo "Every Minute" > /var/log/cron.log 2>&1
+```
+
+Make sure you [change the timezone](#Change-the-timezone) if you don't want to use the default (UTC).
+
+
+
+
+
+
+
+
+## Access workspace via ssh
+
+You can access the `workspace` container through `localhost:2222` by setting the `INSTALL_WORKSPACE_SSH` build argument to `true`.
+
+To change the default forwarded port for ssh:
+
+```yml
+ workspace:
+ ports:
+ - "2222:22" # Edit this line
+ ...
+```
+
+
+
+
+
+
+
+
+## MySQL access from host
+
+You can forward the MySQL/MariaDB port to your host by making sure these lines are added to the `mysql` or `mariadb` section of the `docker-compose.yml` or in your [environment specific Compose](https://docs.docker.com/compose/extends/) file.
+
+```
+ports:
+ - "3306:3306"
+```
+
+
+
+
+
+
+
+
+## MySQL root access
+
+The default username and password for the root MySQL user are `root` and `root `.
+
+1 - Enter the MySQL container: `docker-compose exec mysql bash`.
+
+2 - Enter mysql: `mysql -uroot -proot` for non root access use `mysql -uhomestead -psecret`.
+
+3 - See all users: `SELECT User FROM mysql.user;`
+
+4 - Run any commands `show databases`, `show tables`, `select * from.....`.
+
+
+
+
+
+
+
+
+## Change MySQL port
+
+Modify the `mysql/my.cnf` file to set your port number, `1234` is used as an example.
+
+```
+[mysqld]
+port=1234
+```
+
+If you need MySQL access from your host, do not forget to change the internal port number (`"3306:3306"` -> `"3306:1234"`) in the docker-compose configuration file.
+
+
+
+
+
+
+
+
+## Use custom Domain (instead of the Docker IP)
+
+Assuming your custom domain is `laravel.dev`
+
+1 - Open your `/etc/hosts` file and map your localhost address `127.0.0.1` to the `laravel.dev` domain, by adding the following:
+
+```bash
+127.0.0.1 laravel.dev
+```
+
+2 - Open your browser and visit `{http://laravel.dev}`
+
+
+Optionally you can define the server name in the NGINX configuration file, like this:
+
+```conf
+server_name laravel.dev;
+```
+
+
+
+
+
+
+
+
+## Enable Global Composer Build Install
+
+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.
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `COMPOSER_GLOBAL_INSTALL` argument under the Workspace Container and set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - COMPOSER_GLOBAL_INSTALL=true
+ ...
+```
+3 - Now add your dependencies to `workspace/composer.json`
+
+4 - Re-build the Workspace Container `docker-compose build workspace`
+
+
+
+
+
+
+
+
+## Install Prestissimo
+
+[Prestissimo](https://github.com/hirak/prestissimo) is a plugin for composer which enables parallel install functionality.
+
+1 - Enable Running Global Composer Install during the Build:
+
+Click on this [Enable Global Composer Build Install](#Enable-Global-Composer-Build-Install) and do steps 1 and 2 only then continue here.
+
+2 - Add prestissimo as requirement in Composer:
+
+a - Now open the `workspace/composer.json` file
+
+b - Add `"hirak/prestissimo": "^0.3"` as requirement
+
+c - Re-build the Workspace Container `docker-compose build workspace`
+
+
+
+
+
+
+
+
+## Install Node + NVM
+
+To install NVM and NodeJS in the Workspace container
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `INSTALL_NODE` argument under the Workspace Container and set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_NODE=true
+ ...
+```
+
+3 - Re-build the container `docker-compose build workspace`
+
+
+
+
+
+
+
+
+## Install Node + YARN
+
+Yarn is a new package manager for JavaScript. It is so faster than npm, which you can find [here](http://yarnpkg.com/en/compare).To install NodeJS and [Yarn](https://yarnpkg.com/) in the Workspace container:
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `INSTALL_NODE` and `INSTALL_YARN` argument under the Workspace Container and set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_NODE=true
+ - INSTALL_YARN=true
+ ...
+```
+
+3 - Re-build the container `docker-compose build workspace`
+
+
+
+
+
+
+
+
+## Install Linuxbrew
+
+Linuxbrew is a package manager for Linux. It is the Linux version of MacOS Homebrew and can be found [here](http://linuxbrew.sh). To install Linuxbrew in the Workspace container:
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `INSTALL_LINUXBREW` argument under the Workspace Container and set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_LINUXBREW=true
+ ...
+```
+
+3 - Re-build the container `docker-compose build workspace`
+
+
+
+
+
+
+
+
+## Common Terminal Aliases
+When you start your docker container, LaraDock will copy the `aliases.sh` file located in the `laradock/workspace` directory and add sourcing to the container `~/.bashrc` file.
+
+You are free to modify the `aliases.sh` as you see fit, adding your own aliases (or function macros) to suit your requirements.
+
+
+
+
+
+
+
+## Install Aerospike extension
+
+1 - First install `aerospike` in the Workspace and the PHP-FPM Containers:
+
+a) open the `docker-compose.yml` file
+
+b) search for the `INSTALL_AEROSPIKE_EXTENSION` argument under the Workspace Container
+
+c) set it to `true`
+
+d) search for the `INSTALL_AEROSPIKE_EXTENSION` argument under the PHP-FPM Container
+
+e) set it to `true`
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_AEROSPIKE_EXTENSION=true
+ ...
+ php-fpm:
+ build:
+ context: ./php-fpm
+ args:
+ - INSTALL_AEROSPIKE_EXTENSION=true
+ ...
+```
+
+2 - Re-build the containers `docker-compose build workspace php-fpm`
+
+
+
+
+
+
+
+
+## Install Laravel Envoy (Envoy Task Runner)
+
+1 - Open the `docker-compose.yml` file
+
+2 - Search for the `INSTALL_LARAVEL_ENVOY` argument under the Workspace Container
+
+3 - Set it to `true`
+
+
+It should be like this:
+
+```yml
+ workspace:
+ build:
+ context: ./workspace
+ args:
+ - INSTALL_LARAVEL_ENVOY=true
+ ...
+```
+
+4 - Re-build the containers `docker-compose build workspace`
+
+[**Laravel Envoy Documentation Here**](https://laravel.com/docs/5.3/envoy)
+
+
+
+
+
+
+
+
+
+## PHPStorm Debugging Guide
+Remote debug Laravel web and phpunit tests.
+
+[**Debugging Guide Here**](https://github.com/laradock/laradock/blob/master/_guides/phpstorm.md)
+
+
+
+
+
+
+
+
+
+## Keep track of your LaraDock changes
+
+1. Fork the LaraDock repository.
+2. Use that fork as a submodule.
+3. Commit all your changes to your fork.
+4. Pull new stuff from the main repository from time to time.
+
+
+
+
+
+
+
+
+
+## Upgrading LaraDock
+
+Moving from Docker Toolbox (VirtualBox) to Docker Native (for Mac/Windows). Requires upgrading LaraDock from v3.* to v4.*:
+
+1. Stop the docker VM `docker-machine stop {default}`
+2. Install Docker for [Mac](https://docs.docker.com/docker-for-mac/) or [Windows](https://docs.docker.com/docker-for-windows/).
+3. Upgrade LaraDock to `v4.*.*` (`git pull origin master`)
+4. Use LaraDock as you used to do: `docker-compose up -d nginx mysql`.
+
+**Note:** If you face any problem with the last step above: rebuild all your containers
+`docker-compose build --no-cache`
+"Warning Containers Data might be lost!"
+
+
+
+
+
+
+
+
+
+## Improve speed on MacOS
+
+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.
+
+> How to share files using NFS (d4m-nfs)
+
+[d4m-nfs](https://github.com/IFSight/d4m-nfs) automatically mount NFS volume instead of osxfs one.
+
+1) Update the Docker [File Sharing] preferences:
+
+Click on the Docker Icon > Preferences > (remove everything form the list except `/tmp`).
+
+2) Restart Docker.
+
+3) Clone the [d4m-nfs](https://github.com/IFSight/d4m-nfs) repository to your `home` directory.
+
+```bash
+git clone https://github.com/IFSight/d4m-nfs ~/d4m-nfs
+```
+
+4) Create (or edit) the file `~/d4m-nfs/etc/d4m-nfs-mounts.txt`, and write the follwing configuration in it:
+
+```txt
+/Users:/Users
+/Volumes:/Volumes
+/private:/private
+```
+
+5) Create (or edit) the file `/etc/exports`, make sure it exists and is empty. (There may be collisions if you come from Vagrant or if you already executed the `d4m-nfs.sh` script before).
+
+
+6) Run the `d4m-nfs.sh` script:
+
+```bash
+~/d4m-nfs/d4m-nfs.sh
+```
+
+That's it! Run your containers.. Example:
+
+```bash
+docker-compose up -d nginx mysql
+```
+
+**Note:** If you faced any errors, try restarting Docker, and make sure you have no spaces in the `d4m-nfs-mounts.txt` file, and your `/etc/exports` file is clear.
+
+
+
+
+
+
+
+
+
+## Common Problems
+
+*Here's a list of the common problems you might face, and the possible solutions.*
+
+
+
+
+
+
+
+
+## I see a blank (white) page instead of the Laravel 'Welcome' page!
+
+Run the following command from the Laravel root directory:
+
+```bash
+sudo chmod -R 777 storage bootstrap/cache
+```
+
+
+
+
+
+
+## I see "Welcome to nginx" instead of the Laravel App!
+
+Use `http://127.0.0.1` instead of `http://localhost` in your browser.
+
+
+
+
+
+
+## I see an error message containing `address already in use` or `port is already allocated`
+
+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 `apache`/`httpd` service or other development tools you have installed.
+
+
+
+
+
+
+## I get NGINX error 404 Not Found on Windows.
+
+1. Go to docker Settings on your Windows machine.
+2. Click on the `Shared Drives` tab and check the drive that contains your project files.
+3. Enter your windows username and password.
+4. Go to the `reset` tab and click restart docker.
+
+
+
+
+
+
+## The time in my services does not match the current time
+
+1. Make sure you've [changed the timezone](#Change-the-timezone).
+2. Stop and rebuild the containers (`docker-compose up -d --build `)
+
+
+
+
+
+
+## I get MySQL connection refused
+
+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:
+
+* Option A
+ 1. Check your running Laravel application IP by dumping `Request::ip()` variable using `dd(Request::ip())` anywhere on your application. The result is the IP of your Laravel container.
+ 2. Change the `DB_HOST` variable on env with the IP that you received from previous step.
+* Option B
+ 1. Change the `DB_HOST` value to the same name as the MySQL docker container. The LaraDock docker-compose file currently has this as `mysql`
diff --git a/docs/_settings/content/getting-started/index.md b/docs/_settings/content/getting-started/index.md
new file mode 100644
index 0000000..858f95b
--- /dev/null
+++ b/docs/_settings/content/getting-started/index.md
@@ -0,0 +1,181 @@
+---
+title: Getting Started
+type: index
+weight: 2
+---
+
+## Requirements
+
+- [Git](https://git-scm.com/downloads)
+- [Docker](https://www.docker.com/products/docker/) `>= 1.12`
+
+
+
+
+
+
+
+## Installation
+
+Choose the setup the best suits your needs.
+
+#### A) Setup for Single Project:
+*(In case you want a Docker environment for each project)*
+
+##### A.1) Setup environment in existing Project:
+*(In case you already have a project, and you want to setup an environment to run it)*
+
+1 - Clone this repository on your project root directory:
+
+```bash
+git submodule add https://github.com/Laradock/laradock.git
+```
+
+*Note 1: If you are not yet using Git for your PHP project, you can use `git clone https://github.com/Laradock/laradock.git` instead.*
+
+*Note 2: To keep track of your LaraDock changes, between your projects and also keep LaraDock updated. [Check this](#keep-tracking-LaraDock)*
+
+*Note 3: In this case the folder structure will be like this:*
+
+```
+- project1
+ - laradock
+- project2
+ - laradock
+```
+
+##### A.2) Setup environment first then create project:
+*(In case you don't have a project, and you want to create your project inside the Docker environment)*
+
+1 - Clone this repository anywhere on your machine:
+
+```bash
+git clone https://github.com/laradock/laradock.git
+```
+Note: In this case the folder structure will be like this:
+
+```
+- projects
+ - laradock
+ - myProject
+```
+
+2 - Edit the `docker-compose.yml` file to map to your project directory once you have it (example: `- ../myProject:/var/www`).
+
+3 - Stop and re-run your docker-compose command for the changes to take place.
+
+```
+docker-compose stop && docker-compose up -d XXXX YYYY ZZZZ ....
+```
+
+
+#### B) Setup for Multiple Projects:
+
+1 - Clone this repository anywhere on your machine:
+
+```bash
+git clone https://github.com/laradock/laradock.git
+```
+
+2 - Edit the `docker-compose.yml` file to map to your projects directories:
+
+```
+ applications:
+ image: tianon/true
+ volumes:
+ - ../project1/:/var/www/project1
+ - ../project2/:/var/www/project2
+```
+
+3 - You can access all sites by visiting `http://localhost/project1/public` and `http://localhost/project2/public` but of course that's not very useful so let's setup NGINX quickly.
+
+
+4 - Go to `nginx/sites` and copy `sample.conf.example` to `project1.conf` then to `project2.conf`
+
+5 - Open the `project1.conf` file and edit the `server_name` and the `root` as follow:
+
+```
+ server_name project1.dev;
+ root /var/www/project1/public;
+```
+Do the same for each project `project2.conf`, `project3.conf`,...
+
+6 - Add the domains to the **hosts** files.
+
+```
+127.0.0.1 project1.dev
+```
+
+7 - Create your project Databases. Right now you have to do it manually by entering your DB container, until we automate it soon.
+
+
+
+
+
+
+
+## Usage
+
+**Read Before starting:**
+
+If you are using **Docker Toolbox** (VM), do one of the following:
+
+- Upgrade to Docker [Native](https://www.docker.com/products/docker) for Mac/Windows (Recommended). Check out [Upgrading LaraDock](#upgrading-laradock)
+- Use LaraDock v3.* (Visit the `LaraDock-ToolBox` [Branch](https://github.com/laradock/laradock/tree/LaraDock-ToolBox)).
+
+
+
+>**Warning:** If you used an older version of LaraDock it's highly recommended to rebuild the containers you need to use [see how you rebuild a container](#Build-Re-build-Containers) in order to prevent errors as much as possible.
+
+
+
+1 - Run Containers: *(Make sure you are in the `laradock` folder before running the `docker-compose` commands).*
+
+
+**Example:** Running NGINX and MySQL:
+
+```bash
+docker-compose up -d nginx mysql
+```
+
+**Note**: The `workspace` and `php-fpm` will run automatically in most of the cases, so no need to specify them in the `up` command. If you couldn't find them running then you need specify them as follow: `docker-compose up -d nginx php-fpm mysql workspace`.
+
+
+You can select your own combination of Containers form the list below:
+
+`nginx`, `hhvm`, `php-fpm`, `mysql`, `redis`, `postgres`, `mariadb`, `neo4j`, `mongo`, `apache2`, `caddy`, `memcached`, `beanstalkd`, `beanstalkd-console`, `rabbitmq`, `workspace`, `phpmyadmin`, `aerospike`, `pgadmin`, `elasticsearch`, `rethinkdb`.
+
+
+
+2 - Enter the Workspace container, to execute commands like (Artisan, Composer, PHPUnit, Gulp, ...).
+
+```bash
+docker-compose exec workspace bash
+```
+
+Alternatively, for Windows PowerShell users: execute the following command to enter any running container:
+
+```bash
+docker exec -it {workspace-container-id} bash
+```
+
+**Note:** You can add `--user=laradock` (example `docker-compose exec --user=laradock workspace bash`) to have files created as your host's user. (you can change the PUID (User id) and PGID (group id) variables from the `docker-compose.yml`).
+
+
+3 - Edit your project configurations.
+
+Open your `.env` file and set the `DB_HOST` to `mysql`:
+
+```env
+DB_HOST=mysql
+```
+
+*If you want to use Laravel and you don't have it installed yet, see [How to Install Laravel in a Docker Container](#Install-Laravel).*
+
+
+4 - Open your browser and visit your localhost address (`http://localhost/`).
+
+
+**Debugging**: if you are facing any problem here check the [Debugging](#debugging) section.
+
+If you need a special support. Contact me, more details in the [Help & Questions](#Help) section.
diff --git a/docs/_settings/content/help/index.md b/docs/_settings/content/help/index.md
new file mode 100644
index 0000000..db758fd
--- /dev/null
+++ b/docs/_settings/content/help/index.md
@@ -0,0 +1,9 @@
+---
+title: Help & Questions
+type: index
+weight: 5
+---
+
+Join the chat room on [Gitter](https://gitter.im/LaraDock/laradock) and get help and support from the community.
+
+You can as well can open an [issue](https://github.com/laradock/laradock/issues) on Github (will be labeled as Question) and discuss it with people on [Gitter](https://gitter.im/LaraDock/laradock).
diff --git a/docs/_settings/content/index.md b/docs/_settings/content/index.md
new file mode 100644
index 0000000..56c08a8
--- /dev/null
+++ b/docs/_settings/content/index.md
@@ -0,0 +1,5 @@
+---
+title: Welcome
+type: index
+weight: 0
+---
diff --git a/docs/_settings/content/introduction/index.md b/docs/_settings/content/introduction/index.md
new file mode 100644
index 0000000..850796c
--- /dev/null
+++ b/docs/_settings/content/introduction/index.md
@@ -0,0 +1,196 @@
+---
+title: Introduction
+type: index
+weight: 1
+---
+
+LaraDock strives to make the PHP development experience easier and faster.
+
+It contains pre-packaged Docker Images that provides you a wonderful *development* environment without requiring you to install PHP, NGINX, MySQL, Redis, and any other software on your machines.
+
+LaraDock is configured to run Laravel Apps by default, and it can be modified to run all kinds of PHP Apps (Symfony, CodeIgniter, WordPress, Drupal...).
+
+
+
+
+## Quick Overview
+
+Let's see how easy it is to install `NGINX`, `PHP`, `Composer`, `MySQL`, `Redis` and `beanstalkd`:
+
+1 - Clone LaraDock inside your PHP project:
+
+```shell
+git clone https://github.com/Laradock/laradock.git
+```
+
+2 - Enter the laradock folder and run this command:
+
+```shell
+docker-compose up -d nginx mysql redis beanstalkd
+```
+
+3 - Open your `.env` file and set the following:
+
+```shell
+DB_HOST=mysql
+REDIS_HOST=redis
+QUEUE_HOST=beanstalkd
+```
+
+4 - Open your browser and visit localhost: `http://localhost`.
+
+```shell
+That's it! enjoy :)
+```
+
+
+
+
+
+
+
+
+## What is Docker?
+
+[Docker](https://www.docker.com) is an open-source project that automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of [operating-system-level virtualization](https://en.wikipedia.org/wiki/Operating-system-level_virtualization) on Linux, Mac OS and Windows.
+
+
+
+
+
+
+
+## Why Docker not Vagrant!?
+
+[Vagrant](https://www.vagrantup.com) creates Virtual Machines in minutes while Docker creates Virtual Containers in seconds.
+
+Instead of providing a full Virtual Machines, like you get with Vagrant, Docker provides you **lightweight** Virtual Containers, that share the same kernel and allow to safely execute independent processes.
+
+In addition to the speed, Docker gives tons of features that cannot be achieved with Vagrant.
+
+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).
+
+
+
+
+
+
+
+## LaraDock VS Homestead (For Laravel Developers)
+
+> LaraDock It's like Laravel Homestead but for Docker instead of Vagrant.
+
+LaraDock and [Homestead](https://laravel.com/docs/master/homestead) both give you complete virtual development environments. (Without the need to install and configure every single software on your own Operating System).
+
+- Homestead is a tool that controls Vagrant for you (using Homestead special commands). And Vagrant manages your Virtual Machine.
+
+- LaraDock is a tool that controls Docker for you (using Docker & Docker Compose official commands). And Docker manages your Virtual Containers.
+
+Running a virtual container is much faster than running a full virtual Machine. Thus **LaraDock is much faster than Homestead**.
+
+
+
+
+
+
+
+
+
+## Demo Video
+
+What's better than a **Demo Video**:
+
+- LaraDock [v4.*](https://www.youtube.com/watch?v=TQii1jDa96Y)
+- LaraDock [v2.*](https://www.youtube.com/watch?v=-DamFMczwDA)
+- LaraDock [v0.3](https://www.youtube.com/watch?v=jGkyO6Is_aI)
+- LaraDock [v0.1](https://www.youtube.com/watch?v=3YQsHe6oF80)
+
+
+
+
+
+
+
+
+## Features
+
+- Easy switch between PHP versions: 7.0, 5.6, 5.5...
+- Choose your favorite database engine: MySQL, Postgres, MariaDB...
+- Run your own combination of software: Memcached, HHVM, Beanstalkd...
+- Every software runs on a separate container: PHP-FPM, NGINX, PHP-CLI...
+- Easy to customize any container, with simple edit to the `Dockerfile`.
+- All Images extends from an official base Image. (Trusted base Images).
+- Pre-configured NGINX for Laravel.
+- Easy to apply configurations inside containers.
+- Clean and well structured Dockerfiles (`Dockerfile`).
+- Latest version of the Docker Compose file (`docker-compose`).
+- Everything is visible and editable.
+- Fast Images Builds.
+- More to come every week..
+
+
+
+
+
+
+
+
+## Supported Software (Containers)
+
+- **Database Engines:**
+ - MySQL
+ - PostgreSQL
+ - MariaDB
+ - MongoDB
+ - Neo4j
+ - RethinkDB
+- **Cache Engines:**
+ - Redis
+ - Memcached
+ - Aerospike
+- **PHP Servers:**
+ - NGINX
+ - Apache2
+ - Caddy
+- **PHP Compilers:**
+ - PHP-FPM
+ - HHVM
+- **Message Queuing Systems:**
+ - Beanstalkd
+ - Beanstalkd Console
+ - RabbitMQ
+ - RabbitMQ Console
+- **Tools:**
+ - PhpMyAdmin
+ - PgAdmin
+ - ElasticSearch
+ - Selenium
+ - Workspace
+ - PHP7-CLI
+ - Composer
+ - Git
+ - Linuxbrew
+ - Node
+ - Gulp
+ - SQLite
+ - xDebug
+ - Envoy
+ - Deployer
+ - Vim
+ - Yarn
+ - ... Many other supported tools are not documented. (Will be updated soon)
+
+>If you can't find your Software, build it yourself and add it to this list. Contributions are welcomed :)
+
+
+
+
+
+
+
+
+## Chat with us
+
+You are welcome to join our chat room on Gitter.
+
+[![Gitter](https://badges.gitter.im/LaraDock/laradock.svg)](https://gitter.im/LaraDock/laradock?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
diff --git a/docs/_settings/content/license/index.md b/docs/_settings/content/license/index.md
new file mode 100644
index 0000000..d65e5ab
--- /dev/null
+++ b/docs/_settings/content/license/index.md
@@ -0,0 +1,7 @@
+---
+title: License
+type: index
+weight: 7
+---
+
+[MIT License](https://github.com/laradock/laradock/blob/master/LICENSE) (MIT)
diff --git a/docs/_settings/content/related-projects/index.md b/docs/_settings/content/related-projects/index.md
new file mode 100644
index 0000000..f4b4a42
--- /dev/null
+++ b/docs/_settings/content/related-projects/index.md
@@ -0,0 +1,18 @@
+---
+title: Related Projects
+type: index
+weight: 4
+---
+
+LaraDock related projects:
+
+* [LaraDock CLI](https://github.com/lorinlee/laradock-cli) by [LorinLee](https://github.com/lorinlee)
+* [LaraDock Env](https://github.com/bagart/laradock_env) by [BAGArt](https://github.com/bagart)
+* [Klaradock](https://github.com/poyhsiao/Klaradock) by [Kim Hsiao](https://github.com/poyhsiao)
+* [Ansible Laradock Kubernetes](https://github.com/sifat-rahim/ansible-laradock-kubernetes) by [Sifat Rahim](https://github.com/sifat-rahim)
+These Docker Compose projects have piqued our interest:
+* [MageDock](https://github.com/ojhaujjwal/magedock) by [Ujjwal Ojha](https://github.com/ojhaujjwal)
+* [RubyDev-Dock](https://github.com/scudelletti/rubydev-dock) by [Diogo Scudelletti](https://github.com/scudelletti)
+* [NoDock](https://github.com/Osedea/nodock) by [Osedea](https://github.com/Osedea)
+
+If you want your project listed here, please open an issue.
diff --git a/docs/_settings/static/.gitkeep b/docs/_settings/static/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/docs/_settings/themes/hugo-material-docs/CHANGELOG.md b/docs/_settings/themes/hugo-material-docs/CHANGELOG.md
new file mode 100644
index 0000000..04cec42
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/CHANGELOG.md
@@ -0,0 +1,29 @@
+# Changelog
+
+
+### 11th May 2016
+
+#### Add templates for section lists
+
+Sections such as www.example.com/foo/ will now be rendered with a list of all pages that are part of this section. The list shows the pages' title and a summary of their content.
+
+[Show me the diff](https://github.com/digitalcraftsman/hugo-material-docs/commit/1f8393a8d4ce1b8ee3fc7d87be05895c12810494)
+
+### 22nd March 2016
+
+#### Changing setup for Google Analytics
+
+Formerly, the tracking id for Google Analytics was set like below:
+
+```toml
+[params]
+ google_analytics = ["UA-XXXXXXXX-X", "auto"]
+```
+
+Now the theme uses Hugo's own Google Analytics config option. The variable moved outside the scope of `params` and the setup requires only the tracking id as a string:
+
+```toml
+googleAnalytics = "UA-XXXXXXXX-X"
+```
+
+[Show me the diff](https://github.com/digitalcraftsman/hugo-material-docs/commit/fa10c8eef935932426d46b662a51f29a5e0d48e2)
\ No newline at end of file
diff --git a/docs/_settings/themes/hugo-material-docs/LICENSE.md b/docs/_settings/themes/hugo-material-docs/LICENSE.md
new file mode 100644
index 0000000..1a5879b
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/LICENSE.md
@@ -0,0 +1,20 @@
+Copyright (c) 2016 Digitalcraftsman
+Copyright (c) 2016 Martin Donath
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to
+deal in the Software without restriction, including without limitation the
+rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+sell copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
+IN THE SOFTWARE.
\ No newline at end of file
diff --git a/docs/_settings/themes/hugo-material-docs/README.md b/docs/_settings/themes/hugo-material-docs/README.md
new file mode 100644
index 0000000..efcc807
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/README.md
@@ -0,0 +1,40 @@
+# Material Docs
+
+A material design theme for [Hugo](https://gohugo.io).
+
+[![Screenshot](https://raw.githubusercontent.com/digitalcraftsman/hugo-material-docs/master/static/images/screen.png)](https://digitalcraftsman.github.io/hugo-material-docs/)
+
+## Quick start
+
+Install with `git`:
+
+
+ git clone https://github.com/digitalcraftsman/hugo-material-docs.git themes/hugo-material-docs
+
+
+Next, take a look in the `exampleSite` folder at. This directory contains an example config file and the content for the demo. It serves as an example setup for your documentation.
+
+Copy at least the `config.toml` in the root directory of your website. Overwrite the existing config file if necessary.
+
+Hugo includes a development server, so you can view your changes as you go -
+very handy. Spin it up with the following command:
+
+``` sh
+hugo server
+```
+
+Now you can go to [localhost:1313](http://localhost:1313) and the Material
+theme should be visible. For detailed installation instructions visit the [demo](http://themes.gohugo.io/theme/material-docs/).
+
+Noteworthy changes of this theme are listed in the [changelog](https://github.com/digitalcraftsman/hugo-material-docs/blob/master/CHANGELOG.md).
+
+## Acknowledgements
+
+A big thank you to [Martin Donath](https://github.com/squidfunk). He created the original [Material theme](https://github.com/squidfunk/mkdocs-material) for Hugo's companion [MkDocs](http://www.mkdocs.org/). This port wouldn't be possible without him.
+
+Furthermore, thanks to [Steve Francia](https://gihub.com/spf13) for creating Hugo and the [awesome community](https://github.com/spf13/hugo/graphs/contributors) around the project.
+
+## License
+
+The theme is released under the MIT license. Read the [license](https://github.com/digitalcraftsman/hugo-material-docs/blob/master/LICENSE.md) for more information.
+
diff --git a/docs/_settings/themes/hugo-material-docs/archetypes/default.md b/docs/_settings/themes/hugo-material-docs/archetypes/default.md
new file mode 100644
index 0000000..a49ba48
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/archetypes/default.md
@@ -0,0 +1,2 @@
+---
+---
\ No newline at end of file
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/config.toml b/docs/_settings/themes/hugo-material-docs/exampleSite/config.toml
new file mode 100755
index 0000000..85c6352
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/config.toml
@@ -0,0 +1,78 @@
+baseurl = "https://example.org/"
+languageCode = "en-us"
+title = "Material Docs"
+theme = "hugo-material-docs"
+metadataformat = "yaml"
+canonifyurls = true
+# Enable Google Analytics by entering your tracking id
+googleAnalytics = ""
+
+[params]
+ # General information
+ author = "Digitalcraftsman"
+ description = "A material design theme for documentations."
+ copyright = "Released under the MIT license"
+
+ # Repository
+ provider = "GitHub"
+ repo_url = "https://github.com/digitalcraftsman/hugo-material-docs"
+
+ version = "1.0.0"
+ logo = "images/logo.png"
+ favicon = ""
+
+ permalink = "#"
+
+ # Custom assets
+ custom_css = []
+ custom_js = []
+
+ # Syntax highlighting theme
+ highlight_css = ""
+
+ [params.palette]
+ primary = "red"
+ accent = "teal"
+
+ [params.font]
+ text = "Ubuntu"
+ code = "Ubuntu Mono"
+
+
+[social]
+ twitter = ""
+ github = "digitalcraftsman"
+ email = "hello@email.com"
+
+
+[[menu.main]]
+ name = "Material"
+ url = "/"
+ weight = 0
+
+[[menu.main]]
+ name = "Getting started"
+ url = "getting-started/"
+ weight = 10
+
+[[menu.main]]
+ name = "Adding content"
+ url = "adding-content/"
+ weight = 20
+
+[[menu.main]]
+ name = "Roadmap"
+ url = "roadmap/"
+ weight = 30
+
+[[menu.main]]
+ name = "License"
+ url = "license/"
+ weight = 40
+
+
+[blackfriday]
+ smartypants = true
+ fractions = true
+ smartDashes = true
+ plainIDAnchors = true
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/content/adding-content/index.md b/docs/_settings/themes/hugo-material-docs/exampleSite/content/adding-content/index.md
new file mode 100644
index 0000000..2fce91e
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/content/adding-content/index.md
@@ -0,0 +1,61 @@
+---
+date: 2016-03-09T19:56:50+01:00
+title: Adding content
+weight: 20
+---
+
+## Hello world
+
+Let's create our first content file for your documentation. Open a terminal and add the following command for each new file you want to add. Replace `` with a general term that describes your document in detail.
+
+```sh
+hugo new /filename.md
+```
+
+Visitors of your website will find the final document under `www.example.com//filename/`.
+
+Since it's possible to have multiple content files in the same section I recommend to create at least one `index.md` file per section. This ensures that users will find an index page under `www.example.com/`.
+
+## Homepage
+
+To add content to the homepage you need to add a small indicator to the frontmatter of the content file:
+
+```toml
+type: index
+```
+
+Otherwise the theme will not be able to find the corresponding content file.
+
+## Table of contents
+
+You maybe noticed that the menu on the left contains a small table of contents of the current page. All `
` tags (`## Headline` in Markdown) will be added automatically.
+
+## Admonitions
+
+Admonition is a handy feature that adds block-styled side content to your documentation, for example hints, notes or warnings. It can be enabled by using the corresponding [shortcodes](http://gohugo.io/extras/shortcodes/) inside your content:
+
+```go
+{{* note title="Note" */>}}
+Nothing to see here, move along.
+{{* /note */>}}
+```
+
+This will print the following block:
+
+{{< note title="Note" >}}
+Nothing to see here, move along.
+{{< /note >}}
+
+The shortcode adds a neutral color for the note class and a red color for the warning class. You can also add a custom title:
+
+```go
+{{* warning title="Don't try this at home" */>}}
+Nothing to see here, move along.
+{{* /warning */>}}
+```
+
+This will print the following block:
+
+{{< warning title="Don't try this at home" >}}
+Nothing to see here, move along.
+{{< /warning >}}
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/content/getting-started/index.md b/docs/_settings/themes/hugo-material-docs/exampleSite/content/getting-started/index.md
new file mode 100644
index 0000000..e501c04
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/content/getting-started/index.md
@@ -0,0 +1,240 @@
+---
+date: 2016-03-09T00:11:02+01:00
+title: Getting started
+weight: 10
+---
+
+## Installation
+
+### Installing Hugo
+
+Hugo itself is just a single binary without dependencies on expensive runtimes like Ruby, Python or PHP and without dependencies on any databases. You just need to download the [latest version](https://github.com/spf13/hugo/releases). For more information read the official [installation guides](http://gohugo.io/overview/installing/).
+
+Let's make sure Hugo is set up as expected. You should see a similar version number in your terminal:
+
+```sh
+hugo version
+# Hugo Static Site Generator v0.15 BuildDate: 2016-01-03T12:47:47+01:00
+```
+
+### Installing Material
+
+Next, assuming you have Hugo up and running the `hugo-material-docs` theme can be installed with `git`:
+
+```sh
+# create a new Hugo website
+hugo new site my-awesome-docs
+
+# move into the themes folder of your website
+cd my-awesome-docs/themes/
+
+# download the theme
+git clone git@github.com:digitalcraftsman/hugo-material-docs.git
+```
+
+## Setup
+
+Next, take a look in the `exampleSite` folder at `themes/hugo-material-docs/`. This directory contains an example config file and the content that you are currently reading. It serves as an example setup for your documentation.
+
+Copy at least the `config.toml` in the root directory of your website. Overwrite the existing config file if necessary.
+
+Hugo includes a development server, so you can view your changes as you go -
+very handy. Spin it up with the following command:
+
+``` sh
+hugo server
+```
+
+Now you can go to [localhost:1313](http://localhost:1313) and the Material
+theme should be visible. You can now start writing your documentation, or read
+on and customize the theme through some options.
+
+## Configuration
+
+Before you are able to deploy your documentation you should take a few minute to adjust some information in the `config.toml`. Open the file in an editor:
+
+```toml
+baseurl = "https://example.com/"
+languageCode = "en-us"
+title = "Material Docs"
+
+[params]
+ # General information
+ author = "Digitalcraftsman"
+ description = "A material design theme for documentations."
+ copyright = "Released under the MIT license"
+```
+
+## Options
+
+### Github integration
+
+If your project is hosted on GitHub, add the repository link to the
+configuration. If the `provider` equals **GitHub**, the Material theme will
+add a download and star button, and display the number of stars:
+
+```toml
+[params]
+ # Repository
+ provider = "GitHub"
+ repo_url = "https://github.com/digitalcraftsman/hugo-material-docs"
+```
+
+### Adding a version
+
+In order to add the current version next to the project banner inside the
+drawer, you can set the variable `version`:
+
+```toml
+[params]
+ version = "1.0.0"
+```
+
+This will also change the link behind the download button to point to the
+archive with the respective version on GitHub, assuming a release tagged with
+this exact version identifier.
+
+### Adding a logo
+
+If your project has a logo, you can add it to the drawer/navigation by defining
+the variable `logo`. Ideally, the image of your logo should have
+rectangular shape with a minimum resolution of 128x128 and leave some room
+towards the edges. The logo will also be used as a web application icon on iOS.
+Either save your logo somewhere in the `static/` folder and reference the file relative to this location or use an external URL:
+
+```toml
+[params]
+ logo = "images/logo.png"
+```
+
+### Adding a custom favicon
+
+Favicons are small small icons that are displayed in the tabs right next to the title of the current page. As with the logo above you need to save your favicon in `static/` and link it relative to this folder or use an external URL:
+
+```toml
+[params]
+ favicon = "favicon.ico"
+```
+
+### Google Analytics
+
+You can enable Google Analytics by replacing `UA-XXXXXXXX-X` with your own tracking code.
+
+```toml
+googleAnalytics = "UA-XXXXXXXX-X"
+```
+
+### Small tweaks
+
+This theme provides a simple way for making small adjustments, that is changing
+some margins, centering text, etc. The `custom_css` and `custom_js` option allow you to add further CSS and JS files. They can either reside locally in the `/static` folder or on an external server, e.g. a CDN. In both cases use either the relative path to `/static` or the absolute URL to the external ressource.
+
+
+```toml
+[params]
+ # Custom assets
+ custom_css = [
+ "foo.css",
+ "bar.css"
+ ]
+
+ custom_js = ["buzz.js"]
+```
+
+### Changing the color palette
+
+Material defines a default hue for every primary and accent color on Google's
+material design [color palette][]. This makes it very easy to change the overall look of the theme. Just set the variables `palette.primary` and `palette.accent` to one of the colors defined in the palette:
+
+```toml
+[params.palette]
+ primary = "red"
+ accent = "light-green"
+```
+
+Color names can be written upper- or lowercase but must match the names of the
+material design [color palette](http://www.materialui.co/colors). Valid values are: _red_, _pink_, _purple_, _deep purple_, _indigo_, _blue_, _light-blue_, _cyan_, _teal_, _green_, _light-green_,
+_lime_, _yellow_, _amber_, _orange_, _deep-orange_, _brown_, _grey_ and
+_blue-grey_. The last three colors can only be used as a primary color.
+
+![Color palette](/images/colors.png)
+
+If the color is set via this configuration, an additional CSS file called
+`palettes.css` is included that defines the color palettes.
+
+### Changing the font family
+
+Material uses the [Ubuntu font family](http://font.ubuntu.com) by default, specifically the regular sans-serif type for text and the monospaced type for code. Both fonts are loaded from [Google Fonts](https://www.google.com/fonts) and can be easily changed to other fonts, like for example Google's own [Roboto font](https://www.google.com/fonts/specimen/Roboto):
+
+```toml
+[params.font]
+ text = "Roboto"
+ code = "Roboto Mono"
+```
+
+The text font will be loaded in font-weights 400 and **700**, the monospaced
+font in regular weight.
+
+### Syntax highlighting
+
+This theme uses the popular [Highlight.js](https://highlightjs.org/) library to colorize code examples. The default theme is called `Github` with a few small tweaks. You can link our own theme if you like. Again, store your stylesheet in the `static/` folder and set the relative path in the config file:
+
+```toml
+[params]
+ # Syntax highlighting theme
+ highlight_css = "path/to/theme.css"
+```
+
+### Adding a GitHub and Twitter account
+
+If you have a GitHub and/or Twitter account, you can add links to your
+accounts to the drawer by setting the variables `github` and
+`twitter` respectively:
+
+``` toml
+[social]
+ twitter = ""
+ github = "digitalcraftsman"
+```
+
+### Adding menu entries
+
+Once you created your first content files you can link them manually in the sidebar on the left. A menu entry has the following schema:
+
+```toml
+[[menu.main]]
+ name = "Material"
+ url = "/"
+ weight = 0
+ pre = ""
+```
+
+`name` is the title displayed in the menu and `url` the relative URL to the content. The `weight` attribute allows you to modify the order of the menu entries. A menu entry appears further down the more weight you add. The `pre` attribute is optional and allows you to *pre*pend elements to a menu link, e.g. an icon.
+
+Instead of just linking a single file you can enhance the sidebar by creating a nested menu. This way you can list all pages of a section instead of linking them one by one (without nesting).
+
+You need extend the frontmatter of each file content file in a section slightly. The snippet below registers this content file as 'child' of a menu entry that already exists.
+
+```yaml
+menu:
+ main:
+ parent: Material
+ identifier:
+ weight: 0
+```
+
+`main` specifies to which menu the content file should be added. `main` is the only menu in this theme by default. `parent` let's you register this content file to an existing menu entry, in this case the `Material` link. Note that the parent in the frontmatter needs to match the name in `config.toml`.
+
+`identifier` is the link that is shown in the menu. Ideally you choose the same name for the `identifier` and the `title` of the page. Again, `weight` allows you to change the order of the nested links in a section.
+
+### Markdown extensions
+
+Hugo uses [Blackfriday](https://github.com/russross/blackfriday) to process your content. For a detailed description of all options take a look at the [Blackfriday configuration](http://gohugo.io/overview/configuration/#configure-blackfriday-rendering) section in the Hugo documentation.
+
+```toml
+[blackfriday]
+ smartypants = true
+ fractions = true
+ smartDashes = true
+ plainIDAnchors = true
+```
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/content/index.md b/docs/_settings/themes/hugo-material-docs/exampleSite/content/index.md
new file mode 100644
index 0000000..a48262e
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/content/index.md
@@ -0,0 +1,55 @@
+---
+date: 2016-03-08T21:07:13+01:00
+title: Material for Hugo
+type: index
+weight: 0
+---
+
+## Beautiful documentation
+
+Material is a theme for [Hugo](https://gohugo.io), a fast and flexible static site generator. It is built using Google's [material design](https://www.google.com/design/spec/material-design/introduction.html)
+guidelines, fully responsive, optimized for touch and pointer devices as well
+as all sorts of screen sizes.
+
+![Material Screenshot](/images/screen.png)
+
+Material is very lightweight – it is built from scratch using Javascript and
+CSS that weighs less than 30kb (minified, gzipped and excluding Google Fonts
+and Analytics). Yet, it is highly customizable and degrades gracefully in older
+browsers.
+
+## Quick start
+
+Install with `git`:
+
+```sh
+git clone git@github.com:digitalcraftsman/hugo-material-docs.git themes/hugo-material-docs
+```
+
+## Features
+
+- Beautiful, readable and very user-friendly design based on Google's material
+ design guidelines, packed in a full responsive template with a well-defined
+ and [easily customizable color palette]({{< relref "getting-started/index.md#changing-the-color-palette" >}}), great typography, as well as a
+ beautiful search interface and footer.
+
+- Well-tested and optimized Javascript and CSS including a cross-browser
+ fixed/sticky header, a drawer that even works without Javascript using
+ the [checkbox hack](http://tutorialzine.com/2015/08/quick-tip-css-only-dropdowns-with-the-checkbox-hack/) with fallbacks, responsive tables that scroll when
+ the screen is too small and well-defined print styles.
+
+- Extra configuration options like a [project logo]({{< relref "getting-started/index.md#adding-a-logo" >}}), links to the authors
+ [GitHub and Twitter accounts]({{< relref "getting-started/index.md#adding-a-github-and-twitter-account" >}}) and display of the amount of stars the
+ project has on GitHub.
+
+- Web application capability on iOS – when the page is saved to the homescreen,
+ it behaves and looks like a native application.
+
+See the [getting started guide]({{< relref "getting-started/index.md" >}}) for instructions how to get
+it up and running.
+
+## Acknowledgements
+
+Last but not least a big thank you to [Martin Donath](https://github.com/squidfunk). He created the original [Material theme](https://github.com/squidfunk/mkdocs-material) for Hugo's companion [MkDocs](http://www.mkdocs.org/). This port wouldn't be possible without him.
+
+Furthermore, thanks to [Steve Francia](https://gihub.com/spf13) for creating Hugo and the [awesome community](https://github.com/spf13/hugo/graphs/contributors) around the project.
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/content/license/index.md b/docs/_settings/themes/hugo-material-docs/exampleSite/content/license/index.md
new file mode 100644
index 0000000..2758c65
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/content/license/index.md
@@ -0,0 +1,27 @@
+---
+date: 2016-03-09T20:10:46+01:00
+title: License
+weight: 40
+---
+
+Copyright (c) 2016 Digitalcraftsman
+Copyright (c) 2016 Martin Donath
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to
+deal in the Software without restriction, including without limitation the
+rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
+sell copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
+IN THE SOFTWARE.
+
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/content/roadmap/index.md b/docs/_settings/themes/hugo-material-docs/exampleSite/content/roadmap/index.md
new file mode 100644
index 0000000..ea6f252
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/exampleSite/content/roadmap/index.md
@@ -0,0 +1,27 @@
+---
+date: 2016-03-09T20:08:11+01:00
+title: Roadmap
+weight: 30
+---
+
+Quo vadis? The port of the original [Material theme](https://github.com/squidfunk/mkdocs-material) has replicated nearly all of its features. A few are still missing but I've good news: the Hugo community is actively working on this issues. Maybe with the next release of Hugo we can abandon this list. Stay tuned.
+
+## Localization
+
+Currently, it is possible to collect all strings in a single place for easy customization. However, this only enables you to define all strings in a single language. This approach is quite limiting in terms of localization support. Therefore, I decided to wait for a native integration. This way we can avoid a second setup of all strings in your website.
+
+Keep an eye on [#1734](https://github.com/spf13/hugo/issues/1734).
+
+## Search
+
+Beside third-party services, some hacky workarounds and Grunt-/Gulp-based scripts that only require unnecessary dependencies, future versions of Hugo will support the generation of a content index as a core feature.
+
+This approach plays well with this theme since MkDocs does the same.
+
+Keep an eye on [#1853](https://github.com/spf13/hugo/pull/1853).
+
+## Contributing
+
+Did you found an bug or you would like to suggest a new feature? I'm open for feedback. Please open a new [issue](https://github.com/digitalcraftsman/hugo-material-docs/issues) and let me know.
+
+You're also welcome to contribute with [pull requests](https://github.com/digitalcraftsman/hugo-material-docs/pulls).
diff --git a/docs/_settings/themes/hugo-material-docs/exampleSite/static/.gitkeep b/docs/_settings/themes/hugo-material-docs/exampleSite/static/.gitkeep
new file mode 100644
index 0000000..e69de29
diff --git a/docs/_settings/themes/hugo-material-docs/images/screenshot.png b/docs/_settings/themes/hugo-material-docs/images/screenshot.png
new file mode 100644
index 0000000..97ac062
Binary files /dev/null and b/docs/_settings/themes/hugo-material-docs/images/screenshot.png differ
diff --git a/docs/_settings/themes/hugo-material-docs/images/tn.png b/docs/_settings/themes/hugo-material-docs/images/tn.png
new file mode 100644
index 0000000..d3d374b
Binary files /dev/null and b/docs/_settings/themes/hugo-material-docs/images/tn.png differ
diff --git a/docs/_settings/themes/hugo-material-docs/layouts/404.html b/docs/_settings/themes/hugo-material-docs/layouts/404.html
new file mode 100644
index 0000000..e69de29
diff --git a/docs/_settings/themes/hugo-material-docs/layouts/_default/__list.html b/docs/_settings/themes/hugo-material-docs/layouts/_default/__list.html
new file mode 100644
index 0000000..54c2b78
--- /dev/null
+++ b/docs/_settings/themes/hugo-material-docs/layouts/_default/__list.html
@@ -0,0 +1,57 @@
+{{ partial "head" . }}
+
+