Андрей Степанов “Development server for lamp environment”
1. Development Server for
LAMP Environment
How to set up dedicated development server for team of PHP
developers
2. Using developer’s station
Pros
• Always available
Cons
• Big time efforts for new team member to set up environment
• Environment not consistent
• Too complex to use additional software under Windows or Mac
operation systems
• Not possible to share results
3. Using virtual machine
Pros
• More-less consistent environment
Cons
• Hard to maintain for junior and regular developers
• Hard to synchronize environment changes between team
• Use resources of developer’s station
• Not possible to share results
4. Using Vagrant
Pros
• Consistent environment
Cons
• Not of all software can be configured
• Additional complexity for developers to support vagrant configuration
• Use resources of developer’s machine
• Not possible to share results
5. Using development server
Pros
• Consistent environment for everyone
• New team member doesn’t required to set up environment
• Results can be shared to everyone using company’s DNS (or hosts file)
• Ability to work remotely without hard dependency of environment
• High available editors VIM, Emacs, Cloud9 IDE
Cons
• Single point of failure
6. FTP based development server
Pros
• Simple to set up
Cons
• No sandbox
• No isolations
7. Apache2 virtual hosts based
development server
Pros
• Separated by virtual host
Cons
• Hard to set up new virtual hosts
8. Linux users based development server
Pros
• Sandbox for every user
• No restrictions with virtual hosts
Cons
• Relatively hard to set up