Playbook has a structure that was ad-hoc and a few shortcuts were taken. A more scalable and robust solution is necessary if this is to be used by multiple teams.
Problem
Due to time constraints, the original implementation of Playbook had a few things which were not very customizable. Things like environment variables (Issue #55) and the hierarchy of Django Apps (Issue #32 ) were
Solution
This pull request address issues #55 and #32 . This new structure takes a Django app-driven approach, allowing each app to override another app if necessary.
In addition:
All the documentation was moved into the appropriate docs folder.
Seed data was moved into the bin folder, which contains scripts necessary for everyday contributors.
The requirements files can vary by environment. Some dependencies are needed only under certain circumstances.
kdflint
commented
9 years ago
Context
Playbook has a structure that was ad-hoc and a few shortcuts were taken. A more scalable and robust solution is necessary if this is to be used by multiple teams.
Problem
Due to time constraints, the original implementation of Playbook had a few things which were not very customizable. Things like environment variables (Issue #55) and the hierarchy of Django Apps (Issue #32 ) were
Solution
This pull request address issues #55 and #32 . This new structure takes a Django app-driven approach, allowing each app to override another app if necessary.
In addition:
docsfolder.binfolder, which contains scripts necessary for everyday contributors.requirementsfiles can vary by environment. Some dependencies are needed only under certain circumstances.