This release is a pre-release and may not be stable for production use.
Alliance Auth - Hunting Tools
We are hunting Rabbits.
Features
- Display active targets
- Last known Locate and Past Locates for a given target
- Manage target Alts and their capability
- Note taking on given targets
Planned Features
- Manage Locator Agent Expiries
- Request a Locate from available users
- Generate potential targets from kill activity
Installation
Step 1 - Install from pip
pip install aa-hunting
Step 3 - Configure Auth settings
Configure your Auth settings (local.py) as follows:
- Add
'hunting'toINSTALLED_APPS - Add below lines to your settings file:
## Settings for AA-Hunting
# Notifications (Locator Agent Results)
CELERYBEAT_SCHEDULE['hunting_pull_notifications'] = {
'task': 'hunting.tasks.pull_notifications',
'schedule': crontab(minute='0', hour='*'),
'apply_offset': True,
}
CELERYBEAT_SCHEDULE['hunting_import_notifications_apps'] = {
'task': 'hunting.tasks.import_notifications_apps',
'schedule': crontab(minute='30', hour='*'),
'apply_offset': True,
}
# Dont hit squizz too hard, im not shipping the agent file incase it updates
CELERYBEAT_SCHEDULE['hunting_import_agents_squizz'] = {
'task': 'hunting.tasks.import_agents_squizz',
'schedule': crontab(minute='0', hour='0', day_of_week='0'),
}
Step 3 - Maintain Alliance Auth
- Run migrations
python manage.py migrate - Gather your staticfiles
python manage.py collectstatic - Restart your project
supervisorctl restart myauth:
Permissions
| Perm | Admin Site | Perm | Description |
|---|---|---|---|
| basic_access | nill | Can access the Hunting App | Can access the Hunting App |
| target_add | nill | Can add a Hunting target | Can add a Hunting target |
| target_edit | nill | Can edit a Hunting target | Can edit a Target, Add Alts, Modify Ship Type |
| target_archive | nill | Can archive a Hunting target | Can |
| alt_add | nill | ||
| alt_edit | nill | ||
| alt_remove | nill | ||
| locator_addtoken | nill | ||
| locator_request | nill | ||
| locator_action | nill |
Settings
| Name | Description | Default |
|---|---|---|
HUNTING_ENABLE_CORPTOOLS_IMPORT |
Enable (if Installed) LocateCharMsg's to be pulled from Corp-Tools, for historical information | True |
Contributing
Make sure you have signed the License Agreement by logging in at https://developers.eveonline.com before submitting any pull requests. All bug fixes or features must not include extra superfluous formatting changes.
Metadata
Release files for aa-hunting 0.2.1a0
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 |
|---|---|---|---|---|
| aa_hunting-0.2.1a0.tar.gz | 22.3 kB | Without provenance | Details for aa_hunting-0.2.1a0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aa_hunting-0.2.1a0-py3-none-any.whl | Python 3 | none | any | Details for aa_hunting-0.2.1a0-py3-none-any.whl |
Total release size: 67.6 kB
Release files / aa_hunting-0.2.1a0.tar.gz
| Download URL | aa_hunting-0.2.1a0.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4a3185a1ade814455098ee3f17038aeae1a433fc84e57f69027de0437b49418
|
|
BLAKE2b-256 checksum How to use checksums |
d680f012b83057ad602e05f484ab67bb7cd5a73a246dc560a9e983137ac86ac9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / aa_hunting-0.2.1a0-py3-none-any.whl
| Download URL | aa_hunting-0.2.1a0-py3-none-any.whl |
|---|---|
| Size | 45.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b67dacb4aedd8af1f1146a26f154060d45af443806b960dfab9962dab38cb1f9
|
|
BLAKE2b-256 checksum How to use checksums |
ab5260562235e391f2aed58036ea80a738f70705045f8681c632e7ba4d99be38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for aa-hunting 0.2.1a0
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.