Catalog PyPI
PACKAGE EXPLORERView in registry

aa-buybacks

PyPI

Buyback program management app for Alliance Auth

Versions collected1
Direct dependencies6From release 0.1.6
Last observed20 Oct, 16:49 UTC

README

Version 0.1.6 documentation

Buybacks for Alliance Auth

This is a buyback program management app for Alliance Auth (AA).

License python django

Contents

  1. Key Features
  2. Installation
    1. Install app
    2. Update Eve Online app
    3. Configure AA settings
    4. Finalize installation into AA
    5. Data import
    6. Setup permissions
    7. Setup corp
    8. Define programs
    9. Calculating
  3. Updating
  4. Tips & Tricks
  5. TODO

Overview

This app helps running buyback programs for an alliance or corporation.

Key Features

It offers the following main features:

  • Manage corporation buyback programs
  • Calculate value of the items that will be sent to the buyback program
  • Store statistics on the usage of buyback programs

Installation

Install app

Install into your Alliance Auth virtual environment from PyPI:

pip install aa-buybacks

Update Eve Online app

Update the Eve Online app used for authentication in your AA installation to include the following scopes:

esi-universe.read_structures.v1
esi-contracts.read_corporation_contracts.v1
esi-assets.read_corporation_assets.v1

Configure AA settings

Configure your AA settings (local.py) as follows:

  • Add 'eveuniverse' and 'buybacks' to INSTALLED_APPS

  • Add these lines to bottom of your settings file:

    # settings for buybacks
    CELERYBEAT_SCHEDULE['buybacks_update_all_offices'] = {
        'task': 'buybacks.tasks.update_all_offices',
        'schedule': crontab(minute=0, hour='*/12'),
    }
    CELERYBEAT_SCHEDULE['buybacks_sync_all_contracts'] = {
        'task': 'buybacks.tasks.sync_all_contracts',
        'schedule': crontab(minute=0, hour='*'),
    }
    

Finalize installation into AA

Run migrations & copy static files

python manage.py migrate
python manage.py collectstatic

Restart your supervisor services for AA

Data import

Load EVE Online type data from ESI:

python manage.py buybacks_load_types

Setup permissions

Now you can access Alliance Auth and setup permissions for your users. This is an overview of all permissions used by this app:

NamePurposeCode
Can access this app and view buyback programsEnabling the app for a user. This permission should be enabled for everyone who is allowed to use the app (e.g. Member state)basic_access
Can setup corporationAdd or updates the character for syncing offices and contracts. This should be limited to users with admins / leadership privileges.setup_retriever
Can manage buyback programsUser with this permission can manage the buyback programs and notificationsmanage_programs

Setup corp

Finally you need to set a corporation with the character that will be used for fetching the corporation offices, contracts and related structures. Just click on Setup Corp and add the requested token.

Note that only users with the appropriate permission will be able to see and use this button.

Note that the respective character needs to be a director for the corporation.

Define programs

Let's say your corp has an ORE buyback program and you want to use this tool for that. First, you need to click on Create Program and fill the name of the program.

Note that only users with the appropriate permission will be able to see and use this button.

Once it is created, you should be able to add all the locations (where your corp has an office) denoting the structures or stations to create the contracts for. You might only accept the ores in certain corp refineries and don't want people to send it other structures.

You should also be able to add all the items and the percentage the corp skims on top of the price. For example, for your ORE buyback program, add Plagioclase with brokerage set at 20%.

That's it. The buybacks program is fully created and ready to be used.

Calculating

Any character can use one of the buyback programs by clicking on Use button on one of the program. Once done, they need to select the location and can copy-paste the items they want to send to the corp. When they click on Calculate, the app calculates the exact amount based on the prices defined in the program and shows them that total value.

Once they see the total value, they would need to send an in-game contract for the exact amount and then click on Notify to notify the app about it.

Once the corp accepts a contract, our contracts sync feature would automatically match the corresponding notification (based on the total price, items with quantities and the location of the contract) and store it in the statistics.

Updating

To update your existing installation of Buybacks first enable your virtual environment.

Then run the following commands from your AA project directory (the one that contains manage.py).

pip install -U aa-buybacks
python manage.py migrate
python manage.py collectstatic
python manage.py buybacks_load_types

Finally restart your AA supervisor services.

Tips & Tricks

  • If you want to edit the brokerage of an item in a program, you can just add the item with the new brokerage and it will update the existing one.

TODO

  • Use refined value to calculate OREs
  • Set refining percentage per item
  • Statistics filtering

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 1

Collected releases
VersionPublishedDirect dependenciesOpen version
0.1.62 Apr 20256

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

ACCESSIBLE
pksunkara/aa-buybacks

Shared repository data · GitLab

License detected in repository
MIT License
License branch / ref
master
Contributor identities
5 · complete API traversal
License file
Contributors · showing 5 of 5 collected
ContributorContributions
Pavan Kumar Sunkara25
Peter Pfeufer3
Ikarus Cesaille3
Rebecca Claire Murphy2
jsv0ice1

Default-branch author identities; GitLab commit counts exclude merge commits.

Public sponsor counts have not been collected. These signals belong to the repository owner.

Downloads & popularity

5identities
Gauge · observed snapshots23 Oct 2026
52.50
2026-10-20: 5 · observed 2026-10-20T17:23:37.9473464Z2026-10-21: 5 · observed 2026-10-21T17:23:57.0596355Z2026-10-22: 5 · observed 2026-10-22T17:24:22.9423571Z2026-10-23: 5 · observed 2026-10-23T17:24:49.0684649Z
20 Oct23 Oct

gitlab · 4 observations shown. Missing days are unknown.

View observed values
Date / source periodValueObserved at
2026-10-2352026-10-23T17:24:49.0684649Z
2026-10-2252026-10-22T17:24:22.9423571Z
2026-10-2152026-10-21T17:23:57.0596355Z
2026-10-2052026-10-20T17:23:37.9473464Z

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 16:49 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:f4e50bfa755838eb12de724f3dd778038cb75d8322ee0bf1b5f3b1a779d9cab2