Robert Schuh
Robert Schuh
Just changed the versions like in previous commits, I can try it in a few minutes
@schickling http://138.201.40.82:12345/ ```docker run -d -p 12345:80 -e API_URL="https://esi.tech.ccp.is/latest/swagger.json" -e OAUTH_CLIENT_ID="3a7d1f1207a04b32b7d27feca20748f2" -e OAUTH_REALM="ESI" -e OAUTH_APP_NAME="ESI Swagger UI (self-hosted)" swaggerui``` - [ ] doesnt use the client id - [ ]...
@elberth90 im on vacation and haven't looked further into how to fix the issues I listed, maybe someone can take a quick look? Shouldn't be much effort :3
Waiting for this aswell :)
it would also be nice to just be able to work with jwts that dont have a specific jid field. this would allow for using existing tokens from something like...
``` '/characters/{character_id}/calendar/': post: description: >- Create a new calendar event parameters: - description: Data used to create the event in: body name: calendar_event required: true schema: properties: title: description: The...
``` '/accesslists/': get: description: >- List all accesslists a character has higher roles MANAGER or ADMIN on responses: '200': description: List of Accesslist IDs examples: application/json: - 1234567 - 8765423...
do you want me to write them already or is read only enough for now? if you want to implement it in one load i will take the time to...
sorry for this taking so much time, havent found any time lately. just updated the initial post to add the remaining (?) routes, working on adding the swagger definitions now