Closed siruguri closed 7 years ago
@schaui6 @akanshmurthy
@siruguri sounds good to me
Sounds good. I'm even leaving out the client altogether so that they can go to the API documentation and figure it out but it might be good to have one with a client so that they can understand a bit better.
Thanks.
Typed on a phone
On Nov 2, 2016 1:49 PM, "Akansh Murthy" notifications@github.com wrote:
Sounds good.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/akanshmurthy/railsbridge-hackathon/issues/13#issuecomment-257994508, or mute the thread https://github.com/notifications/unsubscribe-auth/AACezbC-WCtPxVlrnnN9oFMPAf5vIBshks5q6PdRgaJpZM4Knkak .
I'm writing tests for bitly, and need to test the test with a Bitly client. I want to leave in some pieces of the code I'm writing, as a best practice example - specifically how to initialize the client with a password.
I usually check in
config/secrets.yml
, but use thedotenv
gem - but that might be too many steps for a beginner coder. Instead, I want to stop trackingconfig/secrets
and add it to.gitignore
I can also create aconfig/secrets.yml.sample
that does get checked in.Is this strategy ok by you guys?