reading https://boats.gitlab.io/blog/post/2018-01-18-configure/ … and thinking what would the "rails of cli apps" look like?
-
-
Seems like a hard problem to generalize since most configuration you’re solving on behalf of the user is usually really domain driven. I did try to start a basic one a while back as well.
-
I say this hoping you correct me, because I’m interested how this could be solved in a general way. Pluggable configuration standards?
-
Both bundler and cargo standardized around a few basic ways to get config in (local/global files, env vars) where every config has an equivalent (easy to drerive) env var, even for arrays and such. That story is easy to make conventional and valuable.
-
In a lot of ways the problem is similar to rails: there's a lot of pointless scaffolding leading into an endpoint with params, some common kinds of (unimportant) persistence, and then the app takes it from there.
-
Speaking of being a naive programmer, I was thinking at a much higher level. Appreciate the reply as always
End of conversation
New conversation -
-
-
FWIW I think you did a great job with Thor. I've really enjoyed using it to build CLI tools. Thank you!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
What would you have done differently, now that ya know, you have hindsight superpowers?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
