What is a staging server

Today's post deals with the question of why so-called staging or QA systems make sense. If you start “from scratch”, you may still import your changes directly onto the live server. Sometimes, however, it is also the case that the specialist departments do not want to spend any money on it, but complain in the same breath about why there is an error on "the website". A dilemma for the developer or project manager - how do you explain that it would actually have been sensible to have something like a staging system?

Good for those who can call a staging system their own (or operate according to standards such as ITIL). It doesn't have to be that expensive in terms of having its own physical machine. A separate vhost is sufficient for this (if possible on a separate web server instance), which runs on the live machine if necessary (which I absolutely do not recommend). It is better to have your own machine, depending on the size of the database, with a live copy of the database, on which you can integrate and test as you wish. Above all: on which the customer / the specialist department can test in peace without having to work on the developer's vhost (which can sometimes be annoying :-)).

I used the lunch break today to discuss the topic briefly with our colleague Jo Brunner. There is a lot more that could be said, but 11 minutes should be good. Jo looks after our Telefónica and O2 Germany accounts, and staging systems are also used there.