An auth system for EVE Online to help in-game organizations manage online service access.
Fixes swagger specs again.
view_something_corpstats permissionsThe timerboard JS has been edited. Recollect static files with python manage.py collectstatic -c
pip install -U allianceauth then restart gunicon/celery.
With the XML API being turned off in just over two weeks time I figure it's appropriate to release v2. This version reinvents the character management system to use ESI with SSO tokens.
Character ownership is now tracked via refreshable SSO tokens. API keys are gone. All use of the XML API has been replaced by ESI. Customizable username formatting for services. Modular membership state system. Alliance Auth is a python package now. And a ton of bug fixes. I didn't count, but it's a lot.
Before upgrading please make a backup of your database. The process should be painless but things can go wrong.
If you're using v1 you can update to v2 by following this guide. Note that you need to be on v1.15 or newer for this process to work.
New installs: see the new install docs.
If you were part of the beta program you will need to re-create your auth project folder and copy your settings file over. If your database is in sqlite3 and you want to port it to mysql see this script.
If you run into any trouble join us on gitter and our many community members can help you out.
We've been in beta for a couple months and have had tons of feedback and support debugging some particularly odd issues. I tried to gave mention of people helping debug specific issues in commit messages.
Special thanks to @ghoti , @mmolitor87 and @TargetZ3R0 for all their hard work debugging.
Thanks to everyone who participated!
Nothing special. Pull new code, restart apache/nginx/gunicorn/celery/supervisor.
This is the third and hopefully last beta of v2. It might even work this time.
publicData
If you have an existing install your auth project needs editing. Alter myauth/celery.py and remove namespace='CELERY' from the app declaration. Then update base settings with allianceauth update myauth.
Or start a new project, copy your settings file over, and pretend nothing happened. That works too.
Be sure to migrate after installing b3.
Either install from github or wait for it to get published on pypi.
If you're installing for the first time refer to the docs.
The goal of the beta is to iron out any issues we've missed. Please reach out to us on gitter or open an issue here (being sure to mention it's regarding v2.0b3).
Thanks to everyone who reported issues during betas 1 and 2.
The old API endpoint for adding users to Discord is going away on March 23rd. Please update before then.
The DISCORD_INVITE_CODE setting is no longer required. Feel free to delete the invite on your Discord server.
The bot now requires the Create instant invite permission. Ensure it has it on your Discord server.
Get the new code and restart celery.
git fetch --all
git checkout v1.15.7
(whatever commands you use to restart celery and/or gunicorn/apache)
INSTALLED_APPS setting to local settings template.To install v2 a slight modification to the docs is necessary. The auth package hasn't yet been published on pypi, so instead of pip install allianceauth you'll need to pip install git+https://github.com/allianceauth/[email protected]
If you're coming from v1.15, read the b1 release notes.
If you're coming from v2.0b1, run python manage.py migrate eve_autogroups zero before upgrading. After upgrading run migrations again (python manage.py migrate).
Change BROKER_URL in settings/base.py to CELERY_BROKER_URL.
Add from .celery import app as celery_app to your project_template/project_name/__init__.py file (or reinitialise your project).
Restart your wsgi server and celery as usual.
The goal of the beta is to iron out any issues we've missed. Please reach out to us on gitter or open an issue here (being sure to mention it's regarding v2.0b2).
Thanks to everyone who reported issues during beta 1.
This is the first public beta of Alliance Auth v2. It's a big change.
Because CCP is depreciating API keys soon:tm: the goal of v2 is to replace them with SSO tokens. That meant the logic attaching characters to user accounts required an overhaul.
User registration has been revamped. Users now register using SSO. Usernames and passwords are no longer accepted. Emails are validated.
Deployment has changed significantly. Instead of cloning the source from github and running directly, auth is now installed like a standard python package and used to create custom django projects.
Python2 is dead. Auth only works with Python3.4 or newer.
Django 2.0 was released and is supported.
There are a ton of smaller changes I don't feel like mentioning here. All changes are listed in the v2 project.
Documentation has been updated and is available on readthedocs.
To install v2 a slight modification to the docs is necessary. The auth package hasn't yet been published on pypi, so instead of pip install allianceauth you'll need to pip install git+https://github.com/allianceauth/[email protected]
Before proceeding ensure you're on v1.15 or newer.
There's no way to upgrade your code from v1 to v2 because of the new deployment method. However your database can be migrated to v2 automatically. Follow the install instructions for deploying v2 and when defining the database in your project's settings file, point at a copy of your old v1 database to migrate it.
The goal of the beta is to iron out any issues we've missed. Please reach out to us on gitter or open an issue here (being sure to mention it's regarding v2.0b1).