videoflix/backend
2025-05-14 04:49:40 +02:00
..
auth_app fix: minor bugfixes in the authentication process 2025-04-22 13:19:32 +02:00
templates chore: integrate django-environ, create .env-example, and move sensitive settings to .env 2025-04-22 13:08:31 +02:00
user_app refactor: reorganize folder structure for improved maintainability and readability 2025-04-19 18:15:57 +02:00
video_app feat: implement VideoProgressService for persistent video progress tracking, refactor video player setup, and enhance backend (model/serializer/view) to support progress saving 2025-05-14 04:49:40 +02:00
videoflix feat: implement VideoProgressService for persistent video progress tracking, refactor video player setup, and enhance backend (model/serializer/view) to support progress saving 2025-05-14 04:49:40 +02:00
.gitignore feat: update Django and Werkzeug to fix CVEs 2025-04-23 13:01:29 +02:00
erm_videoflix.png bugfixes 2024-08-30 10:38:03 +02:00
manage.py update backend data structure, custom user created 2024-08-04 08:47:19 +02:00
package-lock.json feat: update Django and Werkzeug to fix CVEs 2025-04-23 13:01:29 +02:00
package.json feat: update Django and Werkzeug to fix CVEs 2025-04-23 13:01:29 +02:00
README.md docs: update backend README.md with latest changes and setup instructions 2025-04-24 08:05:31 +02:00
requirements.txt refactor: improve code readability and maintainability across components 2025-05-02 17:20:17 +02:00

Backend

Env Configuration

To configure your backend application, you need to create an .env file in the videoflix folder of your project. This file contains various environment-specific settings, including email, security, and monitoring configuration.

Step 1: Create the .env file

Create a file named .env inside the videoflix folder of your project:

/your-project-root/
└── videoflix/
    ├── .env_example
    └── .env  ← create this file

You can also simply rename or copy the existing .env_example file:

cp videoflix/.env_example videoflix/.env

Then open videoflix/.env and adjust the values according to your environment.

Step 2: Add the required configuration

Open the .env file and include the following lines according to your needs:

# General settings
DEBUG=False
SECRET_KEY=your_secret_key_here

# Email settings
EMAIL_HOST_USER=your_email_user
EMAIL_HOST_PASSWORD=your_email_password

# Sentry settings
SENTRY_DSN=your_sentry_dsn