Today I got yelled at for developing an application on a production server. Quote, developing on a production server is not acceptable - ever!Here is the situation.I set up a development instance: http://example.com:3000The production instance is: http://example.comI complete all my development work on http://example.com:3000 and when the client is pleased with the changes, I move them over to http://example.com.The application I am working with is an old Ruby on Rails application, and I have to say that initially, I did try to set up an development environment locally, but I could never get it running. After trying for a while, I gave up and decided to develop on the production server.Again, am I an idiot? Probably so, but I've been doing web development for a couple of years now, and I have never encountered a situation like this. Who is right and why?
Developing on a production server
web development;ruby on rails;apache;production;hosting
I used to develop on the production server. It can work fine, but it is inadvisable for at least two reasons:Development code can cause infinite loops, memory leaks, or other problems that lock up the CPU, eat up all the memory, or otherwise affect the server in a way that will impact your production code.If you need to make changes to components of the server environment as part of your development work, like the version of Ruby or MySQL or whatever, you'll be in a bind.