Organization of the technical process for the development of the site (version control, testing, updating on the server)

Question

CVS

How to competently organize the development of the site by several developers and the passage through the chain Development -> Testing -> Stage -> Production. Namely:

1. Organization of the repository and workplaces
2. Automated "upload" of the new version to the server (test, working) - updating changed files, deleting more unnecessary ones, ..., automated updating of the database structure
3.?

Please help with advice or links.

Answer 1

Learn Continuos Integration technologies!
Ant/Maven, SVN, Hudson, xUnit,…
Essentially you need to automate builds and deployments. This is solved by the listed set of technologies.
I'm only afraid that if the projects are very simple, then this will only slow down the development process, because. in small projects, instead of code coverage with tests and automation, less time is devoted to manual testing. Yes, and there are things that cannot be tested in reasonable time without manual intervention - layout, for example.
Most of your tasks are covered by Ant. once you write a build script, you can use it in all subsequent projects. He knows how to upload files via SSH/FTP, run SQL on the DBMS, execute console commands (therefore, it can be used for phpUnit, or what do you write on?) - and these are the main tasks.
It is useful to keep the server under test on the Internet, because sometimes you need to show the customer the current state of affairs. This can be done by connecting the server to a static IP, or by purchasing a separate hosting for this. It's more expensive to keep your server.
My SVN rises quickly, I see no reason to keep it on the Internet at first.
And then it's a matter of technology - Scrum and all that.
Well, jobs are the most important thing! Each programmer has a secretary, large tables, darts, a layout designer a computer with a large monitor and Windows, programmers - desktops on ubunts. It is useful to keep your server. You need a locale, of course.

Answer 2

I will add to the previous post. It's not bad to have time-tracking and ticket systems like redmine. It is necessary to give the opportunity to quickly register errors, and preferably not only within the company, but also to customers. Triggers in SVN can be configured to link commits and bugfix requests, for example.