Djaken Notes
Djaken is a complete web-based notes application for Django.
News
Version 2.0.2 released! (2018/12/15)
Version 2.0rc1 released! (2018/12/06)
Version 2.0b1 released! (2018/04/14)
Changes in 2.0~:
Replace Markdown with reStructuredText.
Move inline images to seperate model (DB) field, thus avoiding search and markup processing on bulky image data. It also takes away the encoded image data from the markup text.
GUI: several improvements (HTML templates and CSS).
GUI: Edit Note; change “Save and Close” button to icon and have all three save and close permutations at top and bottom of note.
CODING: Change ‘Generic Views’ back to regular/full Django views.
FIXED: Page reload after going back to unlock encrypted note re-submits encryption key (password).
Disable browser caching as much as possible.
Features
Intuitive, simple and stream-lined user interface.
Login/logout of the notes application.
Create and edit notes in reStructuredText.
Attach inline images (within a note).
Notes can be marked ‘Not relevant’, and if so, are kept out of view by default.
Encrypted notes (stored in database using an AES symmetric cipher).
Keyword search of note title and content.
Sort by modified/created date.
Options / Settings
DJAKEN_BRANDING_TITLE (str:default=’Djaken Notes’)
Requirements
Django>=1.9
docutils>=0.12
pycrypto>=2.6
Quick start
Add “djaken” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [ ... 'djaken', ]Include the djaken URLconf in your project urls.py like this:
url(r'^djaken/', include('djaken.urls')),Run python manage.py migrate to create the djaken models.
Start the development server and visit http://127.0.0.1:8000/djaken/ to start adding notes.
Screen-shots
Only viewable on GitHub project page
All Notes (homepage)
View Note
Edit Note
Unlock an encrypted note
1 maintainer
Metadata
1 maintainer
Release files for django-djaken 2.0.2
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-djaken-2.0.2.tar.gz | 2.9 MB | Without provenance | Details for django-djaken-2.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_djaken-2.0.2-py3-none-any.whl | Python 3 | none | any | Details for django_djaken-2.0.2-py3-none-any.whl |
Total release size: 5.8 MB
Release files / django-djaken-2.0.2.tar.gz
| Download URL | django-djaken-2.0.2.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3ed6b8a61fc69dd6fbcb51ba540a26e99d5e37a5df58ede384c0d8697f94461
|
|
BLAKE2b-256 checksum How to use checksums |
3b92322a2a33897451e164d1d253d4637cb51feedcd4d402b87535c6b52ea7d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/3.4.8
|
Release files / django_djaken-2.0.2-py3-none-any.whl
| Download URL | django_djaken-2.0.2-py3-none-any.whl |
|---|---|
| Size | 2.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f43a86bfb17fc19c90b8314b080db2ca9a390689e23bb9cf196c8044ace83fa
|
|
BLAKE2b-256 checksum How to use checksums |
bbc922dd881727bdda61c57fc6744c3508ec9753ca8a4da15077fb9ff80d000c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/3.4.8
|
Security for django-djaken 2.0.2
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.
