Alliance Auth AFAT — Another Fleet Activity Tracker
An Improved FAT/PAP System for Alliance Auth.
- Features and Highlights
- Screenshots
- Installation
- Updating
- Data Migration
- Settings
- Permissions
- Changelog
- Translation Status
- Contributing
- Credits
Features and Highlights
- Automatic tracking of participation on FAT links created via ESI
- Multiple ESI fleets (with your alts)
- Manually end ESI tracking per fleet
- Fleet type classification (can be added in the admin backend)
- Ship type overview per FAT link
- Graphical statistics views
- Re-open FAT link if the FAT link has expired and is within the defined grace time (only for clickable FAT links)
- Manually add pilots to clickable FAT links, in case they missed clicking the link (for a period of 24 hours after the FAT links original expiry time)
- Log for the following actions (Logs are kept for a certain time, 60 days per default):
- Create FAT link
- Change FAT link
- Remove FAT link
- Re-open FAT link
- Manually add pilot to FAT link
- Remove pilot from FAT link
- Smart filter for integration with Secure Groups
- FATs in time period
AFAT will work alongside the built-in native FAT System and ImicusFAT. However, data doesn't share, but you can migrate their data to AFAT, for more information, see below.
Screenshots
Dashboard
Fat Link List
Fat Link Details
Add Fat Link View for FCs
Smart Filter: FATs in Time Period
Installation
Bare Metal Installation
Step 1: Install the App
Make sure you're in the virtual environment (venv) of your Alliance Auth installation. Then install the latest version:
pip install allianceauth-afat==6.3.0
Step 2: Update Your AA Settings
Configure your AA settings in your local.py as follows:
-
Modify
INSTALLED_APPSto include the following entriesINSTALLED_APPS += [ # ... "eve_sde", # Only if not already added for another app "afat", # ... ] # This line right below the `INSTALLED_APPS` list, and only if not already added for another app INSTALLED_APPS = ["modeltranslation"] + INSTALLED_APPS
-
Add the Scheduled Tasks
# AFAT - https://github.com/ppfeufer/allianceauth-afat if "afat" in INSTALLED_APPS: CELERYBEAT_SCHEDULE["afat_update_esi_fatlinks"] = { "task": "afat.tasks.update_esi_fatlinks", "schedule": crontab(minute="*/1"), } CELERYBEAT_SCHEDULE["afat_logrotate"] = { "task": "afat.tasks.logrotate", "schedule": crontab(minute="0", hour="1"), } if "eve_sde" in INSTALLED_APPS: # Run at 12:00 each day CELERYBEAT_SCHEDULE["EVE SDE :: Check for SDE Updates"] = { "task": "eve_sde.tasks.check_for_sde_updates", "schedule": crontab(minute="0", hour="12"), } # Set the following when you have a bare metal installation, or Docker with a # non-standard storage for `myauth` ESDE_TASK_SPLIT = True
Step 3: Finalizing the Installation
Run migrations, copy static files and load EVE SDE data
python manage.py collectstatic
python manage.py migrate
python manage.py esde_load_sde
Docker Installation
Step 1: Add the App
Add the app to your conf/requirements.txt:
allianceauth-afat==6.3.0
Step 2: Update Your AA Settings
Configure your AA settings (conf/local.py) as follows:
-
Modify
INSTALLED_APPSto include the following entriesINSTALLED_APPS += [ # ... "eve_sde", # Only if not already added for another app "afat", # ... ] # This line right below the `INSTALLED_APPS` list, and only if not already added for another app INSTALLED_APPS = ["modeltranslation"] + INSTALLED_APPS
-
Add the Scheduled Tasks
# AFAT - https://github.com/ppfeufer/allianceauth-afat if "afat" in INSTALLED_APPS: CELERYBEAT_SCHEDULE["afat_update_esi_fatlinks"] = { "task": "afat.tasks.update_esi_fatlinks", "schedule": crontab(minute="*/1"), } CELERYBEAT_SCHEDULE["afat_logrotate"] = { "task": "afat.tasks.logrotate", "schedule": crontab(minute="0", hour="1"), } if "eve_sde" in INSTALLED_APPS: # Run at 12:00 each day CELERYBEAT_SCHEDULE["EVE SDE :: Check for SDE Updates"] = { "task": "eve_sde.tasks.check_for_sde_updates", "schedule": crontab(minute="0", hour="12"), } # Set the following when you have a bare metal installation, or Docker with a # non-standard storage for `myauth` ESDE_TASK_SPLIT = True
Step 3: Build Auth and Restart Your Containers
docker compose build --no-cache
docker compose --env-file=.env up -d
Step 4: Finalizing the Installation
Run migrations, copy static files and load EVE SDE data:
docker compose exec allianceauth_gunicorn bash
auth collectstatic
auth migrate
auth esde_load_sde
Updating
Bare Metal Installation
To update your existing installation of AFAT, first enable your virtual environment (venv) of your Alliance Auth installation.
pip install allianceauth-afat==6.3.0
python manage.py collectstatic
python manage.py migrate
redis-cli flushall
Finally, restart your supervisor services for AA
Docker Installation
To update your existing installation of AFAT, all you need to do is to update the
respective line in your conf/requirements.txt file to the latest version.
allianceauth-afat==6.3.0
Now rebuild your containers:
docker compose build
docker compose --env-file=.env up -d
After that, run the following commands to update your database and static files:
docker compose exec allianceauth_gunicorn bash
auth collectstatic
auth migrate
Common Steps
It is possible that some versions need some more changes. Always read the release notes to find out more.
Data Migration
Right after the initial installation and running migrations, you can import the data from Alliance Auth's native FAT system if you have used it until now.
Import From Native FAT
To import from the native FAT module, run the following:
Bare Metal Installation
python myauth/manage.py afat_import_from_allianceauth_fat
Docker Installation
docker compose exec allianceauth_gunicorn bash
auth afat_import_from_allianceauth_fat
Settings
To customize the module, the following settings can be managed in your admin backend:
| Setting | Description | Default Value |
|---|---|---|
| Use doctrines from fittings module | Whether to use the doctrines from the Fittings modules in the doctrine dropdown or from AFATs own doctrine list. (Note: The fittings module needs to be installed for this.) | No |
| Default FAT link expiry time | Default expiry time for clickable FAT links in Minutes | 60 |
| Default FAT link reopen grace time | Time in minutes a FAT link can be re-opened after it has expired | 60 |
| Default FAT link reopen duration | Time in minutes a FAT link is re-opened | 60 |
| Default log duration | Time in days before log entries are being removed from the DB | 60 |
Permissions
| Name | Description | Notes |
|---|---|---|
| basic_access | Can access the AFAT module | Your line member probably want this permission, so they can see the module and click the FAT links they are given. They also can see their own statistics with this permission. |
| manage_afat | Can manage the AFAT module | Your Military lead probably should get this permission |
| add_fatlink | Can create FAT Links | Your regular FC or who ever should be able to add FAT links should have this permission |
| stats_corporation_own | Can see own corporation statistics | |
| stats_corporation_other | Can see statistics of other corporations | |
| logs_view | Can view the modules logs |
Changelog
To keep track of all changes, please read the Changelog.
Translation Status
Do you want to help translate this app into your language or improve the existing translation? - Join our team of translators!
Contributing
You want to contribute to this project? That's cool!
Please make sure to read the contribution guidelines.
(I promise, it's not much, just some basics)
Credits
AFAT is maintained by @ppfeufer and is based on ImicusFAT by @exiom with @Aproia and @ppfeufer which is based on allianceauth-bfat by @colcrunch
Both of these modules are no longer maintained and are deprecated. Both modules will not run with the latest stable releases of Alliance Auth.
1 maintainer
Metadata
1 maintainer
Release files for allianceauth-afat 6.3.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 | |
|---|---|---|---|
| allianceauth_afat-6.3.0.tar.gz | 331.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| allianceauth_afat-6.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 763.9 kB
Release files / allianceauth_afat-6.3.0.tar.gz
| Download URL | allianceauth_afat-6.3.0.tar.gz |
|---|---|
| Size | 331.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5bcd6e1ad54339370a31c73deb04e6e43ee38122e5a8092dad9049d928b9936
|
|
BLAKE2b-256 checksum How to use checksums |
94f25d6c5aad171696c363040abb9367a1dbf64541f149f6cb8fab4e2293394c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / allianceauth_afat-6.3.0-py3-none-any.whl
| Download URL | allianceauth_afat-6.3.0-py3-none-any.whl |
|---|---|
| Size | 432.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9c85e910461bb9ea07ab327151fcf4914a7041f64c51735045c2e0864fe7b19
|
|
BLAKE2b-256 checksum How to use checksums |
87ce892977281013ee72c4c84ed14a7fac865ce4ac71b973e7385e1ce868913e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency log
