Is it bad to have a test and production environment on one machine?

Question

Would it be bad if everything was set up so that it MySite.comis a production, but test.MySite.coma test? Both work on the same machine. The site does not receive much traffic.

UPDATE

I am talking about an ASP.NET web application running on a Windows server.

Answer 1

Yes, this is a bad idea.

Suppose your test code contains an error that consumes all the memory space / processor / disk? Then your production site does not work.

Have separate machines for production and testing, and use DNS to specify URLs for each.

---

Edit (more points):

, IP-, IP- , .

, , ( , ).

- .

Answer 2

, ( php/perl/python/apache/kernel/whatever) .

Answer 3

. , .

Answer 4

- - ? , , , . ( ) .

Answer 5

, . , , , @Oded. , - , , .. test.mysite.com .

, , , , - - . , , , . , , !

: , -. .

Answer 6

, . " " , " " ... .

. " " .

, . ( ). , , ( ) . , , , , , , , , .. .. , .

, , HAL.

!

Answer 7

", , ". -

. , . , , . , , , .

con - shared . ( , , , chroot ..), , - . DOS , . . - , , . , .

: .