Vagrant-LAMP-Stack

by MiniCodeMonkey

MiniCodeMonkey /Vagrant-LAMP-Stack

A dead-simple LAMP stack without any bells and whistles for your basic Linux/Apache/MySQL/PHP instal...

442 Stars 175 Forks Last release: Not found 61 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Vagrant LAMP stack

A dead-simple LAMP stack without any bells and whistles for your basic Linux/Apache/MySQL/PHP install, using Chef Solo for provisioning.

The idea is for developers to fork this and add additional software and configuration that suits the needs of their project.

Requirements

Note: Vagrant 1.0.x compatible stack is also available.

Installation

Clone this repository

$ git clone [email protected]:MiniCodeMonkey/Vagrant-LAMP-Stack.git

Place your website in the

public
folder

Usage

Start the VM

$ cd Vagrant-LAMP-Stack
$ vagrant up

You can now access your project at http://projectname.local

Screenshot of up-and-running server

Database dump import

Chef will automatically try to import the database dump specified by the filename set in the

:db_dump
option of your Vagrantfile.

If you are using the default configuration, just create a

dump.sql
file in the root directory with your table structure and/or content and it will be imported automatically when you run
vagrant up
.

Installed software

  • Apache 2
  • MySQL
  • PHP 5.4 (with mysql, curl, mcrypt, memcached, gd)
  • memcached
  • postfix
  • vim, git, screen, curl, composer

Default credentials

MySQL

  • Username: root
  • Password: root
  • Host: localhost
  • Port: 3306

Note: Remote MySQL access is enabled by default, so you can access the MySQL database using your favorite MySQL client with the above credentials (and using e.g. projectname.local as hostname).

Memcached

  • Port: 11211

Bitdeli Badge

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.