matthewte / etl_project_monorepo Goto Github PK

Currently root url for the whole project on the Nginx server routes to the API, which doesn't have a root url. This means that the root url throws and error (currently the actual entrypoint for the REST API is /swagger/ to get the API schema. Add a redirect or a page that displays on root url that redirects to either the Swagger UI or the /dev/ section of the project so Nginx can correctly route traffic.

When a blog post is created with a new category I need the API to create a category with that name when it receives the POST request. I will probably have to overwrite the model serializer create() function like the stack overflow article. Also check the DRF documentation for changing read-only seralizers
https://www.django-rest-framework.org/api-guide/relations/#writable-nested-serializers

https://stackoverflow.com/questions/73162763/create-foreign-key-objects-inside-serializer

Add a description to the Swagger UI section that outlines how to use the API and just introductory documentation. I think it can be styled in markdown or it might be non-escaped HTML.

Currently the back-end is a janky sqlite3 database with a sketch docker volume that does not seem to work. This needs to be replaced with a psql instance that correctly connects to the docker volume.

• Set up PSQL connection on the REST API backend with environment variables.
• Create docker-compose instance in nginx repo that creates and configures the psql container.
• Connect the data from the PSQL container to an external volume.
• Re-Deploy onto Droplet and test integration.