django-mvp-community 0.1.0__tar.gz

django_mvp_community-0.1.0/.gitignore

@@ -0,0 +1,65 @@
+# Temporary and binary files
+*~
+*.ruff_cache
+*.mypy_cache
+*.py[cod]
+*.so
+*.cfg
+!.isort.cfg
+!setup.cfg
+*.orig
+*.log
+*.pot
+**/__pycache__
+.cache/*
+.*.swp
+*/.ipynb_checkpoints/*
+.DS_Store
+.vscode/
+.github/instructions/
+docs/api/
+
+# Unittest and coverage
+htmlcov
+.coverage
+.coverage.*
+.tox
+junit*.xml
+coverage.xml
+.pytest_cache/
+
+# Build and docs folder/files
+build/*
+dist/*
+sdist/*
+docs/_rst/*
+docs/_build/*
+cover/*
+MANIFEST
+
+# Per-project virtualenvs
+.venv*/
+.conda*/
+.python-version
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+media/
+/static/
+/*.sqlite3
+
+# */static/vendor/*
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+dist

django_mvp_community-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Samuel Jennings
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

django_mvp_community-0.1.0/PKG-INFO

@@ -0,0 +1,242 @@
+Metadata-Version: 2.5
+Name: django-mvp-community
+Version: 0.1.0
+Summary: Notifications, mail and activity pages for django-mvp projects, built on established Django packages
+Project-URL: Homepage, https://github.com/django-mvp/django-mvp-community
+Project-URL: Repository, https://github.com/django-mvp/django-mvp-community
+Project-URL: Issues, https://github.com/django-mvp/django-mvp-community/issues
+Author-email: Samuel Jennings <samuel.scott.jennings@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: cotton,django,django-mvp
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Web Environment
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Framework :: Django :: 6.0
+Classifier: Framework :: Django :: 6.1
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
+Requires-Python: <4.0,>=3.12
+Requires-Dist: django-mvp>=0.28.1
+Requires-Dist: django>=5.2
+Provides-Extra: activity
+Requires-Dist: django-activity-stream>=2.0; extra == 'activity'
+Provides-Extra: mail
+Requires-Dist: django-anymail>=13; extra == 'mail'
+Requires-Dist: django-post-office>=3.12; extra == 'mail'
+Provides-Extra: notifications
+Requires-Dist: django-generic-notifications>=2.4; extra == 'notifications'
+Provides-Extra: push
+Requires-Dist: cryptography>=42; extra == 'push'
+Requires-Dist: django-generic-notifications>=2.4; extra == 'push'
+Requires-Dist: django-push-notifications[wp]>=3.3; extra == 'push'
+Requires-Dist: py-vapid>=1.9; extra == 'push'
+Requires-Dist: requests>=2.31; extra == 'push'
+Requires-Dist: ua-parser>=1.0; extra == 'push'
+Provides-Extra: sharecards
+Description-Content-Type: text/markdown
+
+# django-mvp-community
+
+[![Tests](https://github.com/django-mvp/django-mvp-community/actions/workflows/tests.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/tests.yml)
+[![Build](https://github.com/django-mvp/django-mvp-community/actions/workflows/build.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/build.yml)
+[![Publish](https://github.com/django-mvp/django-mvp-community/actions/workflows/publish.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/publish.yml)
+[![codecov](https://codecov.io/gh/django-mvp/django-mvp-community/branch/main/graph/badge.svg)](https://codecov.io/gh/django-mvp/django-mvp-community)
+[![PyPI](https://img.shields.io/pypi/v/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Development status](https://img.shields.io/pypi/status/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Python](https://img.shields.io/pypi/pyversions/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Django](https://img.shields.io/pypi/djversions/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![License](https://img.shields.io/github/license/django-mvp/django-mvp-community)](https://github.com/django-mvp/django-mvp-community/blob/main/LICENSE)
+[![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
+
+Notifications, mail and activity pages for django-mvp projects, built on established Django packages
+
+<!--
+  The README is this package's charter, and it is read in two places: on the
+  repository page and on the package index. Write it for someone deciding
+  whether to install this, who has not read anything else here.
+
+  Every link is absolute. A relative link resolves on GitHub and 404s on PyPI,
+  which is where the person deciding is most likely to be standing.
+
+  The badge row above is the standard set for a published package: one status
+  badge per workflow that runs on a push or a pull request, then coverage, the
+  PyPI version, supported Python and Django, and the licence. A workflow added
+  later gets its badge in the same row. The PyPI badges read "not found" until
+  the first release, and the GitHub ones need the repository to be public.
+
+  Sections, in this order:
+    1. One sentence, above. What it does, for whom.
+    2. Scope & philosophy — below. What it is and is not, and the principles
+       that settle a close call.
+    3. Installation.
+    4. Quickstart — the smallest thing that works, end to end.
+    5. The public surface, in full. For a package this small, list it.
+    6. Anything genuinely surprising: what it deliberately does not do, what it
+       leaves to the host project, and the failure modes that are quiet.
+
+  Keep the CHANGELOG out of it. Link to it instead.
+-->
+
+## Scope & philosophy
+
+django-mvp-community gives a django-mvp project the pages and components for
+keeping people in touch with the site and with each other: notifications and
+their preferences, push and reminders, email, and activity feeds. Each is built
+on an established Django package, and this package supplies what those packages
+leave to you: templates that match the rest of the application, menu entries,
+Account Center pages, settings, and the few lines of wiring that connect one
+package to another. Each feature is an optional extra, installed only when a
+project wants it.
+
+What it deliberately is not:
+
+- **A notification, mail or activity engine.** It adds no logic or models of its
+  own. The packages it builds on do the work.
+- **Real-time.** No websockets or server-sent events. Unread counts refresh by
+  polling.
+- **Native phone push.** Web push to browsers and installed web apps only.
+- **A mail service.** Mail goes out through whichever provider django-anymail is
+  configured for.
+- **A forum.**
+
+When two designs conflict, the one with less code of our own wins. A template
+override beats a Python hook, and an existing package beats anything written
+here.
+
+## Installation
+
+```bash
+pip install django-mvp-community
+```
+
+Then add it to `INSTALLED_APPS`, above `mvp`:
+
+```python
+INSTALLED_APPS = [
+    # ...
+    "mvp_community",
+    "mvp",
+]
+```
+
+It goes above `mvp` because some of its templates extend django-mvp's templates of
+the same name, such as the Account Center's landing page. Django uses the first one
+it finds, so listed below `mvp` they are never used.
+
+This package requires [django-mvp](https://github.com/django-mvp/django-mvp).
+It renders inside django-mvp's layout and reads its colours from the theme
+django-mvp supplies, so it does nothing useful on its own.
+
+## Extras
+
+Each feature is an extra, installed by naming it:
+
+```bash
+pip install "django-mvp-community[notifications]"
+```
+
+The extras are `notifications`, `push`, `mail`, `activity` and `sharecards`. An extra
+brings the packages its feature is built on, and the base install depends on
+Django and django-mvp alone. Importing `mvp_community` never imports a package
+that belongs to an extra, so a project carries nothing for a feature it does
+not use.
+
+Code that needs an extra's packages lives in that extra's integration module,
+`mvp_community.integrations.<extra>`, and nowhere else in the package. A
+project switches an extra on by installing it and importing from that module.
+
+The `notifications` extra is built and documented in
+[Notifications](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/notifications.md):
+a bell in the header, a notifications page, notification preferences in
+the Account Center, and, with the `mail` extra, notifications by email in real
+time or as a daily or weekly digest.
+
+The `push` extra is built and documented in
+[Push](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/push.md):
+a push channel for notifications, so a person who turns push on from their
+preferences page gets each notification in their browser as it happens, even
+when the site is closed.
+
+The `activity` extra is built and documented in
+[Activity](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/activity.md):
+a feed view you mount where you like, a following page in the Account Center,
+and components for recent activity, a follow control and a followers list.
+
+The `mail` extra is configured and documented in
+[Mail](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/mail.md):
+every email your project sends is queued and logged, then delivered through
+your provider, and stored templates extend django-mvp's email layout. It is
+settings and documentation only, so there is no integration module to import.
+The other extra is empty for now: installing it adds no packages, and there is
+no integration module to import.
+
+## Overriding a template
+
+Any template this package ships can be replaced on its own, without forking
+the package. A template's name is its path below `mvp_community/templates/`,
+and Django uses the first template it finds with that name. Put a file with the
+same name in the project's own template directory, the one listed in
+`TEMPLATES["DIRS"]`, and Django uses it instead of this package's. A template
+in an app listed above `mvp_community` in `INSTALLED_APPS` overrides it in the
+same way.
+
+Components follow the same rule. A component's tag is its path below
+`templates/cotton/`, so this file in the project replaces the component
+`<c-mvp_community.name>` everywhere it is used:
+
+```text
+templates/cotton/mvp_community/name.html
+```
+
+Template names are part of the public interface. Renaming one is a breaking
+change, made only after a release that warns about it, with the CHANGELOG
+naming what replaces it.
+
+## Quickstart
+
+<!--
+  The smallest complete example: what goes in the view, what goes in the
+  template, and what appears on the page. Real code that runs, not a sketch.
+  If the example needs three files, show three files.
+-->
+
+## Public surface
+
+<!--
+  Everything a host project can touch: components and their attributes,
+  settings, template tags, models, views. Being able to list it exhaustively is
+  a feature of a package this size, and the list is what makes an addition to
+  it a deliberate decision rather than a side effect.
+-->
+
+## Contributing
+
+Standards for this repository live in
+[CONSTITUTION.md](https://github.com/django-mvp/django-mvp-community/blob/main/CONSTITUTION.md),
+and the vocabulary to use in issues and commits lives in
+[CONTEXT.md](https://github.com/django-mvp/django-mvp-community/blob/main/CONTEXT.md).
+
+```bash
+uv sync
+uv run pytest
+uv run pre-commit install
+```
+
+`demo/` is a Django project on django-mvp's application shell, for looking at
+this package in a browser while working on it:
+
+```bash
+uv run python manage.py migrate
+uv run python manage.py seed_demo
+uv run python manage.py runserver
+```
+
+## License
+
+MIT. See [LICENSE](https://github.com/django-mvp/django-mvp-community/blob/main/LICENSE).

django_mvp_community-0.1.0/README.md

@@ -0,0 +1,199 @@
+# django-mvp-community
+
+[![Tests](https://github.com/django-mvp/django-mvp-community/actions/workflows/tests.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/tests.yml)
+[![Build](https://github.com/django-mvp/django-mvp-community/actions/workflows/build.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/build.yml)
+[![Publish](https://github.com/django-mvp/django-mvp-community/actions/workflows/publish.yml/badge.svg)](https://github.com/django-mvp/django-mvp-community/actions/workflows/publish.yml)
+[![codecov](https://codecov.io/gh/django-mvp/django-mvp-community/branch/main/graph/badge.svg)](https://codecov.io/gh/django-mvp/django-mvp-community)
+[![PyPI](https://img.shields.io/pypi/v/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Development status](https://img.shields.io/pypi/status/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Python](https://img.shields.io/pypi/pyversions/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![Django](https://img.shields.io/pypi/djversions/django-mvp-community)](https://pypi.org/project/django-mvp-community/)
+[![License](https://img.shields.io/github/license/django-mvp/django-mvp-community)](https://github.com/django-mvp/django-mvp-community/blob/main/LICENSE)
+[![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
+
+Notifications, mail and activity pages for django-mvp projects, built on established Django packages
+
+<!--
+  The README is this package's charter, and it is read in two places: on the
+  repository page and on the package index. Write it for someone deciding
+  whether to install this, who has not read anything else here.
+
+  Every link is absolute. A relative link resolves on GitHub and 404s on PyPI,
+  which is where the person deciding is most likely to be standing.
+
+  The badge row above is the standard set for a published package: one status
+  badge per workflow that runs on a push or a pull request, then coverage, the
+  PyPI version, supported Python and Django, and the licence. A workflow added
+  later gets its badge in the same row. The PyPI badges read "not found" until
+  the first release, and the GitHub ones need the repository to be public.
+
+  Sections, in this order:
+    1. One sentence, above. What it does, for whom.
+    2. Scope & philosophy — below. What it is and is not, and the principles
+       that settle a close call.
+    3. Installation.
+    4. Quickstart — the smallest thing that works, end to end.
+    5. The public surface, in full. For a package this small, list it.
+    6. Anything genuinely surprising: what it deliberately does not do, what it
+       leaves to the host project, and the failure modes that are quiet.
+
+  Keep the CHANGELOG out of it. Link to it instead.
+-->
+
+## Scope & philosophy
+
+django-mvp-community gives a django-mvp project the pages and components for
+keeping people in touch with the site and with each other: notifications and
+their preferences, push and reminders, email, and activity feeds. Each is built
+on an established Django package, and this package supplies what those packages
+leave to you: templates that match the rest of the application, menu entries,
+Account Center pages, settings, and the few lines of wiring that connect one
+package to another. Each feature is an optional extra, installed only when a
+project wants it.
+
+What it deliberately is not:
+
+- **A notification, mail or activity engine.** It adds no logic or models of its
+  own. The packages it builds on do the work.
+- **Real-time.** No websockets or server-sent events. Unread counts refresh by
+  polling.
+- **Native phone push.** Web push to browsers and installed web apps only.
+- **A mail service.** Mail goes out through whichever provider django-anymail is
+  configured for.
+- **A forum.**
+
+When two designs conflict, the one with less code of our own wins. A template
+override beats a Python hook, and an existing package beats anything written
+here.
+
+## Installation
+
+```bash
+pip install django-mvp-community
+```
+
+Then add it to `INSTALLED_APPS`, above `mvp`:
+
+```python
+INSTALLED_APPS = [
+    # ...
+    "mvp_community",
+    "mvp",
+]
+```
+
+It goes above `mvp` because some of its templates extend django-mvp's templates of
+the same name, such as the Account Center's landing page. Django uses the first one
+it finds, so listed below `mvp` they are never used.
+
+This package requires [django-mvp](https://github.com/django-mvp/django-mvp).
+It renders inside django-mvp's layout and reads its colours from the theme
+django-mvp supplies, so it does nothing useful on its own.
+
+## Extras
+
+Each feature is an extra, installed by naming it:
+
+```bash
+pip install "django-mvp-community[notifications]"
+```
+
+The extras are `notifications`, `push`, `mail`, `activity` and `sharecards`. An extra
+brings the packages its feature is built on, and the base install depends on
+Django and django-mvp alone. Importing `mvp_community` never imports a package
+that belongs to an extra, so a project carries nothing for a feature it does
+not use.
+
+Code that needs an extra's packages lives in that extra's integration module,
+`mvp_community.integrations.<extra>`, and nowhere else in the package. A
+project switches an extra on by installing it and importing from that module.
+
+The `notifications` extra is built and documented in
+[Notifications](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/notifications.md):
+a bell in the header, a notifications page, notification preferences in
+the Account Center, and, with the `mail` extra, notifications by email in real
+time or as a daily or weekly digest.
+
+The `push` extra is built and documented in
+[Push](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/push.md):
+a push channel for notifications, so a person who turns push on from their
+preferences page gets each notification in their browser as it happens, even
+when the site is closed.
+
+The `activity` extra is built and documented in
+[Activity](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/activity.md):
+a feed view you mount where you like, a following page in the Account Center,
+and components for recent activity, a follow control and a followers list.
+
+The `mail` extra is configured and documented in
+[Mail](https://github.com/django-mvp/django-mvp-community/blob/main/docs/developer/mail.md):
+every email your project sends is queued and logged, then delivered through
+your provider, and stored templates extend django-mvp's email layout. It is
+settings and documentation only, so there is no integration module to import.
+The other extra is empty for now: installing it adds no packages, and there is
+no integration module to import.
+
+## Overriding a template
+
+Any template this package ships can be replaced on its own, without forking
+the package. A template's name is its path below `mvp_community/templates/`,
+and Django uses the first template it finds with that name. Put a file with the
+same name in the project's own template directory, the one listed in
+`TEMPLATES["DIRS"]`, and Django uses it instead of this package's. A template
+in an app listed above `mvp_community` in `INSTALLED_APPS` overrides it in the
+same way.
+
+Components follow the same rule. A component's tag is its path below
+`templates/cotton/`, so this file in the project replaces the component
+`<c-mvp_community.name>` everywhere it is used:
+
+```text
+templates/cotton/mvp_community/name.html
+```
+
+Template names are part of the public interface. Renaming one is a breaking
+change, made only after a release that warns about it, with the CHANGELOG
+naming what replaces it.
+
+## Quickstart
+
+<!--
+  The smallest complete example: what goes in the view, what goes in the
+  template, and what appears on the page. Real code that runs, not a sketch.
+  If the example needs three files, show three files.
+-->
+
+## Public surface
+
+<!--
+  Everything a host project can touch: components and their attributes,
+  settings, template tags, models, views. Being able to list it exhaustively is
+  a feature of a package this size, and the list is what makes an addition to
+  it a deliberate decision rather than a side effect.
+-->
+
+## Contributing
+
+Standards for this repository live in
+[CONSTITUTION.md](https://github.com/django-mvp/django-mvp-community/blob/main/CONSTITUTION.md),
+and the vocabulary to use in issues and commits lives in
+[CONTEXT.md](https://github.com/django-mvp/django-mvp-community/blob/main/CONTEXT.md).
+
+```bash
+uv sync
+uv run pytest
+uv run pre-commit install
+```
+
+`demo/` is a Django project on django-mvp's application shell, for looking at
+this package in a browser while working on it:
+
+```bash
+uv run python manage.py migrate
+uv run python manage.py seed_demo
+uv run python manage.py runserver
+```
+
+## License
+
+MIT. See [LICENSE](https://github.com/django-mvp/django-mvp-community/blob/main/LICENSE).

django_mvp_community-0.1.0/mvp_community/__init__.py

@@ -0,0 +1 @@
+"""The Community app for django-mvp."""

django_mvp_community-0.1.0/mvp_community/apps.py

@@ -0,0 +1,43 @@
+"""App configuration for django-mvp-community."""
+
+from django.apps import AppConfig, apps
+from django.utils.translation import gettext_lazy as _
+
+
+class MvpCommunityConfig(AppConfig):
+    """What a project gets when it adds this package to INSTALLED_APPS.
+
+    The label is set explicitly rather than left to Django's default, which is
+    the last segment of the module path. Two installed apps whose paths end in
+    the same word collide on that default, and the error names neither of them
+    clearly.
+    """
+
+    name = "mvp_community"
+    label = "mvp_community"
+    verbose_name = _("Community")
+    default_auto_field = "django.db.models.BigAutoField"
+
+    def ready(self):
+        """Add each installed extra's Account Center entry."""
+        if apps.is_installed("generic_notifications"):
+            from mvp_community.integrations.notifications import (
+                checks,  # noqa: F401
+                menus,  # noqa: F401
+                setup,
+            )
+
+            setup.configure(apps.is_installed("post_office"))
+        if apps.is_installed("generic_notifications") and apps.is_installed(
+            "push_notifications"
+        ):
+            from mvp_community.integrations.push import (
+                checks as push_checks,  # noqa: F401
+            )
+            from mvp_community.integrations.push import setup as push_setup
+
+            push_setup.configure()
+        if apps.is_installed("actstream"):
+            from mvp_community.integrations.activity import (
+                menus as activity,  # noqa: F401
+            )

django_mvp_community-0.1.0/mvp_community/integrations/__init__.py

@@ -0,0 +1 @@
+"""Modules that import an extra's packages. A project imports one only when it uses that extra."""

django_mvp_community-0.1.0/mvp_community/integrations/activity/__init__.py

@@ -0,0 +1 @@
+"""The activity extra, built on django-activity-stream."""

django_mvp_community-0.1.0/mvp_community/integrations/activity/menus.py

@@ -0,0 +1,13 @@
+"""The Account Center entry for the page listing what a person follows."""
+
+from django.utils.translation import gettext_lazy as _
+from flex_menu import MenuItem
+from mvp.menus import AccountCenterMenu
+
+AccountCenterMenu.append(
+    MenuItem(
+        name="following",
+        view_name="mvp_community_activity:following",
+        extra_context={"label": _("Following"), "icon": "activity.following"},
+    )
+)

django_mvp_community-0.1.0/mvp_community/integrations/activity/streams.py

@@ -0,0 +1,24 @@
+"""The one stream this package shapes beyond django-activity-stream's own."""
+
+from actstream.models import Action
+from django.contrib.contenttypes.models import ContentType
+
+
+def followed_activity(user, **filters):
+    """Return the public activity of what ``user`` follows, without their own actions.
+
+    django-activity-stream's ``user`` stream also holds the person's own actions
+    where they act on something they follow, and the "started following" each
+    follow records. The feed of what a person follows leaves those out.
+
+    Args:
+        user: The signed-in person.
+        **filters: Passed to the stream, such as ``verb``.
+
+    Returns:
+        The stream, newest first.
+    """
+    return Action.objects.user(user, **filters).exclude(
+        actor_content_type=ContentType.objects.get_for_model(user),
+        actor_object_id=str(user.pk),
+    )

django_mvp_community-0.1.0/mvp_community/integrations/activity/urls.py

@@ -0,0 +1,46 @@
+"""The activity extra's routes.
+
+Include this at the root, ``path("", include(...))``, as django-mvp's own URLs
+are: each route chooses its own address.
+
+Only django-activity-stream's four follow routes are taken from its URLconf.
+The rest of it also shows actions that are not public and lists anyone's
+follows to anyone. The follow routes keep their own names, with no namespace,
+because django-activity-stream's template tags reverse them by those names.
+"""
+
+from actstream import urls as actstream_urls
+from django.urls import include, path
+
+from . import views
+
+FOLLOW_ROUTES = {
+    "actstream_follow",
+    "actstream_follow_all",
+    "actstream_unfollow",
+    "actstream_unfollow_all",
+}
+
+pages = [
+    path(
+        "account-center/following/",
+        views.FollowingView.as_view(),
+        name="following",
+    ),
+    path(
+        "activity/control/<int:content_type_id>/<str:object_id>/",
+        views.FollowControlView.as_view(),
+        name="follow_control",
+    ),
+]
+
+follow_routes = [
+    route
+    for route in actstream_urls.urlpatterns
+    if getattr(route, "name", None) in FOLLOW_ROUTES
+]
+
+urlpatterns = [
+    path("", include((pages, "mvp_community_activity"))),
+    path("activity/", include(follow_routes)),
+]