Usually, these are easy to add here dsa_actionkit/templatetags/actionkit_tags.py Actionkit provides implementations here
If you make a context that's not covered already, please contribute with a patch to dsa_actionkit/contexts/ Note that these are also useful to browse to see what variables you can access from a particular page context.
For all intents and purposes, this project can be managed, run, and developed like a normal Django project. Notable deviations are listed below.
By default, a simple SQLite database (db.sqlite, ignored by git) is created alongside the project. The included migrations represent models that were created from the Robotic Dogs sandbox database provided by ActionKit, mirroring the database schema.
If you'd like to connect to Robotic Dogs directly within the project for further exploration, check out the Django documentation on multiple databases and include a .env file in your project root containing your credentials:
ROBOTIC_DOGS_USER=yourusername
ROBOTIC_DOGS_PASSWORD=yourpassword
- The Django "project" settings live in the
dsa_actionkitdirectory, which provides configurations for the apps within the project - Django "apps" are generated by the
django-admin/manage.pycommand and are integrated into the Django project via theINSTALLED_APPSsetting. They can be considered normal Python packages within the project, the modules they contain may be imported accordingly. Currently, this includesmydsaand its contents. Usually, apps will be split out by their purpose within the project. For example, a project may have apps for Authentication, Payments System, Emails and Notifications, etc.