Schon — your store without the extra baggage. https://schon.io
Find a file
Egor fureunoir Gorbunov 18782a8bc0 Features: 1) Add context to serializers in create method of AddressViewSet.
Fixes: 1) Correct serialization flow by separating create and output serializers.

Extra: 1) Minor variable renaming for clarity; 2) Improved readability of the `create` method.
2025-06-01 19:58:51 +03:00
blog Features: 1) Add .gitkeep files for payments/static and blog/static directories to track empty folders; 2025-06-01 18:50:37 +03:00
core Features: 1) Add context to serializers in create method of AddressViewSet. 2025-06-01 19:58:51 +03:00
evibes Features: None; 2025-05-29 22:24:21 +03:00
payments Features: 1) Add .gitkeep files for payments/static and blog/static directories to track empty folders; 2025-06-01 18:50:37 +03:00
scripts Initial Commit 2025-04-29 22:40:30 +03:00
storefront Storefront updates 2025-05-28 22:37:39 +10:00
vibes_auth Features: 1) Enforced password validation using Django's validate_password in password reset flows; 2) Added handling for ValidationError during password validation; 2025-05-29 22:42:13 +03:00
.dockerignore Features: 1) Add .gitkeep files for payments/static and blog/static directories to track empty folders; 2025-06-01 18:50:37 +03:00
.gitignore Features: 1) Expand .gitignore to include comprehensive rules for Python, Node, Docker, IDEs, test artifacts, and distribution files; 2025-05-26 15:54:43 +03:00
CODEOWNERS Features: 1) Add code ownership for .mjs, .cjs, and .astro files to SaVBaD. 2025-06-01 18:32:07 +03:00
docker-compose.yml Features: 2025-05-26 16:03:01 +03:00
Dockerfile.app Features: 1) Add Dockerfile.app with author label for application container; 2) Add CODEOWNERS file for ownership management; 3) Introduce Dockerfile.storefront for storefront container; 4) Add .gitkeep file for storefront folder; 2025-05-26 15:34:45 +03:00
Dockerfile.storefront Features: 1) Add Dockerfile.app with author label for application container; 2) Add CODEOWNERS file for ownership management; 3) Introduce Dockerfile.storefront for storefront container; 4) Add .gitkeep file for storefront folder; 2025-05-26 15:34:45 +03:00
LICENSE Initial Commit 2025-04-29 22:40:30 +03:00
manage.py Initial Commit 2025-04-29 22:40:30 +03:00
nginx Initial Commit 2025-04-29 22:40:30 +03:00
poetry.lock Features: 1) Add UploadAvatar mutation to handle avatar uploads; 2) Integrate graphene-file-upload for file upload capability. 2025-05-20 11:52:07 +03:00
pyproject.toml Features: None; 2025-05-29 22:24:21 +03:00
README.md Features: 2025-05-26 17:36:12 +03:00
ruff.toml Features: 2025-05-26 17:36:12 +03:00

eVibes

LOGO

eVibes is an eCommerce backend service built with Django. Its designed for flexibility, making it ideal for various use cases and learning Django skills. The project is easy to customize, allowing for straightforward editing and extension.

Table of Contents

Features

  • Modular Architecture: Easily extend and customize the backend to fit your needs.
  • Dockerized Deployment: Quick setup and deployment using Docker and Docker Compose.
  • Asynchronous Task Processing: Integrated Celery workers and beat scheduler for background tasks.
  • GraphQL and REST APIs: Supports both GraphQL and RESTful API endpoints.
  • Internationalization: Multilingual support using modeltranslate.
  • Advanced Caching: Utilizes Redis for caching and task queuing.
  • Security: Implements JWT authentication and rate limiting.

Getting Started

Prerequisites

  • Docker and Docker Compose installed on your machine.
  • Python 3.12 if running locally without Docker.

Installation

  1. Clone the repository:

    git clone https://gitlab.com/wiseless.xyz/eVibes.git
    cd eVibes
    
  2. Copy the example environment file and configure it.

  3. Build and start the services:

    docker-compose up -d --build
    

    This command will build the Docker images and start all the services defined in the docker-compose.yml file.

Configuration

Dockerfile

Don't forget to change the RUN sed -i 's|https://deb.debian.org/debian|https://ftp.<locale>.debian.org/debian|g' /etc/apt/sources.list.d/debian.sources

Environment Variables

The project uses environment variables for configuration. Below is an example of the .env file:

EVIBES_PROJECT_NAME="eVibes"
EVIBES_FRONTEND_DOMAIN="evibes.com"
EVIBES_BASE_DOMAIN="evibes.com"
SENTRY_DSN=""
DEBUG=1

SECRET_KEY="SUPERSECRETKEY"
JWT_SIGNING_KEY="SUPERSECRETJWTSIGNINGKEY"

ALLOWED_HOSTS="localhost 127.0.0.1 evibes.com api.evibes.com b2b.evibes.com"
CSRF_TRUSTED_ORIGINS="http://api.localhost http://127.0.0.1 https://evibes.com https://api.evibes.com https://www.evibes.com https://b2b.evibes.com"
CORS_ALLOWED_ORIGINS="http://api.localhost http://127.0.0.1 https://evibes.com https://api.evibes.com https://www.evibes.com https://b2b.evibes.com"

POSTGRES_DB="evibes"
POSTGRES_USER="evibes_user"
POSTGRES_PASSWORD="SUPERSECRETPOSTGRESPASSWORD"

DBBACKUP_SFTP_HOST="Your SFTP backup host"
DBBACKUP_SFTP_USER="The username to use to log in to that host"
DBBACKUP_SFTP_PASS="The password to use to log in to that host"

ELASTIC_PASSWORD="SUPERSECRETELASTICPASSWORD"

REDIS_PASSWORD="SUPERSECRETREDISPASSWORD"

CELERY_BROKER_URL="redis://:SUPERSECRETREDISPASSWORD@redis:6379/0"
CELERY_RESULT_BACKEND="redis://:SUPERSECRETREDISPASSWORD@redis:6379/0"

FLOWER_USER=evibes
FLOWER_PASSWORD="SUPERSECRETFLOWERPASSWORD"

EMAIL_BACKEND="django.core.mail.backends.smtp.EmailBackend"
EMAIL_HOST="smtp.whatever.evibes.com"
EMAIL_PORT="465"
EMAIL_USE_TLS=0
EMAIL_USE_SSL=1
EMAIL_HOST_USER="your-email-user@whatever.evibes.com"
EMAIL_HOST_PASSWORD="SUPERSECRETEMAILHOSTPASSWORD"
EMAIL_FROM="your-email-user@whatever.evibes.com"

COMPANY_NAME="eVibes, Inc."
COMPANY_PHONE_NUMBER="+888888888888"
COMPANY_ADDRESS="The place that does not exist"

OPENAI_API_KEY="Haha, really?"

ABSTRACT_API_KEY="Haha, really? x2"

Note: Replace all placeholder values (e.g., your-secret-key, your-database-name) with your actual configuration.

Usage

Add these lines to your hosts-file to use django-hosts functionality on localhost:

127.0.0.1 api.localhost
127.0.0.1 b2b.localhost

Otherwise, add needed subdomains to DNS-settings of your domain.

Once the services are up and running, you can access the application at http://api.localhost:8000.

  • Django Admin: http://api.localhost:8000/admin/
  • API Endpoints:
    • REST API: http://api.localhost:8000/docs/swagger or http://api.localhost:8000/docs/redoc
    • GraphQL API: http://api.localhost:8000/graphql/

Contact

FAVICON