AA Time Zones
App for displaying different time zones with Alliance Auth
- Installation
- (Optional) Public Views
- Updating
- Configure the Timezone Panels
- Adjusting Time
- Discord Bot Command
- Changelog
- Translation Status
- Contributing
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 aa-timezones==3.2.2
Step 2: Update Your Alliance Auth Settings
Configure your AA settings (local.py) as follows:
- Add
'timezones',toINSTALLED_APPS
Step 3: Finalizing the Installation
Run migrations & copy static files
python manage.py collectstatic
python manage.py migrate
Restart your supervisor services for AA
Once done, it's time to add all the time zone information, so you can define your own set of panels later. To do so, simply run:
python manage.py timezones_load_tz_data
(Optional) Public Views
This app supports AA's feature of public views, since time zones conversion is not
any mission-critical information. To allow users to view the time zone conversion page
without the need to log in, please add "timezones", to the list of
APPS_WITH_PUBLIC_VIEWS in your local.py:
# By default, apps are prevented from having public views for security reasons.
# To allow specific apps to have public views, add them to APPS_WITH_PUBLIC_VIEWS
# » The format is the same as in INSTALLED_APPS
# » The app developer must also explicitly allow public views for their app
APPS_WITH_PUBLIC_VIEWS = [
"timezones", # https://github.com/ppfeufer/aa-timezones
]
Note
If you don't have a list for
APPS_WITH_PUBLIC_VIEWSyet, then add the whole block from here. This feature has been added in Alliance Auth v3.6.0 so you might not yet have this list in yourlocal.py.
Updating
To update your existing installation of AA Time Zones, first enable your virtual environment.
Then run the following commands from your AA project directory (the one that
contains manage.py).
pip install aa-timezones==3.2.2
python manage.py collectstatic
python manage.py migrate
Now restart your AA supervisor services.
Configure the Timezone Panels
Per default, there are 10 additional time zone panels that are displayed (see first image). If you want to change those, you can create your own set of panels in your admin backend.
NOTE: "Local time" and "EVE time" will always be displayed as the first two panels, no matter what.
Adjusting Time
You can easily adjust the time that is displayed for all timezones. This is useful for reinforcement timers or pre-planned fleets. To do so, click on the "Adjust Time" button below the time zone panels, and you will see 2 different ways to set a new time.
The first one is meant for timers, like reinforcement timers, anchoring timers or the like. Its maximum is 7 days, 59 minutes and 59 seconds into the future. That should cover pretty much all timers you can find in Eve Online.
The second one is best suited for pre-planned fleets. Here you can set a fixed date and time based on the selected time zone. The default selected time zone is "EVE time" but you can change it to all the available options. Keep in mind the selected time zone is the one the time and date will be adjusted to. So if you are going to use it to plan fleets, it is recommended to keep this set to "EVE time".
To set the adjusted time, simply click on "Set Time" in the row you altered. This will then adjust all time zone panels to the time you selected and will also alter the link in your browser, so you can share it with others directly.
Discord Bot Command
For this to work, you'll need to have allianceauth-discordbot installed, configured
and running. (See this link)
| Command | Effect |
|---|---|
/time |
Displays the current EVE time and what time it is in the configured time zones |
Changelog
See CHANGELOG.md
Translation Status
Do you want to help translate this app into your language or improve the existing translation? - Join our team of translators!
Contributing
Do 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)
1 maintainer
Metadata
1 maintainer
Release files for aa-timezones 3.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aa_timezones-3.2.2.tar.gz | 526.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aa_timezones-3.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / aa_timezones-3.2.2.tar.gz
| Download URL | aa_timezones-3.2.2.tar.gz |
|---|---|
| Size | 526.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4450e06db49efb6c8a9110c1b9854da46f6c2fda92b4384b940d318b036d7508
|
|
BLAKE2b-256 checksum How to use checksums |
1c21b02241b0ca895ee4d1f0819966def6a5ada501d5dd4b71bed57bc3f0a0ed
|
| 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 6, 2026.
Transparency logRelease files / aa_timezones-3.2.2-py3-none-any.whl
| Download URL | aa_timezones-3.2.2-py3-none-any.whl |
|---|---|
| Size | 726.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f004590eb6a87713d681b80b1440054e1796231fb3ec3141fb54034580f9c46d
|
|
BLAKE2b-256 checksum How to use checksums |
9e64d8757df124a49646ee82044c7685d691c125588a1cdbb9b88bca8b2cbbcf
|
| 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 6, 2026.
Transparency log
