The challenge is done

.env

@@ -0,0 +1,14 @@
+SECRET_KEY=
+DEBUG=
+ALLOWED_HOSTS=
+
+DB_NAME=
+DB_USER=
+DB_PASS=
+DB_HOST=
+DB_PORT=
+
+TIME_ZONE=
+
+ADMIN_USERNAME=
+ADMIN_PASSWORD=

.gitignore

@@ -0,0 +1,139 @@
+### Python template
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# IDE
+.idea

Dockerfile

@@ -0,0 +1,18 @@
+FROM python:3.10
+LABEL MAINTAINER = "Mahdi Namaki | mavenium@gmail.com"
+
+ENV PYTHONUNBUFFERD 1
+
+RUN mkdir /project
+WORKDIR /project
+COPY /src /project
+
+ADD requirements_base.txt /project
+
+RUN apt-get -y update
+RUN apt-get -y upgrade
+
+RUN pip install --upgrade pip
+RUN pip install --upgrade -r requirements_base.txt
+
+RUN apt-get clean

README.md

@@ -1,23 +1,38 @@
-# django-challenge
-
-
-The volleyball Federation decided to use an online selling platform for the next season, and our company has been chosen for implementing that.
-
-# Requirements
-
-Our system should have REST APIs for the following tasks:
-
-- User signup and login
-- Adding a new stadium
-- Defining matches
-- Defining the place of seats for each match
-- Buying seats of a match (There is no need for using a payment gateway)
-
-# Implementation details
-
-We don't need a GUI for this system. You can use the Django admin.
-Try to write your code as **reusable** and **readable** as possible. Also, don't forget to **document your code** and clear the reasons for all your decisions in the code.
-Using API documentation tools is a plus.
-Don't forget that many people trying to buy tickets for a match. So try to implement your code in a way that could handle the load. If your solution is not sample enough for implementing fast, you can just describe it in your documents.
-
-Please fork this repository and add your code to that. Don't forget that your commits are so important. So be sure that you're committing your code often with a proper commit message.
+### How to execute via docker?
+- Install `docker` and `docker-compose` on server
+- Clone the project `git clone https://<token>@github.com/mavenium/django-challenge.git`
+- Go to the project directory `cd django-challenge`
+- Run `docker-compose -f docker-compose-dev.yml up -d --force-recreate --build` command
+- Then go to the `http://127.0.0.1:8000/` in your browser
+
+### How to execute in local?
+- Clone the project `git clone https://<token>@github.com/mavenium/django-challenge.git`
+- Go to the project directory `cd django-challenge/src`
+- Create a new environment and active that
+- Run the `pip install --upgrade -r ../requirements_development.txt` to install the requirements
+- Then create a new database in the Postgresql like `ticket_sales_system` and add the database name to the `core/settings.py`
+- Then run the `python manage.py migrate` to create the tables
+- Then run the `python manage.py initialize_admin` to create the default admin
+- After that run the `python manage.py runserver`
+
+### Additional Notes
+#### What is the username and password for the default superuser?
+- Username is `admin@ticketing.sample` and password is `admin@control*987`
+#### How to run the tests ?
+- By running the `python manage.py test` command in the running environment (local or docker container)
+#### What are the `swagger` and `redoc` urls ?
+- The `swagger` url is `http://127.0.0.1:8000/api/v1/swagger/`
+- The `redoc` url is `http://127.0.0.1:8000/api/v1/redoc/`
+#### Is the postman collection also offered?
+- Yes, `postman_collection.json` 
+#### How to run on the production server ?
+- This project is not 100% ready for production mode, but you can change the `Dockerfile` and `docker-compose-dev.yml` for this purpose
+- The `.env` file is available in the project 
+#### Where is the documentation?
+- It located in the `docs/_build/html/index.html`
+#### Anything else ?
+- We need the Celery for creating the scheduled task in order to remove the ticket object with reserved status after 5 or 10 minutes of creating it in order to make tickets available for buying for people.
+- A scheduled task system is not developed due to the experimental of the project
+- There are 44 tests in the project. Those are not enough, but they show my ability to write tests on two levels.
+- A caching system is needed in production mode, it has not been implemented due to the experimental of the project
+- The project has been implemented with the ability to translate into other languages

docker-compose-dev.yml

@@ -0,0 +1,57 @@
+version: '3.3'
+
+services:
+  postgresql:
+    image: postgres:latest
+    hostname: postgresql
+    container_name: postgresql
+    volumes:
+      - postgresql_volume:/data
+    restart: always
+    ports:
+      - "5432:5432"
+    environment:
+      - POSTGRES_DB=postgres
+      - POSTGRES_USER=postgres
+      - POSTGRES_PASSWORD=postgres
+    networks:
+      - project_network
+
+  project:
+    build:
+      context: .
+      dockerfile: Dockerfile
+    command: sh -c '
+      python manage.py wait_for_db &&
+      python manage.py migrate &&
+      python manage.py migrate --run-syncdb &&
+      python manage.py collectstatic --noinput &&
+      python manage.py initialize_admin &&
+      python manage.py runserver 0.0.0.0:8000'
+    hostname: project
+    container_name: project
+    volumes:
+      - ./src:/project
+      - statics_volume:/project/statics
+    restart: always
+    environment:
+      - DB_NAME=postgres
+      - DB_HOST=postgresql
+      - DB_USER=postgres
+      - DB_PASS=postgres
+    ports:
+      - "8000:8000"
+    networks:
+      - project_network
+    depends_on:
+      - postgresql
+
+volumes:
+  postgresql_volume:
+    external: false
+  statics_volume:
+    external: false
+
+networks:
+  project_network:
+    external: false

docs/Makefile

@@ -0,0 +1,20 @@
+# Minimal makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line, and also
+# from the environment for the first two.
+SPHINXOPTS    ?=
+SPHINXBUILD   ?= sphinx-build
+SOURCEDIR     = .
+BUILDDIR      = _build
+
+# Put it first so that "make" without argument is like "make help".
+help:
+	@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
+
+.PHONY: help Makefile
+
+# Catch-all target: route all unknown targets to Sphinx using the new
+# "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
+%: Makefile
+	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

docs/_build/html/.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: 405e4bab41ed14b5f0c33c454d997738
+tags: 645f666f9bcd5a90fca523b33c5a78b7