No project description provided
Project description
Garpix Notify
Quickstart
Install with pip:
pip install garpix_notify
Add the garpix_notify and dependencies to your INSTALLED_APPS:
# settings.py
INSTALLED_APPS = [
# ...
'fcm_django',
'garpix_notify',
]
FCM_DJANGO_SETTINGS = {
"APP_VERBOSE_NAME": "Firebase Cloud Messaging",
"FCM_SERVER_KEY": "[your api key]",
"ONE_DEVICE_PER_USER": False,
"DELETE_INACTIVE_DEVICES": False,
}
NOTIFY_SMS_URL = "http://sms.ru/sms/send"
NOTIFY_SMS_API_ID = "[your api key from sms.ru]"
Package not included migrations, set path to migration directory. Don’t forget create this directory (app/migrations/garpix_notify/) and place empty __init__.py:
app/migrations/
app/migrations/__init__.py # empty file
app/migrations/garpix_notify/__init__.py # empty file
Add path to settings:
# settings.py
MIGRATION_MODULES = {
'garpix_notify': 'app.migrations.garpix_notify',
}
Create your custom user model and add AUTH_USER_MODEL to app/settings.py:
AUTH_USER_MODEL = 'user.User'
Run make migrations:
python manage.py makemigrations
Migrate:
python manage.py migrate
Example
Step 1. Set notify types in app/settings.py, for example:
REGISTRATION_EVENT = 1
FEEDBACK_EVENT = 2
EXAMPLE_EVENT_1 = 3
EXAMPLE_EVENT_2 = 4
NOTIFY_EVENTS = {
REGISTRATION_EVENT: {
'title': 'Register',
},
FEEDBACK_EVENT: {
'title': 'Feeback',
},
EXAMPLE_EVENT_1: {
'title': 'Example 1',
},
EXAMPLE_EVENT_2: {
'title': 'Example 2',
},
}
CHOICES_NOTIFY_EVENT = [(k, v['title']) for k, v in NOTIFY_EVENTS.items()]
Step 2. Go to the admin panel and go to the “Notifications” section - “SMTP accounts”
Add an SMTP account to send Email notifications. These will be the senders of Email notifications.
Step 3. Also go to “Notifications” - “Categories”
Create a category that will be used to send emails. Usually one category is enough. The ability to enter several categories is necessary to divide them into informational and marketing notifications.
Step 4. Go to “Notifications” - “Templates”
Create a template for a specific event (when you added them to settings.py).
Step 5. Call Notify.send()
In the code where it is necessary to work out sending a notification, we perform the following actions:
from django.conf import settings
from garpix_notify.models import Notify
# Syntax
# Notify.send(<event>, <context>[, <user=None>, <email=None>, <phone=None>, <files=None>, <data_json=None>])
# That is, we specify the event ID as the first parameter,
# create variables for the template,
# third - the user to send it to (it is not necessary to specify his email, phone number, etc.,
# because this will be determined automatically depending on the type of template)
# Пример
user = request.user # this will be the recipient of the notification.
Notify(settings.REGISTRATION_EVENT, {
'confirmation_code': 'abcdef12345',
}, user=user)
# If we do not have a user in the system, but we need to send an email, we can do the following
Notify(settings.EXAMPLE_EVENT_1, {
'confirmation_code': 'abcdef12345',
}, email='example@mail.ru')
Do not forget run celery:
celery -A app worker --loglevel=info -B
Changelog
See CHANGELOG.md.
Contributing
See CONTRIBUTING.md.
License
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for garpix_notify-4.1.0-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | f4d1623e5b3ecb42b1b45b6aec41b121c2b51c31a1f060dcdb3a4a2661a26912 |
|
MD5 | e322ba40e9c38b7b9afce0b8355c33be |
|
BLAKE2b-256 | a1111cddc8cf22bbd997bde31a74049876168c178d72f1c30a49167dbf298a2a |