The torque app
This is the django app that should be deployed in a running django server.
Outside of installing the app, this should remain a black box. The reason being that none of the routes or uses for this should be accessed except through the Torque MediaWiki plugin.
For developers, look in the individual code files for details on the inner workings.
See INSTALL.md for installation instructions.
Django Commands
torque ships commands
remove_unattached
Whenever loading up a new collection, there may be changes to the form of the data as the collection evolves. Because it may be uploaded in mistake, nothing is deleted from the database to ensure that no unintentional data loss occurs. However, admins may want to remove that data to reflect the upgrades in the data.
remove_unattached removes those items. Each field/document that gets uploaded will
be marked as attached. If there are edits associated with a field or document, then
the --forced argument is required.
run_cache_rebuilder
run_cache_rebuilder starts up the cache rebuilder. This is responsible for all
the cache regeneration, and split off to a separate application in order to ensure
that it doesn't affect the main process. It IS required to run, though, as it
does important database upkeep items as part of it's workflow.
If you want to run it as part of the application instead of separately, add
"torque.cache_rebuilder", as an INSTALLED_APP in your settings file, as
is exampled in test_settings.py and INSTALL.md
Removing attachment files
As a system runs, old FileField files can hang around on the hard drive. Those are usually uploaded attachments and templates. This can start to take up too much space. To remove, one was is to use https://github.com/akolpakov/django-unused-media:
$ pipenv install django-unused-media
Add 'django_unused_media' to your INSTALLED_APPS and then run:
$ pipenv run python ./manage.py cleanup_unused_media
1 maintainer
Metadata
1 maintainer
Release files for django-torque 0.9.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 | |
|---|---|---|---|
| django_torque-0.9.1.tar.gz | 48.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_torque-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 116.8 kB
Release files / django_torque-0.9.1.tar.gz
| Download URL | django_torque-0.9.1.tar.gz |
|---|---|
| Size | 48.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0c2b829e79dd49f808d6780986c58543e941a656b7fdff3c61527d6bd67564b
|
|
BLAKE2b-256 checksum How to use checksums |
8db074d9a9dbdfe10891bf4d223d323a3185b0da083719dfb64b3acd0e4eac1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / django_torque-0.9.1-py3-none-any.whl
| Download URL | django_torque-0.9.1-py3-none-any.whl |
|---|---|
| Size | 68.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7033961be5444b140031a48ef085815ab84df42220f2a22876c161cf90366baa
|
|
BLAKE2b-256 checksum How to use checksums |
57477a54b661ac859f6ee5d24476ae8f2c1dc8f4ff635e0032f4a5d6b88ce4eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
