webinno/vagrant-lamp
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[WIP] Readme in english

Browse source
This commit is contained in:
Axel DE VIGNON 2017-09-27 12:57:03 +02:00
parent 4e82709a48
commit bc7546b4a2
1 changed files with 15 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
README.md
View file

@ -3,14 +3,26 @@
## Description ## 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. This repository is a starter kit providing 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. This 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. The Vagrant Virtual Machine (or VM) will run a Ubuntu Server instance. 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 use a different box or use your own by editing the `config.vm.box` setting into the `Vagrantfile` at the root of this repository. You should use an Ubuntu box. It might also work on Debian but this is untested. Changing the Vagrant box is at your own risk as I cannot guaranty the compatibility.
### Why should I use this starter kit?
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. 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.
More tools can be added very easily if you need to. Just edit the recipe and build your own VM according to your needs.
The VM is throwable. All the data remains on the host computer. Just backup the host computer, you are sure you will not loose anything (sources, databases, configuration files...).
The VM crashed because you messed with it? Just destroy it and restart it. You're good to go in no time.
You may adapt the services configuration (like PHP) according to your needs. Just edit the `vagrant-lamp/cookbooks/lamp/templates/default/php.ini.erb`, issue a `vagrant provision` and you're good to go.
For your team, it guaranties that all developers are using the exact same environment. Plus you get rid of the pain of installing a Linux environment from scratch. Let's say a new developer joins the team, he's ready to code in minutes.
Finally, the team members can run a `vagrant provision` in order to apply any recipe update if applicable. Let's say the lead developer adds a new tool in the recipes, this will be deployed for the entire team in no time.
### ⚠ Attention ⚠ ### ⚠ 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`. 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`.