SeAT - seat-5_1 - Page 1

SeAT is about to enter into a period of development denoted as SeAT 5.1 There are three main objectives of this period of development: 1. Burn down the remaining backlog of SeAT 5 issues on GitHub 2. Provide gated access (behind configuration variables) to experimental options developed within SeAT core 3. Provide a stepping stone for development of SeAT 6 The purpose of this channel will be to document the configuration required to opt in to experimental features and how plugin developers can prepare for v6 using those features.

Let's start with a first one: On the most recent eveapi versions, you can set CITADEL_ACCESS_CACHE to db in your .env to move the citadel access cache from redis to the database, meaning it is persistent across restarts of the docker stack. This might be interesting for people having issues with running into error limits from structures after restarting the containers. If anyone notices a performance hit from this feature, I'd appreciate it if you could tell us.