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.

Sign up for GitHub

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

Jump to bottom

non-private settings #50

Closed
ilyakatz opened this issue Apr 25, 2013 · 1 comment
Closed

non-private settings #50

ilyakatz opened this issue Apr 25, 2013 · 1 comment

Comments

@ilyakatz
Copy link

Figaro is great to configure private settings, but it would be great if it could also support non-private settings that can be safely committed a VCS
@laserlemon
Copy link
Owner

I'd like to understand this better. Is the appeal the central location for these settings in one file? If the configuration is not private and would be committed to the repository, I typically configure/use those values where needed rather than pulling from a central location.

@eric-smartlove eric-smartlove mentioned this issue Jul 7, 2013
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@laserlemon @ilyakatz