Difference between revisions of "Django"

From Sinfronteras
Jump to: navigation, search
(Created page with "https://www.djangoproject.com/ <br /> ==Recipe REST API - Udemy course== https://www.udemy.com/course/django-python-advanced/ '''API Features:''' * 19 API Endpoints : Man...")
 
Line 52: Line 52:
  
 
'''Test-driven development (TDD)'''
 
'''Test-driven development (TDD)'''
 +
 +
... pegar la imagen de la presentacion que tomé del curso ...
 +
 +
 +
'''How we'll use Docker:'''
 +
* Define a Dockerfile: Contains all  the OS level dependencies that our project needs.
 +
* Create a Docker Compose configuration: Tells Docker how to run the images that are created from our Docker file configuration.
 +
* Run all commands via Docker Compose.
 +
 +
 +
* Docker on GitHub Actions:
 +
:* '''Docker Hub''' is where we can pull shared public images to reuse them for your project. For example there an image for Python, PostgreSQL, etc. Docker Hub has introduced rate limits.
 +
::* Because of the rate limits, we have to Authenticate with Docker Hub: Create an account / Setup credentials / Login before running job.
 +
::* https://hub.docker.com/
 +
 +
 +
----
 +
 +
* create «requirements.txt» in your project directory:
 +
 +
requirements.txt:
 +
Django>=3.2.4,<3.3
 +
djangorestframework>=3.12.4,<3.13
 +
 +
 +
Dockerfile:
 +
FROM python:3.9-alpine3.13
 +
LABEL maintainer="adeloaleman"
 +
 +
ENV PYTHONUNBUFFERED 1
 +
COPY ./requirements.txt /tmp/requirements.txt
 +
COPY ./app /app
 +
WORKDIR /app
 +
EXPOSE 8000
 +
 +
RUN python -m venv /py && \
 +
    /py/bin/pip install --upgrade pip && \
 +
    /py/bin/pip install -r /tmp/requirements.txt && \
 +
    rm -rf /tmp && \
 +
    adduser \
 +
        --disabled-password
 +
        --no-create-home \
 +
        django-user
 +
       
 +
ENV PATH="/py/bin:$PATH"
 +
 +
USER django-user
 +
 +
 +
.dockerignore:
 +
# Git
 +
.git
 +
.gitignore
 +
 +
# Docker
 +
.docker
 +
 +
# Python
 +
app/__pycache__/
 +
app/*/__pycache__/
 +
app/*/*/__pycache__/
 +
app/*/*/*/__pycache__/
 +
.env/
 +
.venv/
 +
venv/
 +
 +
 +
Then we create the app directory insde our project directory
 +
 +
Then we run:
 +
docker build .
 +
 +
 +
Then we create our docker-compose.yml:
 +
version: "3.9"
 +
 +
services:
 +
  app:
 +
    build:
 +
      context: .
 +
    ports:
 +
      - "8000:8000"
 +
    volumes:
 +
      - ./app:/app
 +
    command: >
 +
      sh -c "python manage.py runserver 0.0.0.0:8000"
 +
 +
 +
Then we run in our project directory:
 +
docker-compose build
 +
 +
 +
...
 +
...
 +
...
 +
 +
 +
docker-compose run --rm app sh -c "flake8"
 +
 +
 +
docker-compose run --rm app sh -c "django-admin startproject app ."
 +
 +
 +
docker-compose up

Revision as of 00:00, 5 May 2023

https://www.djangoproject.com/



Recipe REST API - Udemy course

https://www.udemy.com/course/django-python-advanced/


API Features:

  • 19 API Endpoints
Managing users, recipes, tags, ingredients
  • User Authentication
  • Browseable Admin Interface (Django Admin)
  • Browsable API (Swagger)


Techologies used in this course:

  • Django allows handle:
  • URL Mappings
  • Object Relational Mapper
  • Admin site
  • Django REST Framework:
  • Django add-on
  • Build REST APIs
  • PostgresSQL
  • Docker
  • Swagger:
  • Documentation
  • Browsable API (testing)


Structure of the project:

  • app/ : Main app - Django project
  • app/core/ : Hangle any code shared between multiple apps. Such as the DB definition using the Django modules
  • app/user/ : User related code. Such as User registration & auth tokens
  • app/recipe/ : Recipe related code. Such as handling updating ingredients - Creating/Deleting/Udating recipes


Unit Tests and Test-driven development (TDD):
See explanation at https://www.udemy.com/course/django-python-advanced/learn/lecture/32238668#notes


  • Unit Tests: Code which test code:
It's usually done this way:
  • You Set up some conditions; such as inputs to a function
  • Then you run a piece of code
  • Checks outputs of that code using "assertions"


Test-driven development (TDD)

... pegar la imagen de la presentacion que tomé del curso ...


How we'll use Docker:

  • Define a Dockerfile: Contains all the OS level dependencies that our project needs.
  • Create a Docker Compose configuration: Tells Docker how to run the images that are created from our Docker file configuration.
  • Run all commands via Docker Compose.


  • Docker on GitHub Actions:
  • Docker Hub is where we can pull shared public images to reuse them for your project. For example there an image for Python, PostgreSQL, etc. Docker Hub has introduced rate limits.
  • Because of the rate limits, we have to Authenticate with Docker Hub: Create an account / Setup credentials / Login before running job.
  • https://hub.docker.com/



  • create «requirements.txt» in your project directory:

requirements.txt: Django>=3.2.4,<3.3 djangorestframework>=3.12.4,<3.13


Dockerfile: FROM python:3.9-alpine3.13 LABEL maintainer="adeloaleman"

ENV PYTHONUNBUFFERED 1 COPY ./requirements.txt /tmp/requirements.txt COPY ./app /app WORKDIR /app EXPOSE 8000

RUN python -m venv /py && \

   /py/bin/pip install --upgrade pip && \
   /py/bin/pip install -r /tmp/requirements.txt && \
   rm -rf /tmp && \
   adduser \
       --disabled-password
       --no-create-home \
       django-user
       

ENV PATH="/py/bin:$PATH"

USER django-user


.dockerignore:

  1. Git

.git .gitignore

  1. Docker

.docker

  1. Python

app/__pycache__/ app/*/__pycache__/ app/*/*/__pycache__/ app/*/*/*/__pycache__/ .env/ .venv/ venv/


Then we create the app directory insde our project directory

Then we run: docker build .


Then we create our docker-compose.yml: version: "3.9"

services:

 app:
   build:
     context: .
   ports:
     - "8000:8000"
   volumes:
     - ./app:/app
   command: >
     sh -c "python manage.py runserver 0.0.0.0:8000"


Then we run in our project directory: docker-compose build


... ... ...


docker-compose run --rm app sh -c "flake8"


docker-compose run --rm app sh -c "django-admin startproject app ."


docker-compose up