Plio Backend

This repository is responsible for managing plio data, API support and database handling.

Installation

To set up this project, visit the installation steps.

Postgres 14 upgrade note

This branch moves the local database image from postgres:11 to postgres:14-alpine. Postgres cannot open a data directory created by an older major version, so docker-compose now uses a fresh postgres14_data volume; your previous postgres_data volume is left untouched. Local dev data is normally disposable (re-run migrations and the seed commands). If you need the old data, dump it before upgrading:

docker compose run --rm -v plio-backend_postgres_data:/old postgres:11 \
  bash -c "pg_dumpall -h db -U postgres" > backup.sql
# then, after `docker compose up` on this branch:
cat backup.sql | docker compose exec -T db psql -U postgres

Tests

After starting the docker-compose stack, run the backend integration lane with:

docker-compose exec web pytest -m integration

Deployment

Visit our deployment guideline for setting up this repository on a production environment.

API usage

Visit the REST API guide to connect your Plio's frontend setup with the backend.

Contributing

• Pre-commit
• GitHub Workflows
• Multitenancy
• Caching
• Zappa Settings
• Soft Delete
• Google OAuth2
• Error monitoring
• Cypress
• DB Backup And Restore

Product Guide

To know more about the features and updates on Plio, visit the product guide on our YouTube channel.