Sign in to access MinerSheets revolutionary features
Try searching with different keywords
The backbone of operational excellence
Understanding MinerSheets revolutionary design and technical foundation
MinerSheets is built on a Dynamic Model Factory architecture that combines the best of Google AppSheet's visual approach with Django's robustness and Laravel's elegant relationships.
Tailwind CSS + Alpine.js for modern, reactive UI with zero build step
Django 4.2 with dynamic model registration and runtime schema management
PostgreSQL 15 with dynamic schema synchronization and automatic migrations
Django 4.2.7 with Python 3.11+
ORM, admin interface, authentication, and dynamic model support
PostgreSQL 15
Advanced data types, JSON support, and runtime schema modifications
Tailwind CSS 3.x + Alpine.js 3.x
Utility-first CSS framework and lightweight reactive components
Django REST Framework + Token Authentication
RESTful API endpoints with comprehensive validation
Docker, Pre-commit Hooks, Comprehensive Testing
Quality enforcement and dual environment methodology
The heart of MinerSheets - allows runtime model creation without code or migrations.
Core module handling all dynamic model operations and database management.
Organized admin interface for logical separation of concerns.
Create and configure new models
Manage dynamically created models
Django core administration
schema_builder_custommodel
Stores model definitions (name, table, display field)
schema_builder_customfield
Stores field configurations (type, options, relations)
schema_builder_<model_name>
Dynamically created tables for user-defined models
💡 Smart Design: Tables are created and modified at runtime without migrations, while maintaining full Django ORM compatibility and referential integrity.
Browser sends request to Django (via Nginx in production)
Django URLs route to appropriate view function
View retrieves dynamic model from registry, queries database
Django template engine renders HTML with context data
Alpine.js enhances interactivity on client side
🎯 Best Practice: Both environments share the same PostgreSQL database (port 5434), ensuring zero data inconsistency while providing different testing contexts.