What if I want other environment names? What if I don't want staging, because I consider that staging == production?

These values are used only to auto-generate query methods like Crystal.env.development?.

In 99% of cases these should be enough, but if you don't need/want to use those, you can always do Crystal.env.name == "foo" to check for non-standard env.

This is not nice:

if Crystal.env.staging? || Crystal.env.name == "integration"
  # do some stuff
end

I agree, in terms of solutions we could add Crystal::Environment.setup(keys) macro replacing/extending defaults, or use method_missing (which was deemed a bad idea before).

I like the idea for a setup macro. Though I think the default envs are going to be enough in most cases

Also I think staging should be removed. Amber uses dev/test/prod and so does Elixir’s mix, Rails etc. Heroku even recommends against staging. So I think the main 3 should be there and people can add others if they want. Thoughts?

PoC implemented, see https://github.com/Sija/crystal-environment/blob/master/spec/crystal-environment_spec.cr#L51