VagrantPress is a packaged development environment for developing WordPress themes and modules. I initially created this project to aid in developing child modules for a WordPress blog.
/etc/php5/apache2/php.ini is the proper directory inside vagrant.
Change both the upload_max_size and post_max_size.
- Ubuntu Trusty (14.04)
- Wordpress 4.0
- Mysql
- Php
- Phpmyadmin
- Subversion
- PEAR
- Xdebug
- PHPUnit
- phploc
- phpcpd
- phpdcd
- phpcs
- phpdepend
- phpmd
- PHP_CodeBrowser
- WordPress sniffs for phpcs
- Search and Replace DB
- Vagrant
- Virtualbox
- vagrant-hostsupdater plugin (optional)
This is a fairly simple project to get up and running. The procedure for starting up a working WordPress is as follows:
- Clone the project. (There’s only master branch.)
- Run the command
vagrant up - Open your browser and point 192.168.50.4 (or
HOSTNAMEif you have the vagrant-hostsupdater plugin installed)
- Wordpress DB: wordpress/wordpress
- Root: root/vagrant
Both the theme and plugin directories are automatically mounted in the guest operating system using
the THEME_NAME and PLUGIN_NAME variables (defined in the Vagrantfile) as their enclosing directory within the themes and plugins
directories, respectively, within the guest OS.
Access is also provided to the plugins and uploads directories on the guest OS (mounted on the host in the repository).
If you have the vagrant-hostsupdater plugin installed, an
entry will automatically be added to your /etc/hosts file to point to the guest machine's address. The
hostname that the machine uses is set by the HOSTNAME variable in the Vagrantfile.
All the files for Search and Replace DB have been copied into the VM and should be accessible via the web server at the following path: /srdb.
- If you're needing a password (for anything - including mysql, it should be
vagrant)
Feel free to file an issue, create a pull request, or contact me at my website.