Support a genuinely headless install (UI_TYPE=none without Django)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- build-system
Research direction
Start by grepping LOGGER_MANAGER_DATABASE and setup_django in utils/install_openrvdas.sh and reading where the supervisord config is generated, then run a UI_TYPE=none install to see what it still pulls in. Audit logger/readers/database_reader.py and the installer-written database/settings.py for guarded ORM use, and compare server/sqlite_server_api.py against django_gui/django_server_api.py to judge backend parity. Done means a fresh headless install completes with pure-Python deps only and LoggerManager runs on the sqlite backend.
Written by the indexing model from the issue text.
Description
Summary
UI_TYPE=none is meant to be the logger-only install: run loggers on a box that reports to a server elsewhere, with no web console. It works today (as of #597), but it still installs and configures Django, because the installer treats the Django ORM as LoggerManager's backing store regardless of UI choice.
For constrained hardware — a Raspberry Pi running a handful of sensors — that's a database engine, a migration step, and a settings file that nothing subsequently uses.
Why Django is still required
Two places assume it, independent of UI_TYPE:
utils/install_openrvdas.shrunssetup_djangounconditionally. Its comment reads "always needed — logger_manager uses Django ORM regardless of which web UI is selected". It copiesdjango_gui/settings.py, then runsmanage.py makemigrationsandmanage.py migrate.LOGGER_MANAGER_DATABASE=djangois written into the supervisord config for every UI type exceptreact, so the running LoggerManager is pointed at the Django backend.
This is why #592's attempt to make Django optional broke headless installs, and why #597 put it back in core.
What already exists
server/logger_manager.py supports three backends and imports them conditionally:
if args.database == 'django':
from django_gui.django_server_api import DjangoServerAPI
elif args.database == 'memory':
from server.in_memory_server_api import InMemoryServerAPI
elif args.database == 'sqlite':
from server.sqlite_server_api import SQLiteServerAPI
server/sqlite_server_api.py is a full ServerAPI implementation with no Django dependency. So the capability is there — the installer just never selects it.
Proposed change
When UI_TYPE=none:
- Set
LOGGER_MANAGER_DATABASE=sqliteinstead ofdjango. - Skip
setup_django— nodjango_gui/settings.py, no migrations. - Move
django,djangorestframeworkanddrf-spectacularout of core dependencies into adjangoextra, installed whenUI_TYPE != none. (uwsgistays in thewebextra, installed whenUI_TYPE == django, as #597 established.)
Result: a logger-only install pulls 8 pure-Python packages, needs no compiler, no GDAL, and no database engine.
Open questions for whoever picks this up
- Does anything else in the headless path touch the Django ORM?
database/settings.pyis written by the installer and imported (guarded) bylogger/readers/database_reader.py; that needs checking before Django is removed. Worth auditing rather than assuming. - Is
sqlitebackend parity good enough? It should be verified that cruise load, mode changes and logger status all behave the same underSQLiteServerAPIas underDjangoServerAPIbefore this becomes the default for any install mode. - Migration path for existing headless installs. Someone who installed with
UI_TYPE=nonetoday has a Django-backed state DB. Switching backends on upgrade would orphan it. This may need to apply only to fresh installs, or need an explicit opt-in. - Does supervisord still make sense here, or should a logger-only mode be lighter still? Out of scope for this issue, but related — see the discussion of an
install_minimal.sh, which was considered and set aside in favor of makingUI_TYPE=nonework properly.
Context
Came out of the v2.6.1 packaging work (#591, #592, #593, #595, #597), which made a compiler-free and GDAL-free install possible. This is the remaining step to make the logger-only case genuinely minimal rather than merely working.
- Dominant language
- Python
- Stars
- 57
- Forks
- 30
- Avg merge
- 3h 14m
- Merged PRs (30d)
- 56
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OceanDataTools/openrvdas
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OceanDataTools/openrvdas#760 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
OceanDataTools/openrvdas#758 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OceanDataTools/openrvdas#748 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 58/100
OceanDataTools/openrvdas#743 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OceanDataTools/openrvdas#721 ·
Maintainers usually reply within 1 day
All issues in OceanDataTools/openrvdas
Similar issues
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
almanac-data/climate-almanac#138 ·
Maintainers usually reply within 1 day
-
level/subtask type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-virtual-machines#1091 ·
Maintainers usually reply within 1 day
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#142 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·