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.

@here With the latest eveapi update I have snuck in a quick testing bit of code for CCP. It makes no change to how SeAT will function for you, but will help CCP gather some data on internal tooling of their own. It only affects the skills endpoints. This test will conclude very shortly (current target end 6/1/26). Please consider opting in by adding CCP_SKILLS_CACHE_TEST=true to you .env file and restarting your instance. You can opt out again by removing this line (or setting to false), or it will automatically end when the trial concludes Happy New Year!