You can choose to run Apache instead, if preferred...
Clone this repo.
CD to the project directory and remove the .git directory.
rm -rf .git
Add to your own git repo (doing something kind of like)...
git init
git remote add origin git@github.com:yourname/foo.git
git fetch
git branch master origin/master
git checkout master
git add -A
git commit -m 'first commit'
git push
Edit the puphpet/config.yaml file in your favorite text editor or IDE.
Search for project.dev and replace with your project's development domain, for example, awesomeproject.dev. (Examples throughout refer to awesomeproject.dev, obviously, this probably isn't your project's desired URL).
If you would rather have Apache than NGINX, find this block of text in the puphpet/config.yaml file...
nginx:
install: '1'
And change it to this :
nginx:
install: '0'
Then find...
apache:
install: '0'
and change it to this :
apache:
install: '1'
Save the file.
Install the vagrant hostmanager plugin,
vagrant plugin install vagrant-hostmanager
OR edit your hosts file and add :
192.168.56.101 awesomeproject.dev www.awesomeproject.dev docs.awesomeproject.dev
Save the file.
CD back to the project root.
Run :
$ vagrant up
Have a cup of coffee while Vagrant downloads the necessary files.
Upon success, you will have a guest Linux environment running Ubuntu 14, NGINX 1.8.0 (or Apache 2.4 if you chose to enable Apache instead), PHP 5.6.8, and MySQL 5.6.22. This will act as your local dev server for the project. This Vagrant box is not intended for production use!
When the machine has finished booting, you should be able to visit http://awesomeproject.dev in your browser.
On initial visit, the famous 5 minute WordPress install screen should be presented to you.
Fill out the form to complete the installation process.
You should now have a fully functional WordPress installation running in Vagrant.
Visiting http://awesomeproject.dev/wp/wp-admin/ should bring you to the WordPress login / dashboard.
Visting http://awesomeproject.dev:1080/ should bring you to the Mailcatcher server. From Mailcatcher you can view and debug emails being sent by WordPress on your guest machine.
Visiting http://docs.awesomeproject.dev/ should bring you to a barebones MDwiki installation.
It is strongly suggested that command line actions, such as composer install, composer update, wp-cli commands, etc., be performed in the Guest VM. $ vagrant ssh can be used to log into the Guest machine.
Warning, performing command line actions from the Host could have unexpected consequences, if it works at all.
The composer.json file sits in the root of the project.
Edit / modify this file to suit your project's needs.
Default Plugins Installed By Composer :
+-------------------------------------+
| name |
+-------------------------------------+
| advanced-custom-fields |
| debug-bar |
| debug-bar-actions-and-filters-addon |
| debug-bar-constants |
| debug-bar-cron |
| debug-bar-list-dependencies |
| debug-bar-post-types |
| debug-bar-remote-requests |
| debug-bar-roles-and-capabilities |
| debug-bar-shortcodes |
| debug-bar-transients |
| jetpack |
| log-deprecated-notices |
| pods |
| posts-to-posts |
| query-monitor |
| rewrite-rules-inspector |
| ricg-responsive-images |
| root-relative-urls |
| safe-redirect-manager |
| simple-page-ordering |
| simply-show-ids |
| theme-check |
| user-switching |
| vip-scanner |
| wordpress-importer |
| wordpress-seo |
| wp-pagenavi |
| wp-google-analytics |
| wp-help |
| wp-sync-db |
| wp-sync-db-cli |
| wp-sync-db-media-files |
| jetpack-development-mode |
| register-theme-directory |
+-------------------------------------+
This installation does not include a copy of phpMyAdmin, since we do not recommend using this tool for making changes to the MySQL database.
The preferred way to connect to your database is using a dedicated application like Sequel Pro (OS X), HeidiSQL (Windows), or MySQL Workbench (available for NIX, Mac, and Win platforms).
Connect using SSH tunnel, username vagrant and SSH key generated at puphpet/files/dot/ssh/id_rsa. This key is generated after your initial $ vagrant up!
Create a connection using "Standard TCP/IP over SSH," the SSH Hostname is "awesomeproject.dev:22", the SSH Username is "vagrant", do not enter an SSH password, the SSH Key File to use is located at (/path/to/your/project/)puphpet/files/dot/ssh/id_rsa. The MySQL Hostname is "localhost", the MySQL Server Port is "3306", the MySQL Username is "root", the password is "123".
The SSH Key File is generated after your initial $ vagrant up.
This Vagrant box was built with Puphpet.com, with some additions/modifications to make it more WP friendly. To read more about Puphpet's features, visit their website.
The project root translates to /var/www/ in the Guest.
Points of interest in the Vagrant box outlined below :
├── .editorconfig
├── .gitattributes
├── .gitignore
├── README.md (this file)
├── bin (where Composer installs binaries for use in the Guest machine)
├── composer.json (the Composer installer that adds WP / Plugins / Themes into the web root)
├── docs (barebones MDwiki installation)
├── html (web root)
│ ├── index.php
│ ├── wp (Where Composer installs WordPress Core)
│ ├── wp-cli.yml (WP-CLI config providing path to core)
│ ├── wp-config.php (The WP Config file)
│ └── wp-content (The Content outside of Core)
│ ├── mu-plugins
│ │ ├── jetpack-development-mode.php (Enable Jetpack Dev mode, do not deploy to production)
│ │ └── register-theme-directory.php (prevents WSOD on initial install by registering core theme dir)
│ ├── plugins
│ ├── themes
│ └── uploads
├── puphpet (files generated by puphpet, required by Vagrant for spin up)
│ ├── config.yaml (The Puphpet config)
│ ├── files
│ │ ├── exec-once
│ │ │ ├── 01-delete-index-html.sh (custom script to delete the default index.html file from web root)
│ │ │ ├── 02-wordpress-config-copy.sh (custom script to copy wp-config-dist to wp-config in proper location)
│ │ │ ├── 03-composer-install.sh (custom script to kick off Composer installation)
│ │ │ ├── 04-phpcs-config-set.sh (custom script to add WordPress Coding Standards to phpcs in the Guest)
│ │ │ └── empty
│ │ └── startup-always-unprivileged
│ │ ├── 01-echo-wordpress-ascii-art.sh (Extra WordPress Goodness)
│ │ └── empty
│ └── vagrant
│ └── Vagrantfile-local (slightly modified from original for Win support)
├── vendor (where Composer installs vendor libraries)
│ └── wp-coding-standards (WordPress coding standards, accessible by phpcs in host, can be added to PhpStorm)
│ └── wpcs
├── wp-cli.yml (WP-CLI config providing path to core)
└── wp-config-dist.php (WP-Config Distribution file)