Pegasus’s Code Structure¶
This is the overall structure of a new Pegasus project:
The first three directories are Python modules while the remaining ones are not.
This is your Django project root directory.
It’s where your settings, root urlconf and
wsgi.py file will live.
This is where your project’s apps will live. It is pre-populated with Pegasus’s default apps for you to further customize to your needs.
The module starts with up to five apps, depending on your configuration.
subscriptionsis for functionality related to Stripe subscriptions.
usersis where your user models and views are defined.
teamsis where team models and views are defined.
utilsis a set of functionality shared across the project.
webcontains utilities and components related to the generic views, layouts and templates.
This is where the Pegasus examples live.
In general it is not expected that you’ll need to modify much in this module, though feel free to do so!
This is where you define your project’s Python requrements.
Requirements are managed using
For more information on using it see their documentation.
See front-end for more information on how to compile these files.
This folder contains your project’s static files, including the compiled output files
assets folder as well as images.
This folder contains your project’s Django templates.
There is one sub-folder for each application that has templates.
The majority of the project’s base template layouts are in the