Skip to main content

The control room for your Django app

Project description

Tests codecov PyPI version Python versions License: MIT

DJ Control Room

The control room for your Django app

Docs

https://yassi.github.io/dj-control-room/

Features

  • TBD: Add your main features here

Project Structure

dj-control-room/
├── dj_control_room/         # Main package
│   ├── templates/           # Django templates
│   ├── views.py             # Django views
│   └── urls.py              # URL patterns
├── example_project/         # Example Django project
├── tests/                   # Test suite
├── images/                  # Screenshots for README
└── requirements.txt         # Development dependencies

Requirements

  • Python 3.9+
  • Django 4.2+

Screenshots

Django Admin Integration

Seamlessly integrated into your Django admin interface. A new section for dj-control-room will appear in the same places where your models appear.

NOTE: This application does not actually introduce any model or migrations.

Admin Home

Installation

1. Install the Package

pip install dj-control-room

2. Add to Django Settings

Add dj_control_room to your INSTALLED_APPS:

INSTALLED_APPS = [
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'dj_control_room',  # Add this line
    # ... your other apps
]

3. Configure Settings (Optional)

Configure how panels appear in the admin sidebar:

# Optional: DJ Control Room settings
DJ_CONTROL_ROOM = {
    # Control whether panels register in both Control Room and their own admin sections
    'REGISTER_PANELS_IN_ADMIN': False,  # Default: False (only in Control Room)
    
    # Or use granular per-panel control:
    # 'PANEL_ADMIN_REGISTRATION': {
    #     'redis': True,   # Redis shows in both places
    #     'cache': False,  # Cache only in Control Room
    #     '*': False,      # Default for other panels
    # }
}

See ADMIN_INTEGRATION.md for detailed configuration options.

4. Include URLs

Add the Panel URLs to your main urls.py:

from django.contrib import admin
from django.urls import path, include

urlpatterns = [
    path('admin/dj-control-room/', include('dj_control_room.urls')),  # Add this line
    path('admin/', admin.site.urls),
]

5. Run Migrations and Create Superuser

python manage.py migrate
python manage.py createsuperuser  # If you don't have an admin user

6. Access the Panel

  1. Start your Django development server:

    python manage.py runserver
    
  2. Navigate to the Django admin at http://127.0.0.1:8000/admin/

  3. Look for the "DJ CONTROL ROOM" section in the admin interface

License

This project is licensed under the MIT License. See the LICENSE file for details.


Development Setup

If you want to contribute to this project or set it up for local development:

Prerequisites

  • Python 3.9 or higher
  • Redis server running locally
  • Git
  • Autoconf
  • Docker

It is reccommended that you use docker since it will automate much of dev env setup

1. Clone the Repository

git clone https://github.com/yassi/dj-control-room.git
cd dj-control-room

2a. Set up dev environment using virtualenv

python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate

pip install -e . # install dj-control-room package locally
pip intall -r requirements.txt  # install all dev requirements

# Alternatively
make install # this will also do the above in one single command

2b. Set up dev environment using docker

make docker_up  # bring up all services (redis, memached) and dev environment container
make docker_shell  # open up a shell in the docker conatiner

3. Set Up Example Project

The repository includes an example Django project for development and testing

cd example_project
python manage.py migrate
python manage.py createsuperuser

4. Populate Test Data (Optional)

Add any custom management commands for populating test data if needed.

6. Run the Development Server

python manage.py runserver

Visit http://127.0.0.1:8000/admin/ to access the Django admin with DJ Control Room.

7. Running Tests

The project includes a comprehensive test suite. You can run them by using make or by invoking pytest directly:

# build and install all dev dependencies and run all tests inside of docker container
make test_docker

# Test without the docker on your host machine.
# note that testing always requires a redis and memcached service to be up.
# these are mostly easily brought up using docker
make test_local

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

dj_control_room-0.1.0.tar.gz (1.4 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

dj_control_room-0.1.0-py3-none-any.whl (1.4 MB view details)

Uploaded Python 3

File details

Details for the file dj_control_room-0.1.0.tar.gz.

File metadata

  • Download URL: dj_control_room-0.1.0.tar.gz
  • Upload date:
  • Size: 1.4 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.9.7

File hashes

Hashes for dj_control_room-0.1.0.tar.gz
Algorithm Hash digest
SHA256 f4916e775594cd83665712edff158b090f5bcfedf66ba4ff9f361c04d36e13bb
MD5 eb47dadbe25b4b8e5a743dc09c9f0a6b
BLAKE2b-256 c4a12f25440f587f88a382fb344b270d0f37475f57daa4efd6b5aa16b3cfa63b

See more details on using hashes here.

File details

Details for the file dj_control_room-0.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for dj_control_room-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 30793c4d87d3acd7cefcf94541eb611197789e6a222bade8e414a606fe0bb12c
MD5 7fc8cfc1d262725edb78f360e385b292
BLAKE2b-256 7ac5d32b72c9c0e0899c6bedac154bc3cd5615c397b3a1e299b0485942955d59

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page