Landing page template for Metaservices based on ShariX Open with the login button for authorization and access to open-webuser.
Шаблон посадочной страницы Метасервиса на основе ShariX Open с кнопкой авторизации для перехода к open-webuser.
|
|
2 weeks ago | |
|---|---|---|
| data | 6 months ago | |
| docs | 1 month ago | |
| locale | 2 weeks ago | |
| migrations | 3 weeks ago | |
| static | 2 weeks ago | |
| templates | 2 weeks ago | |
| templatetags | 2 weeks ago | |
| .env.example | 3 weeks ago | |
| .gitignore | 2 weeks ago | |
| CODING_POLICY.md | 2 weeks ago | |
| LICENSE | 2 weeks ago | |
| README.md | 2 weeks ago | |
| RELEASE_POLICY.md | 2 weeks ago | |
| __init__.py | 3 years ago | |
| admin.py | 2 weeks ago | |
| admin_rich_text.py | 1 month ago | |
| apps.py | 3 years ago | |
| forms.py | 1 year ago | |
| license | 4 years ago | |
| models.py | 1 month ago | |
| requirements.txt | 1 month ago | |
| rich_text.py | 1 month ago | |
| tables.py | 3 months ago | |
| tests.py | 1 month ago | |
| urls.py | 6 months ago | |
| utils.py | 3 months ago | |
| views.py | 3 months ago |
The shared header shows the Publications-owned News link when sharix_publications
is installed, enabled and allows Landing display. Its optional integration helper
supplies the localized label and reverse-resolved URL; no article query or role
logic lives in Landing. Missing/older/disabled modules leave the header usable.
The public page, tag filters and default shell adapter belong to Publications.
The public feed is anonymous even for a signed-in visitor. No new Landing setting,
schema or migration is required. Keep the operational branch's migration history.
Landing migration history is branch-owned. The historic operational master
release can have divergent installation-local migrations 0001..0029. A reviewed
and sealed canonical 0030 baseline, its leaf and stage7_6_6_baseline.json
must be produced once by release maintainers using
prepare_canonical_migration_baselines in a controlled authoritative checkout
and committed in the master source. All subsequent migrations are committed in
normal order (0031+). A deployment branch such as office with a committed
independent 0001+ history retains that history, including when it merges
ordinary master commits. repositories.sh sync-operational checks for schema
changes before cross-lineage merges and permits new deployment-branch migrations
to be tracked through its branch-local migrations/.gitignore exception.
The source archive from 2026-10-14 does not contain the required canonical
Landing baseline. Merely relaxing .gitignore cannot make legacy installations
safe to upgrade; the installer must stop until the actual baseline is published.
The installer never runs makemigrations to create migrations on a server,
never fakes a migration and never erases legacy data/history. Local historical
migration source may be SHA-archived only after it is verified as applied;
actual schema must match the immutable baseline before adoption.
A Landing deployment branch with its own committed 0001+ history must retain
its branch-owned migrations. Do not copy the standard branch's 0030 into it.
See root docs/migration_baselines.md and Stage 7.6.6 release procedure.
This module owns landing/.env.example with 2 declared settings. During install/upgrade ShariX materializes conf-real/landing/.env; existing nonempty installation values are migrated from the root .env with restricted backups and commented-out history. Run the canonical conf/utils/normalize_env.py --diff, then --write, then --check from the owning webapp root. Never commit real credentials. Core/shared infrastructure variables remain with the installation.