Django Appointments
Django Appointments is a Django reusable app for managing hospitals, doctor’s & patients. This Package comes with build in admin panel to manage users & hospitals. Hospitals can manage doctors, confirm appointments, view appointments. Pateints can sign up and create their profile to book appointments. Once appointment is confirmed appointment date and time is mailed to Doctor and Patient. Users can also regenrate passwords by password reset link.
Quick start
Add “crispy_forms”,”doctor”, “hospital”, “patient” & “user” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [ ... 'crispy_forms', 'doctor', 'hospital', 'patient', 'user', ... ]Add line : AUTH_USER_MODEL=’user.CustomUser’ to setting.py
Include the app URLconf in your project urls.py like this:
path('', include('user.urls')),Add SMTP server details to settings.py:-
EMAIL_BACKEND =’django.core.mail.backends.smtp.EmailBackend’ EMAIL_HOST = ‘smtp.your-host.com’ EMAIL_USE_TLS = True EMAIL_PORT = 587 EMAIL_HOST_USER = ‘user@your-host.com’ EMAIL_HOST_PASSWORD = ‘your-password’
Run python manage.py makemigrations to create the migrations.
Run python manage.py migrate to create the app models.
Run python manage.py createsuperuser to create admin username & password to login.
Start the development server and visit http://127.0.0.1:8000/manage/ to manage files & settings.
Visit http://127.0.0.1:8000/admin/ to add hospitals.
Hospital can add doctors.
Visit http://127.0.0.1:8000/signup/ to for patient signup.
Visit http://127.0.0.1:8000/login/ to login for doctors, hospitals, patients.
Bugtracker: https://github.com/deligence-vinit/django-appointments/issues
Code repository: https://github.com/deligence-vinit/django-appointments
For integration contact sanjay@deligence.com
Metadata
Release files for django-appointments 1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-appointments-1.5.tar.gz | 1.7 MB | Without provenance | Details for django-appointments-1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_appointments-1.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for django_appointments-1.5-py2.py3-none-any.whl |
Total release size: 3.3 MB
Release files / django-appointments-1.5.tar.gz
| Download URL | django-appointments-1.5.tar.gz |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e824861c2eb0469a8eb617cc30f25e3e9f8fda90a805e233fa5d63fa993e30d5
|
|
BLAKE2b-256 checksum How to use checksums |
7109f60c6c6b0dd5496ca108b534013f6d96b530bb93890f687bc8483094ab37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.6.9
|
Release files / django_appointments-1.5-py2.py3-none-any.whl
| Download URL | django_appointments-1.5-py2.py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
922cc119d80453e1e2ea1ede1cf14f5e6d76d6ac79f28d412acc5b4803379910
|
|
BLAKE2b-256 checksum How to use checksums |
1abb1f610403a36bee0d6269e07002f31040605e6fcb56eb8ea9560cb03e942e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.6.9
|
Security for django-appointments 1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.