Weekly release for May

Features

• Fetching access token for plio-analytics through Auth0
• Pagination support for the list of all plios
• Support for searching a given query in the list of all plios
• New endpoint for downloading the CSV dump for a plio

Bugs

• #155 the defaults for when no organization header is passed was inconsistent with empty organization header

Deletions

• Removed the endpoint for returning the number of unique users per plio

v0.1.1 - Weekly release for May

Features

• support for websockets to trigger events from the server to the frontend
• auto-refreshing auth tokens and logging users out when refresh token expires
• updates the badges in the README for staging and production deployment

Miscellaneous

• All the plios have been ported from S3 to the new DB

v0.1

This is the first minor version release for the Plio backend 🎉. This release involves:

1. New database structure in place.
2. Multi-tenant application architecture with single-tenant multiple-schema database.
3. REST API fully functional with Redoc docs
4. Dockerization of the project and installation steps updated
5. AWS ECS Continuous Deployment and deployment steps updated
6. Full-fledged authentication
   1. OTP based authentication using AWS SNS
   2. Google account based authentication
7. Flake8 added to pre-commit checks
8. Removed Zappa settings and using .env based environment variables handling
9. Functionalities for users to list, create, view and edit plios.

v0.0.3

This pre-release contains:

1. zappa_settings.example.json file added to help set up new environments
2. Updates to various markdown files for better installation, deployment and best practices support

v0.0.2

This pre-release contains:

1. Removed hardcoding for frontend URL and added to settings.py
2. Fixed bug with fetching questions when not in CMS
3. Cleanups in env variables
4. Fixes for question ordering

v0.0.1

This is the first patch release for Plio-backend.

Changes include:

1. Readme cleanups and better installation & deployment guides.
2. Requirements.txt is up to date
3. Pre-commit feature added
4. Question structure updated - changed terminology to items

Elastic Beanstalk -- working config (autodeploy)

Tagging to come back to just in case we want to move back to EB on ALC AWS