Moon Registry for Alliance Auth
This is a Moon Registry app for Alliance Auth (AA)
Features
- Search all moons across Eve once imported, by (system, constellation, region), ore, sov. owner, rarity
- Add moon scans via parsed text
Installation
Before installing Moon Registry, install and configure django-eveonline-sde
(eve_sde) in Alliance Auth. Complete its migrations and run esde_load_sde
successfully. The SDE load must include regions, constellations, solar systems,
item types, type materials, planets, and moons. Follow the SDE package's setup
instructions, including its modeltranslation requirement.
In your Alliance Auth virtual environment, install Moon Registry in editable mode from a local checkout:
pip install -e {path_to}/aa_moonregistry
or via PyPi:
pip install aa_moonregistry
Add aa_moonregistry to INSTALLED_APPS in settings/local.py.
Apply Moon Registry's migrations. On upgrades, existing moon scans and cached prices keep their EVE type IDs.
python manage.py migrate
Load initial Eve sovereignty
python manage.py aa_moonregistry_load_sovereignty
Load Metenox-specific fuel data
python manage.py aa_moonregistry_load_metenox_data
Load initial JITA IV material pricing. Calculates average of top 5 JBV per type
python manage.py aa_moonregistry_load_jita_materials_prices
Next copy all the static data to the output folder
python manage.py collectstatic --noinput
Finally restart your AA setup.
Permissions
There is only one access level that will give access to the app in menu aa_moonregistry.basic_access
Alliance Auth Tasks
There are several registered tasks that should be run periodically.
aa_moonregistry.tasks.refresh_sovereignty - Reloads current Eve Sovereignty. Schedule once a week or so.
aa_moonregistry.tasks.refresh_material_prices - Refreshes pricing for calculations. Schedule once per day.
aa_moonregistry.tasks.refresh_metenox_data - Refreshes Metenox metadata. Schedule once per month.
Metadata
Release files for aa-moonregistry 0.2.0
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 | |
|---|---|---|---|---|
| aa_moonregistry-0.2.0.tar.gz | 25.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aa_moonregistry-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.4 kB
Release files / aa_moonregistry-0.2.0.tar.gz
| Download URL | aa_moonregistry-0.2.0.tar.gz |
|---|---|
| Size | 25.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b54bea53bdf7a3dd53b7cfa29b39a716e0361bb5dc880bf5a41080a636e198c1
|
|
BLAKE2b-256 checksum How to use checksums |
1fe606a510e854af41678da0bcf8239d295bbb9e6f06a92409718b59897c6a35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / aa_moonregistry-0.2.0-py3-none-any.whl
| Download URL | aa_moonregistry-0.2.0-py3-none-any.whl |
|---|---|
| Size | 34.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3464108bb63feef33dbdc888555c31e112a30c23238d88bb7fba4a911f83d4a
|
|
BLAKE2b-256 checksum How to use checksums |
328da570228495cc83a37594d5fa8fe71d7905ea131359cebb8cfa108d07867f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for aa-moonregistry 0.2.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.