Skip to main content

Assets module for AllianceAuth.

pre-commit.ci status Code style: black Tests codecov

ko-fi

Assets System with Ordering Feature

-

Features

  • Asset System for Character & Corporation
  • Ordering System

Upcoming

  • Performance Updates
  • More Filter
  • Notifications
  • Status Updates

Installation

[!NOTE] AA Assets needs at least Alliance Auth v4.0.0 Please make sure to update your Alliance Auth before you install this APP

Step 1 - Install the Package

Make sure you're in your virtual environment (venv) of your Alliance Auth then install the pakage.

pip install aa-assets

Step 2 - Configure Alliance Auth

Configure your Alliance Auth settings (local.py) as follows:

  • Add 'eveuniverse', to INSTALLED_APPS
  • Add 'assets', to INSTALLED_APPS

Step 3 - Add the Scheduled Tasks

To set up the Scheduled Tasks add following code to your local.py

CELERYBEAT_SCHEDULE["assets_update_all_assets"] = {
    "task": "assets.tasks.update_all_assets",
    "schedule": crontab(minute=0, hour="*/1"),
}
CELERYBEAT_SCHEDULE["assets_update_all_locations"] = {
    "task": "assets.tasks.update_all_locations",
    "schedule": crontab(minute=0, hour="*/12"),
}
CELERYBEAT_SCHEDULE["assets_update_all_parent_locations"] = {
    "task": "assets.tasks.update_all_parent_locations",
    "schedule": crontab(minute=0, hour=0, day_of_week=0),
}

Step 4 - Migration to AA

python manage.py collectstatic
python manage.py migrate

Step 5 - Setting up Permissions

With the Following IDs you can set up the permissions for the Assets

ID Description
basic_access Can access the Assets module All Members with the Permission can access the Assets.
add_personal_owner Can add personal owners
add_corporate_owner Can add corporate owners
manage_requests Can manage requests Get Notifications & Manage Requests

Step 6 - (Optional) Setting up Compatibilies

The Following Settings can be setting up in the local.py

  • ASSETS_APP_NAME: "YOURNAME" - Set the name of the APP

  • ASSETS_LOGGER_USE: True / False - Set to use own Logger File

If you set up ASSETS_LOGGER_USE to True you need to add the following code below:

LOGGING_ASSETS = {
    "handlers": {
        "assets_file": {
            "level": "INFO",
            "class": "logging.handlers.RotatingFileHandler",
            "filename": os.path.join(BASE_DIR, "log/assets.log"),
            "formatter": "verbose",
            "maxBytes": 1024 * 1024 * 5,
            "backupCount": 5,
        },
    },
    "loggers": {
        "assets": {
            "handlers": ["assets_file", "console"],
            "level": "INFO",
        },
    },
}
LOGGING["handlers"].update(LOGGING_ASSETS["handlers"])
LOGGING["loggers"].update(LOGGING_ASSETS["loggers"])

Highlights

[!NOTE] Contributing You want to improve the project? Just Make a Pull Request with the Guidelines. We Using pre-commit

Metadata

Release files for aa-assets 0.1.2

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

Source distribution (sdist)

Source distribution for aa-assets 0.1.2
File Size Uploaded Provenance
aa_assets-0.1.2.tar.gz 58.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for aa-assets 0.1.2
File Interpreter ABI Platform
aa_assets-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 128.8 kB

Release files / aa_assets-0.1.2.tar.gz

Download URL aa_assets-0.1.2.tar.gz
Size 58.4 kB
Tags Source
SHA-256 checksum
How to use checksums
eca558bb36e1c86baea9b71efda1ab38e86cf6a25eb8de3d3ef4e65798481570
BLAKE2b-256 checksum
How to use checksums
4e0ef9dec2e3c0689d1270b4d0560497324fae3842e837532c511aeda97df4ea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.3

Release files / aa_assets-0.1.2-py3-none-any.whl

Download URL aa_assets-0.1.2-py3-none-any.whl
Size 70.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
31bf5f468e4e48f00cdabf4a24d98c934550c7063319bd0767e29c43c7736441
BLAKE2b-256 checksum
How to use checksums
a18a638e7d27e63879aa9b329e83521ac804db4d6cdc0d7b084a44f621524d2f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.3

Security for aa-assets 0.1.2

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.

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files No provenance

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