Geek Answers Handbook

Localhost + production + production environment?

I have a website www.livesite.com that is currently running. I develop a new version of the site on my local machine with http: // localhost , and then transfer my changes using svn to www.testsite.com where I would check the site on the livesite.com server, but in a different domain (its environment, as in real time, but in a different domain).

Now I am ready to release a new version on liveite.com. Doing this for the first time is easy, I could just copy and paste everything from testsite.com to livesite.com (not sure if this is the best way to do this).

I want testsite.com to be a testing place where I would push updates, test them, and as soon as I am happy with the transition to lifeite.com, but I'm not sure how to do this after the launch of a new site. I don’t think that copying pasting the entire catalog is the right way to do it, and it will disrupt current users on livesite.com.

I also want to keep my svn history on testite.com. What is the correct way to do this using SVN? Thank you very much!

+5
source share
3 answers

Other answers regarding Hudson or Weploy are good. They cover more issues than what follows. This may be enough.

, , SVN sysadminning.

root , . , - :

/var/www/myproject-1-0-0
/var/www/myproject-1-1-0
/var/www/myproject-1-1-1
/var/www/html -> myproject-1-1-1

, (, myproject-1-1-2), . , - :

$ rm html && ln -s myproject-1-1-2 html

svn checkout/svn . ( - myproject-X-Y-Z). , , , .

, . :

, . (plain-old-SQL - ), , . , , , , . " " (/var/www/mainenance) , .

, Weploy, , ( ) .

+5

, :

Hudson.

Hudson / / svn. , .

, , .

PHP

, , , , .

+2

, , , . . , ajax, . , , .

, , - , , , . , "-" , , , . , . , -, , , 30 , .

For things like fixing security errors in the OS or system software, adding hardware, etc., downtime can be avoided if there is load balancing, and the fixes are applied one by one.

+1
source

More articles:


All Articles