crystal-lang / crystal-env Goto Github PK

Ref: crystal-lang/crystal#9687

Now it's pointing at bintray.

Why is any environment other than development, testing and production considered invalid? These may be quite common, but there are plenty of software systems which use more/other than these specific ones. I don't see why a generalized library should limit usage to three more or less arbitrary environment names.

I mean, it'd certainly be nice if everything could standardize on these three, would make many things easier. But this is just practically impossible. If this shard is supposed to become a commonly used library it should let library and app developers decide which environments their software needs.
In a way this is already possible by redefining Env.OPTIONS, but you'd have to do that before requiring env. It should certainly be easier.