Yet another environment variable manager. Read from a file like a
- Add the dependency to your
dependencies: lucky_env: github: luckyframework/lucky_env
Environment variable file
Create your "env" file. Name it whatever you want. Most common is
The file is created with key/value pairs separated by
# This would normally go in your `src/shards.cr` file require "lucky_env" # Loads the ".env" file. Raises if it is missing LuckyEnv.load(".env") # Use `load?` if the file is optional. # This will not raise if the file is missing LuckyEnv.load?(".env") ENV["LUCKY_ENV"] == "development" # => true # Returns whatever `ENV["LUCKY_ENV"]` is set to, or `"development"` if not set. LuckyEnv.environment # => "development" # Environment predicates LuckyEnv.development? # => true LuckyEnv.production? # => false LuckyEnv.test? # => false
shards install, and start making changes.
Be sure to run
./bin/ameba, and the crystal formatter
crystal tool format spec src.
Read through the issues for things you can work on. If you have an idea, feel free to open a new issue!
- Fork it (https://github.com/luckyframework/lucky_env/fork)
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create a new Pull Request
- Jeremy Woertink - creator and maintainer