Django model based search for Django CMS
The reason I created this was simply to avoid the overhead of using third party applications such as haystack. I was deploying an app on Amazons Elastic Beanstalk that will run on one or more instance and did not want the hassle of trying to save the index results in a centralized storage. I also did not want another instance just to act as a search endpoint like solr etc.
Doing it this way by saving the results in the database makes it extremely portable.
On publishing a page, an index item is added to the model. On unpublishing or deleting its removed.
Installation
Installation with pip:
$ pip install djangocms-site-search
Setup
Add the following apps to the INSTALLED_APPS ensuring its below cms:
INSTALLED_APPS = (
...
'cms',
'site_search',
)
Add the url routes to the project in urls.py:
urlpatterns = [
url(r'^', include('site_search.urls', 'search')),
]
Documentation
Please head over to our documentation for all the details on how to install and use the django CMS site search.
License
The project is licensed under the MIT license.
Metadata
Release files for djangocms-site-search 0.2.3
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 |
|---|---|---|---|---|
| djangocms-site-search-0.2.3.tar.gz | 11.6 kB | Without provenance | Details for djangocms-site-search-0.2.3.tar.gz |
Release files / djangocms-site-search-0.2.3.tar.gz
| Download URL | djangocms-site-search-0.2.3.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de0b2ca1e8d446845c533bfdba3fc67aa685ecc4b7970f43d591f04a77de64c6
|
|
BLAKE2b-256 checksum How to use checksums |
0f46ec213e1b3291252558391854f6a9a00b3e187b1efb138b2dc301b3f8db1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djangocms-site-search 0.2.3
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.