معرفی شرکت ها
django-organizations-2.1.0
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشترتوضیحات
Group accounts for Django
| ویژگی | مقدار |
|---|---|
| سیستم عامل | - |
| نام فایل | django-organizations-2.1.0 |
| نام | django-organizations |
| نسخه کتابخانه | 2.1.0 |
| نگهدارنده | [] |
| ایمیل نگهدارنده | [] |
| نویسنده | Ben Lopatin |
| ایمیل نویسنده | ben@benlopatin.com |
| آدرس صفحه اصلی | https://github.com/bennylope/django-organizations/ |
| آدرس اینترنتی | https://pypi.org/project/django-organizations/ |
| مجوز | BSD License |
====================
django-organizations
====================
.. start-table
.. list-table::
:stub-columns: 1
* - Summary
- Groups and multi-user account management
* - Author
- Ben Lopatin (http://benlopatin.com)
* - Status
- |docs| |travis| |version| |wheel| |supported-versions| |supported-implementations|
.. |docs| image:: https://readthedocs.org/projects/django-organizations/badge/?style=flat
:target: https://readthedocs.org/projects/django-organizations
:alt: Documentation Status
.. |travis| image:: https://travis-ci.org/bennylope/django-organizations.svg?branch=master
:alt: Travis-CI Build Status
:target: https://travis-ci.org/bennylope/django-organizations
.. |version| image:: https://img.shields.io/pypi/v/django-organizations.svg?style=flat
:alt: PyPI Package latest release
:target: https://pypi.python.org/pypi/django-organizations
.. |wheel| image:: https://img.shields.io/pypi/wheel/django-organizations.svg?style=flat
:alt: PyPI Wheel
:target: https://pypi.python.org/pypi/django-organizations
.. |supported-versions| image:: https://img.shields.io/pypi/pyversions/django-organizations.svg?style=flat
:alt: Supported versions
:target: https://pypi.python.org/pypi/django-organizations
.. |supported-implementations| image:: https://img.shields.io/pypi/implementation/django-organizations.svg?style=flat
:alt: Supported implementations
:target: https://pypi.python.org/pypi/django-organizations
.. end-table
Separate individual user identity from accounts and subscriptions. Django
Organizations adds user-managed, multi-user groups to your Django project. Use
Django Organizations whether your site needs organizations that function like
social groups or multi-user account objects to provide account and subscription
functionality beyond the individual user.
* Works with your existing user model, whether
`django.contrib.auth` or a custom model. No additional user
or authentication functionality required.
* Users can be belong to and own more than one organization (account, group)
* Invitation and registration functionality works out of the box for many
situations and can be extended as need to fit specific requirements.
* Start with the base models or use your own for greater customization.
Documentation is on `Read the Docs
<http://django-organizations.readthedocs.org/en/latest/index.html>`_
Development & Contributing
==========================
**The master branch represents version 2 development. For updates related to 1.x
versions of django-organizations pull requests should be made against the
[`version-1.x` branch](tree/version-1.x).**
Development is on-going. To-do items have been moved to the wiki for the time
being.
The basic functionality should not need much extending. Current dev priorities
for me and contributors should include:
* Improving the tests and test coverage (ideally moving them back out of the
main module and executable using the setup.py file)
* Improving the backends and backends concept so that additional invitation and
registration backends can be used
* Documentation
* Ensuring all application text is translatable
Please use the project's issues tracker to report bugs, doc updates, or other
requests/suggestions.
Targets & testing
-----------------
The codebase is targeted and tested against:
* Django 3.2.x against Python 3.7, 3.8, 3.9, 3.10
* Django 4.0.x against Python 3.8, 3.9, 3.10
* Django 4.1.x against Python 3.8, 3.9, 3.10
To run the tests against all target environments, install `tox
<https://testrun.org/tox/latest/>`_ and then execute the command::
tox
Fast testing
------------
Testing each change on all the environments takes some time, you may
want to test faster and avoid slowing down development by using pytest
against your current environment::
pip install -r requirements-test.txt
py.test
Supply the ``-x`` option for **failfast** mode::
py.test -x
Submitting
----------
These submission guidelines will make it more likely your submissions will be
reviewed and make it into the project:
* Ensure they match the project goals and are sufficiently generalized
* Please try to follow `Django coding style
<https://docs.djangoproject.com/en/stable/internals/contributing/writing-code/coding-style/>`_.
The code base style isn't all up to par, but I'd like it to move in that
direction
* Also please try to include `good commit log messages
<http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html>`_.
* Pull requests should include an amount of code and commits that are
reasonable to review, are **logically grouped**, and based off clean feature
branches.
Code contributions are expected to pass in all target environments, and
pull requests should be made from branches with passing builds on `GitHub Actions <https://github.com/bennylope/django-organizations/actions/workflows/test.yml>`_.
Project goals
-------------
django-organizations should be backend agnostic:
1. Authentication agnostic
2. Registration agnostic
3. Invitation agnostic
4. User messaging agnostic
Etc.
Installing
==========
First add the application to your Python path. The easiest way is to use
`pip`::
pip install django-organizations
Check the `Release History tab <https://pypi.org/project/django-organizations/#history>`_ on
the PyPI package page for pre-release versions. These can be downloaded by specifying the version.
You can also install by downloading the source and running::
$ python setup.py install
By default you will need to install `django-extensions` or comparable libraries
if you plan on adding Django Organizations as an installed app to your Django
project. See below on configuring.
Configuring
-----------
Make sure you have `django.contrib.auth` installed, and add the `organizations`
application to your `INSTALLED_APPS` list:
.. code-block:: python
INSTALLED_APPS = (
...
'django.contrib.auth',
'organizations',
)
Then ensure that your project URL conf is updated. You should hook in the
main application URL conf as well as your chosen invitation backend URLs:
.. code-block:: python
from organizations.backends import invitation_backend
urlpatterns = [
...
url(r'^accounts/', include('organizations.urls')),
url(r'^invitations/', include(invitation_backend().get_urls())),
]
Auto slug field
~~~~~~~~~~~~~~~
The standard way of using Django Organizations is to use it as an installed app
in your Django project. Django Organizations will need to use an auto slug
field which are not included. By default it will try to import these from
django-extensions, but you can configure your own in settings. The default:
.. code-block:: python
ORGS_SLUGFIELD = 'django_extensions.db.fields.AutoSlugField'
Alternative:
.. code-block:: python
ORGS_SLUGFIELD = 'autoslug.fields.AutoSlugField'
Previous versions allowed you to specify an `ORGS_TIMESTAMPED_MODEL` path. This
is now ignored and the functionality satisfied by a vendored solution. A
warning will be given but this *should not* have any effect on your code.
- `django-extensions <http://django-extensions.readthedocs.org/en/latest/>`_
- `Django AutoSlug <https://github.com/justinmayer/django-autoslug/>`_
- `django-slugger <https://gitlab.com/dspechnikov/django-slugger/>`_
Registration & invitation backends
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can specify a different invitation backend in your project settings, and
the `invitation_backend` function will provide the URLs defined by that
backend:
.. code-block:: python
INVITATION_BACKEND = 'myapp.backends.MyInvitationBackend'
Usage Overview
==============
For most use cases it should be sufficient to include the app views directly
using the default URL conf file. You can customize their functionality or
access controls by extending the base views.
There are three models:
* **Organization** The group object. This is what you would associate your own
app's functionality with, e.g. subscriptions, repositories, projects, etc.
* **OrganizationUser** A custom `through` model for the ManyToMany relationship
between the `Organization` model and the `User` model. It stores additional
information about the user specific to the organization and provides a
convenient link for organization ownership.
* **OrganizationOwner** The user with rights over the life and death of the
organization. This is a one to one relationship with the `OrganizationUser`
model. This allows `User` objects to own multiple organizations and makes it
easy to enforce ownership from within the organization's membership.
The underlying organizations API is simple:
.. code-block:: python
>>> from organizations.utils import create_organization
>>> chris = User.objects.get(username="chris")
>>> soundgarden = create_organization(chris, "Soundgarden", org_user_defaults={'is_admin': True})
>>> soundgarden.is_member(chris)
True
>>> soundgarden.is_admin(chris)
True
>>> soundgarden.owner.organization_user
<OrganizationUser: Chris Cornell>
>>> soundgarden.owner.organization_user.user
>>> <User: chris>
>>> audioslave = create_organization(chris, "Audioslave")
>>> tom = User.objects.get(username="tom")
>>> audioslave.add_user(tom, is_admin=True)
<OrganizationUser: Tom Morello>
Custom models
-------------
Django-organizations can act as a base library (not installed in your project)
and used to create unique organization model sets using custom tables. See the
`Cooking with Django Organizations
<http://django-organizations.readthedocs.org/en/latest/cookbook.html#advanced-customization>`_
section in the documentation for advice on proceeding.
License
=======
Anyone is free to use or modify this software under the terms of the BSD
license.
Sponsors
========
`Muster <https://www.muster.com/home?utm_source=github&campaign=opensource>`_ is building precision advocacy software to impact policy through grassroots action.
.. image:: https://www.muster.com/hs-fs/hubfs/muster_logo-2.png?width=600&name=muster_logo-2.png
:target: https://www.muster.com/home?utm_source=github&campaign=opensource
:width: 400
:alt: Alternative text
.. :changelog:
History
=======
2.1.0
-----
* Adds migrations to support Django 4.x
* Removes support for Django < 3.2
* Updates tox testing for supported configurations of Django 3.2 - 4.1 with Python 3.7 - 3.10
* Early tox testing of Django 4.1 with Python 3.11
* Fixes GitHub Actions automated testing
2.0.2
-----
* Remove `default_app_config` for forward compatiblity with Django 4.1
2.0.1
-----
* Better compatibility with Django 3.2
2.0.0
-----
* Invitation model backend uses models to track invitations
* Registration/inviation backends take an optional namespace argument on initialization. The use
case is if you want to namespace the URLs
* Can provide a dotted path to `invitation_backend` and `registration_backend` functions
* Drops support for Python 2 and Django versions < 2.2 LTS
* Migrate the codebase to an src/ layout
* Now with more test coverage!
1.1.1
-----
* Fixes issue with default backend where users defined without first/last names
might not be represented
1.1.0
-----
* Migrations and slug related fixup
This is a small but significant change. A change introduced in version 1.0.0 due to
incompatability with an unmaintained default dependency yielded migration issues for
many users. This release switches *back* to a *fork* of the original dependency
to revert the default changes.
1.0.0
-----
* Django 2 compatibility.
At this point it seems reasonable to bump to version 1.
0.9.3
-----
* Create username value for user if username field exists (custom user models)
* Replaced BaseBackend._send_email with BaseBackend.email_message. email_message() should return
the message without actually doing the send.
0.9.2
-----
* Decouple concrete organizations.Organization model from the invitation/registration backends
0.9.1
-----
* Fixes missing migration. Migration was created due to non-schema changes in models
0.9.0
-----
* Add notification to users when added to an organization
* New abstract models create separation between 'plain' base models and abstract
models that include abstracted functionality previously included only in
concrete models
* Python 3.6 and Django 1.11 test support
0.8.2
-----
* Updates setup classifiers information
0.8.1
-----
* Fixes [lack of] validation bug in backend registration form
0.8.0
-----
* Adds Django 1.10 support
0.7.0
-----
Fixes some issues which may require some users to clear out extraneous
migrations produced by using configurable base classes.
* Fixes condition where `create_organization` produces an owner who is not an
admin user.
* Fixes issue in slug field import resulting in spurious migrations.
* Immediately deprecates configurable TimeStampedModel import. This caused
serious problems with Django's migration library which were not easily
resolved for a feature that added little value.
0.6.1
-----
* Fixes email parsing from settings
0.6.0
-----
* Adds Django 1.9 support
* Drops support for Django 1.7
* Fixes migration issue related to incomplete support for configurable model
fields and base model. If you are upgrading (especially from a fork of the
development version of django-organization) you may have an extra migration,
0002_auto_20151005_1823, which has been removed.
0.5.3
-----
* Fixes migrations problem in build
0.5.2
-----
* Fixes packaging bug
0.5.1
-----
* Cleaned up installation instructions
0.5.0
-----
* Drops testing support for Django 1.5 and Django 1.6
* Adds native Django database migrations
* Adds tested support for Django 1.7 and Django 1.8
0.4.3
-----
* Adds app specific signals
0.4.2
-----
* Various related name fixes in models, registration backends
0.4.1
-----
* Support for older Django versions with outdated versions of `six`
0.4.0
-----
* Allows for configurable TimeStampModel (base mixin for default Organization
model) and AutoSlugField (field on default Organization model).
0.3.0
-----
* Initial Django 1.7 compatability release
0.2.3
-----
* Fix issue validating organziation ownership for custom organization models
inheriting directly from the `Organization` class.
0.2.2
-----
* Packaging fix
0.2.1
-----
* Packaging fix
0.2.0
-----
* Abstract base models. These allow for custom organization models
without relying on mulit-table inheritence, as well as custom
organization user models, all on an app-by-app basis.
0.1.10
------
* Packaging fix
0.1.9
-----
* Restructures tests to remove from installed module, should reduce installed
package size
0.1.8
-----
* Fixes *another* bug in email invitations
0.1.7
-----
* Fixes bug in email invitation
0.1.6
-----
* Extends organizaton name length
* Increase email field max length
* Adds `get_or_add_user` method to Organization
* Email character escaping
0.1.5
-----
* Use raw ID fields in admin
* Fixes template variable names
* Allow superusers access to all organization views
* Activate related organizations when activating an owner user
0.1.4a
------
* Bug fix for user model import
0.1.4
-----
* Bugfixes for deleting organization users
* Removes additional `auth.User` references in app code
0.1.3b
------
* Changes SlugField to an AutoSlugField from django-extensions
* Base models on TimeStampedModel from django-extensions
* ForeignKey to user model based on configurable user selection
0.1.3
-----
* Manage organization models with South
* Added configurable context variable names to view mixins
* Added a base backend class which the Invitation and Registration backends extend
* Lengthed Organization name and slug fields
* Makes mixin model classes configurable
* Improved admin display
* Removes initial passwords
0.1.2
-----
* Added registration backend
* Various bug fixes
0.1.1
-----
* Add RequestContext to default invitation registration view
* Fix invitations
0.1.0
-----
* Initial alpha application
نیازمندی
| مقدار | نام |
|---|---|
| - | six |
| >=2.2.0 | Django |
| - | typing |
نحوه نصب
نصب پکیج whl django-organizations-2.1.0:
pip install django-organizations-2.1.0.whl
نصب پکیج tar.gz django-organizations-2.1.0:
pip install django-organizations-2.1.0.tar.gz