Answer the question
In order to leave comments, you need to log in
How to organize the laying out of a site for tests + a working version?
Hello. I work alone, not in a team, so I make websites the old fashioned way.
On the local version, I debug the code, then upload it via ftp to the combat server.
But everything changed when it became necessary for me to first show the work of the site before the update (remotely) to another person.
Now I do this: I do debugging in the locale, I upload via FTP to the subdomain, if the person is satisfied, then I already synchronize the subdomain with the main domain. Here is the inconvenience. It is necessary to remember exactly which files have changed ...
It seems to me that this is somehow antediluvian. Maybe there are other ways.
Share how you do it.
Answer the question
In order to leave comments, you need to log in
I use RealSync for debugging in a live environment and hooks in the central git repository for deployment. This is sufficient for relatively simple single server projects.
habrahabr.ru/qa/28521/#answer_114347
With git, very convenient!
You can set up automatic generation of a subdomain for each branch, this will allow you to separately test literally every new feature!
Then we merge everything into masters and deploy to production :)
git+jenkins.
Of course, it all needs to be deployed somewhere, but it's worth it.
Well, or a more budget option that I use for personal needs - SVN + self-written system for deployment.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question