Miemieda

Vagrant box for PHP projects

For PHP5.X see legacy/ubuntu-14.04-PHP5 branch. The feature/php7 branch is also deprecated, PHP7 is now in the master branch.

• Vagrant Cloud

Legacy Releases

• Vagrant Cloud PHP7.x
• Vagrant Cloud PHP5.x

For legacy versions, please refer to at15/lnmp repository.

Include

• Ubuntu 18.04 LTS
• Nginx 1.16.1 ppa:nginx/stable
• MySQL 5.7
• PHP 7.3 ppa:ondrej/php
• Composer /usr/local/bin/composer
• Redis 5.0.7 ppa:chris-lea/redis-server
• Phpmyadmin 4.6.6.5 (nginx config is /etc/nginx/conf.d/phpmyadmin.conf)
• Node.js 12.14.0 LTS (nvm)

Requirement

• Virtualbox 6.0+ (6.1 is tested, the guest addtion is working on windows, Mac user may need to update TODO: the issue for brew cask installed vbox)
• Vagrant latest
• Host OS: Fedora 25, Ubuntu 16.10, Windows 10 (not tested but should work)

Usage

Use the pre-built box (Recommended)

Use the following Vagrantfile, and run vagrant up --provider virtualbox

• edit your host machine's hosts file, add 192.168.10.80 mysql.lk, and use mysql.lk to visit phpmyadmin
• use localhost:8080 to visit nginx welcome page

If you have a bad network, you can run the provison multiple times, it has side effects, but won't break your PHP projects.

• vagrant up --provison works when your vm is stop or running
• vagrant reload --provision would restart the vm and run the provision when start

As for package management tools, you will have problem running npm inside the box when your using windows host due to symbolic link.

• npm can be solved using npm install --no-bin-links see npm/npm#5874
• composer may have similar problem

For windows users, I suggest running git and npm in your git bash or cmd instead of inside the vm. Since most PHP projects use node for building assets instead of application server, running instead vm is not a must.

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|

  # The pre built box is on https://atlas.hashicorp.com/dyweb/boxes/miemieda/
  config.vm.box = "dyweb/miemieda"

  # If the base box updated, you can't update your current vm without destroy it
  config.vm.box_check_update = true

  # Forward vagrant to private network
  config.vm.network "private_network", ip: "192.168.10.80"

  # Forward guest 80 to host 8080
  config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Use 777 for the default mount folder. which works for Ubuntu and Mac, windows always got 777
  config.vm.synced_folder ".", "/vagrant", \
    :disabled => false, \
    :mount_options  => ['dmode=777,fmode=777']

  config.vm.provider "virtualbox" do |vb|
     # Don't show the GUI unless you have some bug
     vb.gui = false
     # Customize the amount of memory on the VM:
     vb.memory = "1024"
     # Config the name
     vb.name = "lnmp7"
  end
end

Build the box

• git clone [email protected]:at15/lnmp.git
• cd lnmp
• Add config.ssh.insert_key = false in your Vagrantfile
• vagrant up it will run the provision using Ansible. see site.yml for detail
• ssh into the vm and run util/clean.sh to clean up apt stuff before you package the box
• vagrant package to build the new box
• upload it to Vagrant Cloud

Acknowledgement

• https://github.com/LukeXuan/atlas-centos7
• https://github.com/leonidas/ansible-nvm
• https://github.com/arbabnazar/ansible-roles/tree/master/LEMP

License

MIT