Geek Answers Handbook

How to version control, deploy and develop php and mySQL

I am working on a project where we are developing php on Zend using the mySQL database, and the project is going to get to the point where it will be necessary to use version control not only for real code, but also for the database,

We also get a good production server (and the actual production server will be a test server).

So, I was wondering if you guys think it’s a good idea to standardize the IDE that programmers use and get them to install apache / php / mySQL in their boxes to test the code, while having a development environment on each computer , test server and production server.

If so, what setting would you recommend for every part of this process, especially mysql version control (I never did) and how to do the deployment?

I know this is a very big question, and most of them answered different questions, but I would like to get a global answer about how faster, better (more rigid and strong) settings are for this and how much time we will have to stop programming so that it actually works! (and yes, hiring a specialist on the topic is pretty much no-no)

Thanks!

+5
source share
3 answers

No, I would not standardize the IDE for all developers. You should standardize the coding style, not the IDE.

PHP/Apache/MySQL - . , , - , , -, ​​ / , . .

MySQL, (CVS, SVN, Perforce, ). , Rails .

- . , , , . Capistrano, Phing ..

+8

, MySQL, DDL DML SQL , . "Agile Database" , .

IDE - , , . , , IDE .

? , . , .

+1

, , , , , IDE, , apache/php/mySQL , , , .

, , , .

0

More articles:


All Articles