Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace lucky env module #655

Merged
merged 2 commits into from
Jul 12, 2021

Conversation

hovsater
Copy link
Contributor

@hovsater hovsater commented Jul 6, 2021

This attempts to replace the Lucky::Env module with LuckyEnv. I was not entirely sure how we want to go about structuring the env.cr file. So any feedback is appreciated. 🙂

Closes #654.

Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some small comments on the env.cr config file, but overall this is awesome! I'll look at a new release for the LuckyEnv shard.

Comment on lines +14 to +23
# Example:
# ```
# LuckyEnv.add_env :staging
# LuckyEnv.staging? # => false
# ```
#
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, I really like this. The only thing I think that's missing is mentioning that the value comes from ENV["LUCKY_ENV"]..

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've amended the original commit. See 6acd902.

@@ -1,20 +1,29 @@
module Lucky::Env
extend self
# Lucky manages environments using `LuckyEnv`. By default, development,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a link to the lucky_env github repo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I adjusted the documentation in 6acd902. However, instead of linking to the GitHub repository, I link to the configuration section of the Lucky documentation. I thought that would be more helpful. What do you think? 🙂

@hovsater hovsater force-pushed the replace-lucky-env-module branch from c9b9931 to 5ffc579 Compare July 6, 2021 15:34
@jwoertink
Copy link
Member

I've released v0.1.3 of LuckyEnv. No shard.yml update should be needed. I think it'll just pick it up.

@hovsater
Copy link
Contributor Author

hovsater commented Jul 6, 2021

@jwoertink thank you! 🙂

Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@jwoertink jwoertink merged commit 20e66a8 into luckyframework:master Jul 12, 2021
@hovsater hovsater deleted the replace-lucky-env-module branch July 13, 2021 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update generated apps config/env to use new LuckyEnv setup
2 participants