Standardized the addition of settings instructions.
Changed all references of local.py to a more generic 'auth project settings file'.
Included basic apache and nginx configs.
Include database creation steps.
Instruct users to restart gunicorn and celery after altering settings.
Include missing TS3 celerybeat schedule.
* Add pseudo foreign keys to EveCharacter model
* Ensure populate alliance is called on create
* Add unit tests for model
* Add extra signal for state removal/addition
* Add unit tests for signals
* Add tests for manager
* Add migrations
* Add sync command to admin control
* Prevent whitespace being stripped from group names
* Add documentation
Settings are self-documented in the new install template.
Services install docs should be updated to indicate settings need to be added and how to configure them.
Update celery tasks to new style & remove djcelery
Vanilla celery + django-celery-beat take over the role of djcelery. Task schedules are consolidated into settings instead of residing in code.
Update docs and example supervisor configs.
Add help text to State model
Remove navbar group headings
Fix registration email pluralization
Group memberships on state admin page
Attempt to prevent resetting of state if set on profile admin manually
Embed readthedocs on help page
Rename CorpStats API Index to Registration Index
Default corputils view to main character's corp if available
Correct Application characters listing
Correct string coercion of optimers
Improve readability of SRP values with intcomma
Beautify tables by embeding in panels
Replace slugify with py3-friendly python-slugify
* Add service access permissions and migration
`ENABLE_AUTH_<servicename> = True` will have the new permission applied
to the settings configured `DEFAULT_AUTH_GROUP` group or `Member` if
none is configured.
`ENABLE_BLUE_<servicename> = True` will have the new permission applied
to the settings configured `DEFAULT_BLUE_GROUP` group or `Blue` if none
is configured.
* Move views and hooks to permissions based access
* Remove access restriction to services view
Hypothetically non-member/blues could be granted permission to access
services manually as desired now. A user that has no permissions to
access any services will see a blank services list.
* Remove obsolete service settings
* Remove references to obsolete settings
* Adjusted tests to support permissions based access
* Fix incorrectly named permissions
* Add simple get_services generator function
* Added signals for user and groups perm changes
* Update validate_services to support permissions
deactivate_services removed as its surplus to requirements.
* Removed state parameter from validate_services calls
* Update tests to support signals changes
* Fix incorrect call to validate_services task
* Fix validate_services and test
* Add validate_user to changed user groups signal
* Added tests for new signals
* Remove unnecessary post_add signals
* Added documentation for service permissions
* Added detection for members with service active
If there are any service users in the Member or Blue groups active, then
the permission will be added to the respective Member or Blue group.
This means its no longer necessary to maintain the service enablesettings to migrate to permissions based service.
Remove obsolete state based status checking
* Added block for page_title as title fragment
* Add permissions auditing tool
* Added tests for permissions audit tool
* Added documentation for permissions tool
* Add permissions tool to coverage
Adarnof