jearistiz / guane-intern-fastapi Goto Github PK

• Setup Pipfile
• Create directory structure
• Create main app

Create CRUDs:

• Base CRUD
• Dog CRUD
• User CRUD

Implement endpoints tests

Consider:

• asyncpg
• tortois
• SqlAlchemy asynchronous I/O features: this one might be the less invasive option. Since the app is already using SqlAlchemy, the support for ORM when using asyncio-compatible dialects would prevent a lot of refactoring.

Create docker containers:

• Python - FastAPI app - Uvicorn server
  • Dockerfile
• PostgreSQL database
• docker-compose.yml

Include

• Local RabbitMQ - Celery and Redis setup/teardown

Using PostgreSQL and SQLAlchemy:

• Create Dog table
• Create User table

• different apps consume the same celery instance.
• different apps consume the same rabbitmq instance.
• different apps consume the same redis instance.

minigramer/diagrams

Include:

• scripts
  • server
  • tests
  • docker
• docker compose

Upload a file to the endpoint POST at https://gttb.guane.dev/api/files via our POST endpoint at /api/upload-predefined-file-to-guane.

• Implement dogs endpoints
• Implement users endpoints

Include:

• How to setup the local build
• How the scripts work

Vulnerability reported and fixed. More info here.

Steps

git clone https://github.com/jearistiz/guane-intern-fastapi
cd guane-intern-fastapi
docker-compose up --build

Expected behaviour

Docker compose starts building all service images from docker-compose.yml

Actual behaviour

$ docker-compose up -d
ERROR: Service 'backend_app' depends on service 'celery' which is undefined.

So there is something I am missing or there is no celery service in docker-compose.yml which is required on backend-app service to work.
See depends-on:

version: "3.5"
services:
  backend_app:
    build:
      context: .
      dockerfile: Dockerfile
    container_name: backend_app
    stop_signal: SIGINT
    env_file: .env
    image: app/backend
    depends_on: 
      - postgres
      - celery
. . .

With information about all the services. The architecture is complete. Celery tests missing.

Also consider moving the celery_app module from core/ to worker/. I think this makes much more sense because it is a completely separate component.

• Celery worker
• Rabbitmq message broker
• Docker image of Rabbitmq