Version History and Release Notes¶
0.23.0to fix installation version conflict.
May 26, 2020
This release begins the move of Pegasus’s core functionality out of the “pegasus” app and into the user-defined apps. It’s a relatively big release from a code perspective, although there is very little new / changed in terms of functionality.
The philosophy guiding this change is “your starting code base should be as understandable as possible”.
Historically, Pegasus has attempted to separate “Pegasus-owned” files from “user-owned” files. The thinking behind this structure was that Pegasus upgrades and code merges would be as easy as possible since - in theory - users would not need to modify anything in the “Pegasus-owned” space.
In practice, the line between “Pegasus-owned” and “user-owned” was fuzzy, and customizing an application often required editing files in the “Pegasus-owned” space. So the benefit was not realized.
Furthermore, this split caused the initial codebase to be more confusing, since core functionality was split across two places.
Changes related to the restructure above include:
- Moved all base templates from
- Moved team invitation templates from
pegasus/apps/usersand all related code into
pegasus/apps/teamsand all related code into
pegasus/apps/componentsand moved code to more specific apps - further details below
promote_user_to_superusermanagement command into
bootstrap_subscriptionsmanagement command into
google_analytics_idcontext processor to web app
meta.pyfrom pegasus app to web app
apps.utilsand moved most of
apps.utilsand renamed to
- Removed unused
stripe.pyfile (replacing functionality with equivalent functions in
- Removed “Pegasus” from API url names
- Moved non-example JS imports out of
- Lowercased (and kebab-cased) all JS file names for consistency
- Moved sass files from
- Renamed various layout classes, e.g.
pegasus-message, etc. to
- Removed unused
Other changes and fixes include:
- Fix accepting an invitation if you’re already signed in
- Remove subscription-related fields from team and user models if not using subscriptions
- Only ship base migration files for users and teams, and have applications manage their own migrations
- Improved checks and error-handling around accepting invitations multiple times
bulmaCSS framework to
npm audit fixto update other JS library dependencies
pip-toolsand other packages in
- Added backend check to the payments example, to show how to prevent client-side exploits
- Improve password reset email copy
- Externalized styles on progress bar demo
A Note on Database Migrations¶
Historically, Pegasus has shipped with complete database migrations. However, maintaining a set of migrations for each possible Pegasus configuration or forcing all configurations to use the same DB schema has proven unwieldy. Thus, migrations are now expected to be managed outside of Pegasus.
For new users, the only change is that prior to running
./manage.py migrate for the first time,
you must first run
For existing users you can either keep your current migrations folder, or you can run
./manage.py makemigrations and then
./manage.py migrate --fake. If you have changed the user or team
models, then you should keep your current folder.
May 19, 2020
- Fixed default Postgres DB settings (adding host and port)
- Removed Stripe webhooks from project urls if not using subscriptions
- Fixed but where subscription and teams templates were still being included even if not enabled for a project
- Cleaned up progress bar demo
- Switched from
constin a few places
- Removed debug logging statements
May 7, 2020
Version 0.5.1 is a minor maintenance release with a few minor bug fixes and bits of cleanup:
- Upgraded Django to 3.0.5
- Fixed bug where certain input types were getting overridden in Django Forms (thanks Yaniv for reporting!)
- Fixed bug with Object Lifecycle and Charts demos not working on Team installations (thanks Greg for reporting!)
admin.pyfiles to use the
April 17, 2020
This is the biggest release to Pegasus since it’s launch. Read below for all the details.
Added the Stripe Subscriptions feature.
Documentation for subscriptions can be found here.
- Added a
CustomUserobjects, and a
SubscriptionModelMixinhelper class for accessing / checking subscription status on a model.
Pegasus.jsand made different modules available in front end code (see subscriptions upgrade page example usage).
Sass / CSS changes¶
- Added a few margin helper classes (e.g.
Small fixes and changes:¶
- Moved app-specific templates from inside the apps to global templates directory as recommended by Two Scoops of Django
- Remove redundant raw prefix on some
- Reduced some duplicate access to
teamobject when already available via the
- Made team permission template tags more consistent with rest of site (also allow access to superusers)
pegasus_settingscontext processor. All config is now handled at installation time instead of by settings variables.
- Catch Stripe card errors in the payments example
- Upgraded various
- Upgraded Bulma to 0.8.0