The cloud portal doesn't really need a database - it is only there to store session data and so that the integration with django.contrib.auth works.
It would be better for scaling etc. and simplicity of deployment if the requirement for a database was removed. This entails storing the Openstack token directly in a cookie instead of in the session and removing all django.contrib.auth integration with DRF.
The cloud portal doesn't really need a database - it is only there to store session data and so that the integration with
django.contrib.authworks.It would be better for scaling etc. and simplicity of deployment if the requirement for a database was removed. This entails storing the Openstack token directly in a cookie instead of in the session and removing all
django.contrib.authintegration with DRF.