Build a Python App
Create an Eenos Django app with protected views, relative URLs, panel templates and namespaced static assets.
Python apps are Django packages loaded into enabled panels. Use the installed Eenos Python/Django environment on a development server; do not install an unrelated Django release into the shared runtime to match a tutorial.
Official reference package
Download the Python sample. Inspect it before installation: it includes interfaces, scripts, hooks and lifecycle files, not just a view. Its name is sampleapp; use your own identity for a new project.
For a minimal WAP app, put the following under exampleapp/wap/exampleapp/ alongside __init__.py. Set the manifest's language to python, enable WAP and leave unsupported panels off.
App configuration
from django.apps import AppConfig
class ExampleappConfig(AppConfig):
default_auto_field = 'django.db.models.BigAutoField'
name = 'exampleapp'Save this as apps.py. Keep the import name identical to the manifest and installed folder name.
Protected read-only view
from django.contrib.auth.decorators import login_required
from django.shortcuts import render
@login_required
def index(request):
return render(request, 'exampleapp/index.html', {})Save as views.py. This demonstrates login enforcement for a read-only page. Account ownership, reseller scope and authorization for sensitive actions still need explicit checks; login_required alone does not implement them.
Relative URLs
from django.urls import path
from . import views
app_name = 'exampleapp'
urlpatterns = [path('', views.index, name='index')]Save as urls.py. The panel mounts this URL configuration under its localized apps/exampleapp/ prefix. Do not repeat that prefix inside the app's own patterns. Use named URL reversal instead of hardcoding a language prefix.
Template and static assets
Create templates/exampleapp/index.html:
{% extends "base.html" %}
{% load i18n static %}
{% block title %}{% translate "Example App" %} - Eenos{% endblock %}
{% block content %}
<div class="eenos-card">
<h1 class="eenos-page-title">{% translate "Example App" %}</h1>
<p>{% translate "Your app is available in this panel." %}</p>
</div>
{% endblock %}Use the current selected panel's base template and shared UI components. Namespace templates and static paths to avoid collisions. Put shared assets under static/exampleapp/ and reference app assets through Django's static tag.
For RAPP/UAPP, supply separate rapp/exampleapp/ and uapp/exampleapp/ packages as needed. Review each panel's identity and data access model rather than copying administrator actions unchanged.
The installer does not automatically create a Django data migration plan for your app. If you add models or persistent storage, document the deployment/migration and rollback process separately and verify it against the installed panel database configuration.