Skip to main content

# Houston Houston is drop-in-place analytics software for Django projects that stores 100% of usage data in-house. At no point is data sent to third parties.

There are a number of projects in the Django ecosystem that facilitate integration with third party analytics software but most of these entail sending client usage to a third party, most likely Google. This is an acceptable strategy in some cases, Google Analytics is a great product that’s easy to integrate with. But if you’re developing software where your users might be hesitant to report their every page view to a third party, especially one with a history of illegally disclosing said data, you might want to consider keeping your users’ usage data on servers you control.

## Usage - Add django-houston as a dependency in your requirements.txt file - Add Houston to your INSTALLED_APPS setting - Include the Houston urls at some path in your urls.py file: url(r’^houston/’, include(‘Houston.urls’)) - Include the tracking fragment on any pages where views should be tracked: {% include “Houston/tracking.html” %}

It’s recommended to include the tracking fragment near the end of the document after any page critical scripts to minimize user impact of tracking, although you can include it anywhere.

Metadata

Release files for django-houston 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-houston 0.3.0
File Size Uploaded Provenance Actions
django-houston-0.3.0.tar.gz 131.9 kB Without provenance Details for django-houston-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-houston 0.3.0
File Interpreter ABI Platform Actions
django_houston-0.3.0-py3-none-any.whl Python 3 none any Details for django_houston-0.3.0-py3-none-any.whl

Total release size: 270.7 kB

Release files / django-houston-0.3.0.tar.gz

Download URL django-houston-0.3.0.tar.gz
Size 131.9 kB
Tags Source
SHA-256 checksum
How to use checksums
bddeb877ac5bb241779e33be6dcbe713759f7df7ed8e59813973490921f8df3a
BLAKE2b-256 checksum
How to use checksums
ae9c6dc8384777c9b21f6a58eb94134c5b62647d305f20f1f0d0a8cf8ad1351a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.3

Release files / django_houston-0.3.0-py3-none-any.whl

Download URL django_houston-0.3.0-py3-none-any.whl
Size 138.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c4d003ffd42178fef557fd639d4189af87acefcfd290e9d2bda21c49df8cc371
BLAKE2b-256 checksum
How to use checksums
58fd8f493ae3074088d241adf4429d9d8a7952f20a3944aa2bcb5618e1c3dd72
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.6.0 requests-toolbelt/0.9.1 tqdm/4.38.0 CPython/3.7.3

Security for django-houston 0.3.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page