Move to Opscode cookbook layout #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main intent of this branch was to move to the way Opscode structures their cookbooks. The cookbook now stands alone without including its dependencies, so it can easily be added as a git submodule to a
cookbooksfolder with its dependencies alongside it. As a side-effect, it no longer makes sense to include aVagrantfilein the repository. An example Vagrant box repository could easily be provided separately.In the process, I added support for Postgres 9.1, and bumped the versions of GEOS and PostGIS to the latest versions GeoDjango explicitly supports.