Comments on: Using a badge to distinguish development and production environments http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/ Sun, 15 Jan 2012 21:29:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jean-Michel http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142716 Jean-Michel Fri, 18 Dec 2009 10:10:43 +0000 http://blog.labnotes.org/?p=1361#comment-142716 The line I had to add to make it work in In application layou is: RAILS_ENV, :id => "rails-env" unless RAILS_ENV[/production/] %> The line I had to add to make it work in In application layou is:

RAILS_ENV, :id => “rails-env” unless RAILS_ENV[/production/] %>

]]> By: Ennuyer.net » Blog Archive » Rails Reading - Oct 20, 2009 http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142297 Ennuyer.net » Blog Archive » Rails Reading - Oct 20, 2009 Tue, 20 Oct 2009 18:27:16 +0000 http://blog.labnotes.org/?p=1361#comment-142297 [...] Labnotes » Using a badge to distinguish development and production environments [...] [...] Labnotes » Using a badge to distinguish development and production environments [...]

]]> By: Alex Chaffee http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142276 Alex Chaffee Sat, 17 Oct 2009 19:37:09 +0000 http://blog.labnotes.org/?p=1361#comment-142276 Very nice. I've adapted it into an Erector widget. http://github.com/pivotal/erector/blob/master/lib/erector/widgets/environment_badge.rb Very nice. I’ve adapted it into an Erector widget.

http://github.com/pivotal/erector/blob/master/lib/erector/widgets/environment_badge.rb

]]> By: Stephen http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142250 Stephen Fri, 09 Oct 2009 03:45:55 +0000 http://blog.labnotes.org/?p=1361#comment-142250 Nice. On an app a few years ago, my friend had the idea to change the whole background color--the content itself was in a white box so still legible. It got to where people referred to the multiple dev/qa instances (it was an enterprise app) by color--app-pink, app-orange, app-black, etc. Nice.

On an app a few years ago, my friend had the idea to change the whole background color–the content itself was in a white box so still legible.

It got to where people referred to the multiple dev/qa instances (it was an enterprise app) by color–app-pink, app-orange, app-black, etc.

]]> By: Assaf http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142248 Assaf Fri, 09 Oct 2009 02:52:18 +0000 http://blog.labnotes.org/?p=1361#comment-142248 Django's debug toolbar gave birth to Rail's Rack::Bug: <a href="http://github.com/brynary/rack-bug">http://github.com/brynary/rack-bug</a> I did not have the best experience with Rack::Bug so far. Django’s debug toolbar gave birth to Rail’s Rack::Bug:

http://github.com/brynary/rack-bug

I did not have the best experience with Rack::Bug so far.

]]> By: Chris Adams http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142247 Chris Adams Fri, 09 Oct 2009 02:39:31 +0000 http://blog.labnotes.org/?p=1361#comment-142247 On Django projects I use a small badge which lists the current Git / SVN revision on non-production sites (i.e. if settings.DEBUG) - this is also a great way to make sure that any internal screenshots are traceable back to a specific point in time. It's styled-inline to avoid external dependencies - something like "position:fixed; bottom:0px; text-aligned:center; width:100px; margin:auto" works pretty well for one line of text. For git try something like the output from "git describe --tags" - there are a bunch of permutations to match your preferences but the default format (--) is pretty useful. On a more advanced note, ala Aaron H's suggestion, steal ideas from the awesome django-debug-toolbar: http://robhudson.github.com/django-debug-toolbar/ - the new UI is very low impact (small badge in the upper right corner, offset down enough to avoid most nav) but expands into a really useful sidebar detailing SQL queries (with backtraces & explain support), template introspection, log messages, etc. I don't use it in production (I prefer capturing data from real users and, if possible, doing so in a way which can't cause their requests to fail) so it's also a reliable cue that you're not on the production site. On Django projects I use a small badge which lists the current Git / SVN revision on non-production sites (i.e. if settings.DEBUG) – this is also a great way to make sure that any internal screenshots are traceable back to a specific point in time. It’s styled-inline to avoid external dependencies – something like “position:fixed; bottom:0px; text-aligned:center; width:100px; margin:auto” works pretty well for one line of text. For git try something like the output from “git describe –tags” – there are a bunch of permutations to match your preferences but the default format (–) is pretty useful.

On a more advanced note, ala Aaron H’s suggestion, steal ideas from the awesome django-debug-toolbar: http://robhudson.github.com/django-debug-toolbar/ – the new UI is very low impact (small badge in the upper right corner, offset down enough to avoid most nav) but expands into a really useful sidebar detailing SQL queries (with backtraces & explain support), template introspection, log messages, etc. I don’t use it in production (I prefer capturing data from real users and, if possible, doing so in a way which can’t cause their requests to fail) so it’s also a reliable cue that you’re not on the production site.

]]> By: Aaron H. http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142246 Aaron H. Fri, 09 Oct 2009 01:59:52 +0000 http://blog.labnotes.org/?p=1361#comment-142246 I've done a similar thing, but I include a div (hidden) that includes any sort of performance metrics or request/session/environment elements I might want to see while debugging. Then, a simple jQuery call to toggle that div when clicking on the tab gives me extra info as needed. In fact, you can put this in production and only render it for admins, etc. Still, always a good idea. I’ve done a similar thing, but I include a div (hidden) that includes any sort of performance metrics or request/session/environment elements I might want to see while debugging. Then, a simple jQuery call to toggle that div when clicking on the tab gives me extra info as needed. In fact, you can put this in production and only render it for admins, etc.

Still, always a good idea.

]]> By: Patrick Mueller http://labnotes.org/2009/10/08/using-a-badge-to-distinguish-development-and-production-environments/comment-page-1/#comment-142244 Patrick Mueller Thu, 08 Oct 2009 23:45:49 +0000 http://blog.labnotes.org/?p=1361#comment-142244 Good idea. Setting opacity: 0.8 might be useful in case the badge occludes things. Or might be annoying. Or maybe set the z-index: -1? Good idea. Setting opacity: 0.8 might be useful in case the badge occludes things. Or might be annoying. Or maybe set the z-index: -1?

]]>