Django Markdown Blog
=====
Django Markdown Blog is a simple Django app that will give any Django project a blog that works with markdown.
Detailed documentation is in the "docs" directory.
Quick start
-----------
1. Add "polls" to your INSTALLED_APPS setting like this::
INSTALLED_APPS = [
...
'polls',
]
2. Include the polls URLconf in your project urls.py like this::
url(r'^blog/', include('markdown_blog.urls')),
3. Run `python manage.py migrate` to create the blog models.
4. Start the development server and visit http://localhost:8000/admin/
to create your first blog post (you'll need the Admin app enabled).
5. Visit http://localhost:8000/polls/ to view your latest blog posts.
Metadata
Release files for django-markdown-blog 0.1
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-markdown-blog-0.1.tar.gz | 3.8 kB | Without provenance | Details for django-markdown-blog-0.1.tar.gz |
Release files / django-markdown-blog-0.1.tar.gz
| Download URL | django-markdown-blog-0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6fd68bb8e5bc8b4dde0d1a463c456d5f20265cf35da6c4a0dfabda1f12dcddf
|
|
BLAKE2b-256 checksum How to use checksums |
3fadb25198215e0b7287a26d9e98821a7fa5fa10725aaeccdd67ba0e6310de35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-markdown-blog 0.1
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.