Slashdot Mirror

← Back to Stories (view on slashdot.org)

A Proper Environment for Web Development?

Posted by Cliff on from the a-sane-and-careful-way-to-code dept.

umdenken wonders: "I'd like to know how others on Slashdot do their server-side web programming. We have dozens of Perl CGI scripts, and are currently doing development by editing these production scripts in place on the web server (!). Our sysadmins have finally installed an SVN client on the server (Solaris), and have offered to create a new virtual host that we can use as the development server. What are some of the practices you use for organizing this kind of set up?"

3 of 66 comments (clear)

  1. Er, uh by baldass_newbie · · Score: -1, Troll

    You mean like a test server?
    We are talking basic code control, right? I mean, this seems so fucking obvious I feel like I'm missing something.

    Hey slashdot, can you help me figure out what question Captain Obvious is asking?

    --
    The opposite of progress is congress
    1. Re:Er, uh by frank_adrian314159 · · Score: 0, Troll
      ...but if you're not already in this sort of environment and someone sort of dumps the problem in your lap, what are you supposed to do?

      Tell your boss he should have hired someone experienced, rather than some "wet behind the ears" kid? :-)

      --
      That is all.
  2. Blah blah blah by Anonymous Coward · · Score: -1, Troll

    Cue Slashdotters listing their pet development tools. The "proper" solution is one that works for you and you shouldn't have to ask.

    I use a popular text editor and RCS, developing on linux and testing locally before deploying to a shared staging server with dev and stable vhosts. The project managers are responsible for pushing our apps to the production servers from there. It's rocket science.