How to organize the revision of a large site after launch?

Question

Yii

Tell me how to work on the site, add functionality when it is in working order?
The developer is one person, not a team.
How does this happen? Is this happening on the live server? Create a copy of all files and database and work with them? And how then to remember what files changed? How to track changes in database structure? How to transfer changes from a working file to a production one? Probably, svn, git are used for this ... I read what was happening, but I still didn’t understand where and what to commit ... What kind of commit, what push, what pool, what sheepskin coat, what hare?! ..
Share your experience, please.

Answer 1

Share your experience please

So after all, they have already shared it - just google books or tutorials on Git, use github for practice - the main commands will take 20 minutes of study maximum. And if you use it inside an IDE with git support , then you won’t need to think about these commands at all (well, almost :)).

Is this happening on the live server?

No, there are such things as test servers. alpha, beta, stage - they are called differently. Vagrant can help in raising such things .

How to track changes in database structure?

With the help of migrations (here you need knowledge from a programmer or a desire to learn).

How to transfer changes from a working file to a production one?

free: rsync, git pull
paid and more professional: beanstalkapp.com/ (and similar)

Answer 2

I recommend reading
habrahabr.ru/post/158769/

Answer 3

1. Create a server for development, you can local - a complete copy of the combat one.
2. Set up a code version control system (gi, svn, mercurial - to choose from)
3. The database has its own version control systems, but we have few such changes and we add the SQL code of the changes in the comment to the ticket when committing.
4. Commit is storing changes in the code, push is uploading all your changes to the main repository, pool is uploading from there.
5. The system for developing new functionality is as follows: pull (on local) - commit - push, pull (on combat).