No commit activity in last 3 years
No release in over 3 years
An ActiveAdmin plugin that provides tags on the admin panel to indicate which environment your rails project is running in
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Dependencies

Development

~> 1.6
~> 0
 Project Readme

ActiveAdminEnvironmentTag

An ActiveAdmin plugin that provides tags on the admin panel to indicate which environment your rails project is running in

Installation

Add this line to your application's Gemfile:

gem 'active_admin_environment_tag'

And then execute:

$ bundle

Include the active admin environment tag stylesheet in the active_admin.rb initializer:

config.register_stylesheet 'active_admin_environment_tag'

Configuration

ActiveAdminEnvironmentTag is configured using an initializer:

ActiveAdminEnvironmentTag.configure do |config|
  config.environment_colors = {
      staging: '#FCBF34'
  }
end

environment_colors

By default, ActiveAdminEnvironmentTag uses the following colors for each of basic environments:

development: '#91CA4B',
production: '#fc1f27',
default: '#c9d6e3'

You can override these colors (including the default) or specify other environments using the environment_colors option to provide a hash of environment names and colors. If ActiveAdminEnvironmentTag is run in a Rails environment that does not have a color associated with it, default is used.

config.environment_colors = {
      staging: '#FCBF34'
  }

tag_position

By default, the environment tag will appear in the top left area of the screen, however you can display it in the bottom left of the screen by specifying

config.tag_position = :bottom_left

Currently no other positions are supported as the left margin of the screen is the only area where the tag does not overlap content.

Contributing

  1. Fork it ( https://github.com/greena13/active_admin_environment_tag/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request