webinno/vagrant-lamp
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
Provides a full LAMP environment for local developments on top of Vagrant
This repository has been archived on 2022-11-02. You can view files and clone it, but cannot push or open issues or pull requests.
13 commits 1 branch 1 tag 356 KiB
Find a file
Axel DE VIGNON 01b4f9ae50 Changing MySQL port forwarding to 3307 to avoid conflicts with existing MySQL instance on the host.
2017-09-27 12:40:17 +02:00
cookbooks/lamp Initial commit with full version working 2017-09-27 10:41:36 +02:00
www Initial commit with full version working 2017-09-27 10:41:36 +02:00
.gitignore Initial commit with full version working 2017-09-27 10:41:36 +02:00
create-vhost.sh Initial commit with full version working 2017-09-27 10:41:36 +02:00
LICENSE Initial commit 2017-09-27 10:34:15 +02:00
README.md [WIP] Readme in english 2017-09-27 12:39:09 +02:00
README_FR.md Initial commit with full version working 2017-09-27 10:41:36 +02:00
Vagrantfile Changing MySQL port forwarding to 3307 to avoid conflicts with existing MySQL instance on the host. 2017-09-27 12:40:17 +02:00

README.md

VAGRANT LAMP ENVIRONMENT

Description

This repository provides a starter kit that you to download in order to get a fully fonctional Ubuntu Server 16.04 LTS (headless) LAMP local development environment on top of Vagrant.

In order to do so, the starter kit uses a virtualization application (VirtualBox), a virtualization wrapper (Vagrant) and a recipes manager (Chef Solo). See "Installation" below.

The Vagrant Virtual Machine (or VM) will run on Ubuntu Server. The box image used was created by me. It is hosted on VagrantUp as axeloz/ubuntu-server-16.04 (https://app.vagrantup.com/axeloz/boxes/ubuntu-server-16.04). It is a clean install of Ubuntu with just a little bit of configuration in it. You may change the box used by Vagrant and use your own (at your own risks) by editing the config.vm.box setting into the Vagrantfile at the root of this repository.

Using one command only, a LAMP environment is installed on your computer among all the required tools for your developments. The Vagrant Virtual Machine (or VM) can be stopped when you don't need it and started when you need it.

⚠ Attention ⚠

You must understand that you can do whatever you want with the Vagrant Virtual Machine (or VM) like adding files, removing anything, installing new applications using APT or compilation. But be aware that the VM is not supposed to be persistent. The persistent data are and should remain on your host computer. The VM is throwable, you may mess with it, crash it, remove it and recreate it brand as new. It is that simple as vagrant destroy && vagrant up.

Content of the starter kit

Installation

  • Download and install VirtualBox (http://www.virtualbox.org/)
  • Download and install Vagrant (https://www.vagrantup.com/)
  • Clone the latest version of this repository (https://github.com/axeloz/vagrant-lamp) into your Home directory, whereever you want it to be. For example for Mac: /Users/my-user/Sites/vagrant-lamp
  • Open your terminal app, cd to the vagrant directory
  • Run a vagrant up command. For the first run, Vagrant will download the Linux Ubuntu 16.04 image from VagrantUp, create a new VirtualBox VM, boot the VM and run the Chef recipes. This will install all the dependencies, it may take some time.
  • Optionally, you can install Vagrant Manager (http://vagrantmanager.com/) which is a GUI to manage your Vagrant VMs.

⚠ Attention ⚠

For Mac and Unix systems When starting the VM, Vagrant will create a mount point between the VM and the host computer. On the VM, the mount point is made on /vagrant. Mounting is done using NFS for security and performance purposes. Vagrant will require your host computer password in order mount the folder. I do not ask for this password and I do not have access to this password. This password is asked by your computer in order to run a command as sudoer.

If you want to avoid typing your password each time you start your VM, you can edit the sudoers file and allow permanently Vagrant to mount NFS folders without password. In your terminal application on your host computer, edit the /etc/sudoers file with sudo. Then paste the following lines at the end of the file:

Cmnd_Alias VAGRANT_EXPORTS_ADD = /usr/bin/tee -a /etc/exports
Cmnd_Alias VAGRANT_NFSD = /sbin/nfsd restart
Cmnd_Alias VAGRANT_EXPORTS_REMOVE = /usr/bin/sed -E -e /*/ d -ibak /etc/exports
%admin ALL=(root) NOPASSWD: VAGRANT_EXPORTS_ADD, VAGRANT_NFSD, VAGRANT_EXPORTS_REMOVE

You might have to logout and login back on your computer to apply these changes. Then next time you boot your VM, it should mount the NFS directly, no password asked.

Upgrade

In order to upgrade, just:

  • git pull at the root of the vagrant-lamp folder
  • vagrant reload --provision

Accessing the tools

  • To SSH into the VM, run the vagrant ssh command from the root of the vagrant-lamp folder. The login is vagrant and the password is vagrant
  • To sudo in the VM, just run sudo <command>. The vagrant user belongs to the sudoers and you may sudo with no password asked
  • The IP address 192.168.99.100 is created by VM
  • The VM is also available on hostname localhost
  • In order to acccess your local websites: http://localhost:8080
  • In order to access Mailcatcher: http://localhost:1080
  • In order to access to MariaDB: mysql://vagrant:vagrant@localhost:3307
  • In order to access the Mailcatcher's SMTP from the host: smtp://localhost:1025
  • In order to access BrowserSync from the host: http://localhost:3000
  • In order to use Drush, run the drush command from the VM
  • In order to use WP_CLI, run the wp command from the VM
  • In order to use DEPLOYER, run the dep command from the VM
  • In order to use GULP, run the gulp command from the VM

The features in detail

SSH

You may access the VM using SSH using the vagrant ssh command. There is an existing Unix user:

  • login: vagrant
  • password: vagrant

The SSH identity forwarding is enabled from the host to the VM (config.ssh.forward_agent = true). This means that your host's computer SSH identity is forwarded to the VM. That may be useful in many case. For example, you clone a Github repository to your host computer using the host's SSH public key attached to your Github account. With the identify forwarding enabled, you can SSH to the VM, cd to the downloaded repository and issue a git pull. It will use your host computer's keypair. There is no need to add a new public key on your Github account.

Apache

Access

Your local environment is available from your host computer at the address: http://localhost:8080. This will launch a default application that will:

  • list all your projects
  • show the PHP configuration
  • show the server informations

Dedicated Apache virtual host

In some cases, you might need to create a dedicated virtual host to access your project. For example: http://myproject.local:8080.

For Mac and Unix systems: in order to do so, a script create-vhost.sh is provided to the root of the repository. Make sure it is executable (chmod +x create-vhost.sh) and run it (./create-vhost.sh). Just follow the instructions, the script will then create an entry into the /etc/hosts file and will add the virtual host to Apache into the vagrant-lamp/apache/conf folder. Finally it will reload Apache.

In any case: you may also do it manually by creating the Apache virtual host configuration file into the vagrant-lamp/apache/conf. Attention: the file must be named with a .conf suffix. You must also add manually an entry into the hosts file. Finally you must reload Apache on the VM machine using service apache2 reload.

Mailcatcher test form

You may also access the http://localhost:8080/mail.php page. This is a test form allowing you to test the Mailcatcher application.

Log files

The Apache log files are located into the vagrant-lamp/apache/logs folder.

MariaDB (MySQL)

Access

MariaDB is running on port 3306 on the VM. There is a port redirection from the host to the VM: 3307 -> 3306.

The root user for MariaDB is:

  • login: vagrant
  • password: vagrant

Data location

As usual, the MariaDB data are located on the host computer into the vagrant-lamp/mysql/data folder.

MariaDB logs

The MariaDB log files are located into the vagrant-lamp/mysql/logs

Gulp

Questions / Know issues

Mailcatcher

Mailcatcher is supposed to be started when the VM boots. For some reason, this is not always the case. In order to start Mailcatcher manually, do SSH to the VM and issue a killall mailcatcher && mailcatcher --no-quit --ip 0.0.0.0

Files watching

Because of VirtualBox, the watch command (for Laravel for example) may not work as expected. The watch command is running on the VM but the source files are located on the host computer and mounted using NFS. The watch command cannot therefore use default Unix feature. You should use the watch-poll command instead (for Laraval). You may have similar issues with gulp watch or browsersync.