Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Clearly marking your staging server

Freshness Warning
This article is over 17 years old. It's possible that the information you read below isn't current.

Web developers often have development, staging, and production (live) servers. If you’re like me you typically have several browser windows open at a time, some opened to the staging server, some to dev, and some to production. And you probably sometimes open the wrong browser window and start testing, finding it hard to figure out why the change you just made on the staging server doesn’t seem to be appearing.

What you need is a way to make it easy to see which server you are on. Create an include file at the top of each page on the site. On the staging and development servers, the include file consists of a big banner at the top of the page with a colored background and "Staging server" or "Development Server" in big letters. The banner also has links to the other two servers. On the production server, the include file is empty. Now just make that you set up your source-control software to ignore the include file (you are using source control software, aren’t you?) and you’re all set.

As an alternative, you can also set your include file up to conditionally display the banner depending upon what server you’re on, but I’ve found that can get messy when several developers are running the code in their own local development environments or when you have multiple, load-balanced production servers.

Trackback from Switch-Case
May 21, 2003 5:58 PM

Marking your staging server

Excerpt: "Cool idea":http://kalsey.com/2003/05/clearly_marking_your_staging_server/ PHP's auto_prepend would work well with this idea. via "Kalsey Consulting Group":http://kalsey.com/blog/


Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.

Name:

Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Recently Written

A framework for onboarding new employees (May 15)
There’s no single good way to onboard an employee that works for every role. Here's a framework for creating a process that you can adapt to each situation.
TV hosts as a guide for software managers (May 10)
Software managers can learn a lot from journalists or late night TV hosts and how they interview people.
The Improvement Flywheel (Apr 29)
An incredible flywheel for the improvement of a development team. Fix a few things, and everything starts getting better.
Managers and technical ability (Dec 26)
In technical fields, the closer you are to the actual work being done, the closer your skills need to resemble those of the people doing the work.
Dysfunctions of output-oriented software teams (Sep 17)
Whatever you call it, the symptom is that you're measuring your progress by how much you build and deliver instead of measuring success by the amount of customer value you create.
Evaluative and generative product development (Aug 30)
Customers never even talk to the companies that don't fit their needs at all. If the only product ideas you're considering are those that meet the needs of your current customers, then you're only going to find new customers that look exactly like your current customers.
Product Manager Career Ladder (Aug 19)
What are the steps along the product management career path?
Building the Customer-Informed Product (Aug 15)
Strong products aren't composed of a list of features dictated by customers. They are guided by strong visions, and the execution of that vision is the primary focus of product development.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.