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

Store pride-level configuration #78

Closed
4 tasks done
lptr opened this issue Jul 24, 2014 · 2 comments
Closed
4 tasks done

Store pride-level configuration #78

lptr opened this issue Jul 24, 2014 · 2 comments
Milestone

Comments

@lptr
Copy link
Contributor

lptr commented Jul 24, 2014

For example the Gradle version to be used when (re)initializing the pride. Or even the default VCS.

  • add a .pride/config file to the pride

  • load the local configuration and merge it with the global configuration

  • allow pride config to modify the global and local configurations; Git-like:

    When reading, the values are read from the system, global and repository local configuration files by default, and options --system, --global, --local and --file can be used to tell the command to read from only that location (see FILES).

    When writing, the new value is written to the repository local configuration file by default, and options --system, --global, --file can be used to tell the command to write to that location (you can say --local but that is the default).

  • add pride init --purge to clear the configuration, but without this option try to load it

@lptr lptr added this to the 0.7.3 milestone Jul 24, 2014
@lptr
Copy link
Contributor Author

lptr commented Jul 25, 2014

Added local config : f15dd4c

@lptr
Copy link
Contributor Author

lptr commented Jul 25, 2014

Won't implement --purge right now -- that switch doesn't really sound right. Let's first think about how this should work in the first place. Until then people can delete .pride/config manually.

All the rest is implemented, plus unsetting properties.

@lptr lptr closed this as completed Jul 25, 2014
lptr added a commit that referenced this issue Jul 25, 2014
lptr added a commit that referenced this issue Jul 27, 2014
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

No branches or pull requests

1 participant