What's New

This release brings about a new group management system and support for the EVE Swagger Interface, brings Fleet Activity Tracking back to a functional state, and adds new functionality to Corp Management. Multiple corps and alliances can now be simultaneously considered members. As well, the dashboard has been upgraded to replace the API Key Management and Characters pages.

Upgrading

Pre-Upgrade Procedures

Complete these before updating the codebase or settings.py

Installing Redis

Auth now defaults to using redis server instead of rabbitmq for task queueing and caching. Ensure you have it installed and running on your server.

For Ubuntu:

sudo apt-get install redis-server

For CentOS:

sudo yum install redis
sudo systemctl enable redis.service
sudo systemctl start redis.service

Switch SSO Providers

Because we are switching to a new SSO package, it's a good idea to remove the old one to prevent foreign key issue later on. Before starting the upgrade, clear its database entries:

python manage.py migrate eve_sso zero

It is now safe to update the codebase and create the new settings file.

Upgrade Process

Get the new code (git checkout v1.14) and update your settings file.

Configuring SSO

SSO is now required. Please visit the EVE Developers Site and create an application. Ensure that the callback url is set to mydomain.com/sso/callback. For FAT and Corp Stats, scopes are required, so select Authenticated API Access. For people with existing SSO applications, these will need to update their scopes. It's easiest to just select every scope beginning with esi, however at this time the only scopes needed are:

• esi-location.read_location.v1
• esi-location.read_ship_type.v1
• esi-universe.read_structures.v1
• esi-corporation.read_membership.v1

As more SSO features are added, more scopes may be needed, so do yourself a favour and select all these now. When authenticating by SSO, only the scopes required for the feature are requested, so there's no reason not to add these now.

Configuring Tenants and Blues

With this release, multiple corps and alliances can be viewed as 'members' in auth. The settings CORP_IDS and ALLIANCE_IDS are a comma-delimited list of member IDs of corps and alliances respectively. Strings and integers are both accepted.

Blues still functions the same, however you can now specify whether to consider standings at the corporate or alliance level from the API key entered.

Now proceed with the upgrade script: bash update.sh

Customizing

Site Appearance

Because there is no longer a single 'owning' entity, the corp/alliance logo is missing from the index page. A placeholder alliance logo is included. To display your own logo on the index page, place the image at customization/static/img/index_images/logo.png, creating subdirectories as needed.

Once the logo has been added, go ahead and collect the new static files:

python manage.py collectstatic

The text in the top-left corner of auth (used to be corp or alliance name) is available to customize - change the SITE_NAME setting.

Selecting EVE Datasources

With the inclusion of the EVE Swagger Interface ('ESI'), there are two routes for getting character, corp, and alliance data: the legacy XML API, and the new ESI. Each has its own advantages:

• ESI has faster queries for alliance data
• XML has a caching mechanism, reducing call times for repetitive data

By default settings are to grab everything from the shiny new ESI. It is not recommended to change this setting for alliance information. However query time might improve by switching character to XML (it takes 2 queries to build a character via ESI versus 1 with XML). In the long run, XML will go away, so it is suggested to stay with ESI.

Settings to alter here are:

• EVEONLINE_CHARACTER_PROVIDER
• EVEONLINE_CORP_PROVIDER
• EVEONLINE_ALLIANCE_PROVIDER