Landing page template for Metaservices based on ShariX Open with the login button for authorization and access to open-webuser.

Шаблон посадочной страницы Метасервиса на основе ShariX Open с кнопкой авторизации для перехода к open-webuser.

ShariX Developer 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
data ea68ad345e change: delete examples of ai files to answer and comment button upload files 6 months ago
docs b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
locale 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
migrations d73c814ca0 fix migrations 3 weeks ago
static 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
templates 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
templatetags 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
.env.example f732f647fa new .env example 3 weeks ago
.gitignore 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
CODING_POLICY.md 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
LICENSE 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
README.md 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
RELEASE_POLICY.md 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
__init__.py 61544d8769 first commit 3 years ago
admin.py 08a50516a0 Reconcile common Landing changes on master; keep office design 2 weeks ago
admin_rich_text.py b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
apps.py 61544d8769 first commit 3 years ago
forms.py 5d0ca4d23a format code 1 year ago
license a39efbf2a4 license info added 4 years ago
models.py b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
requirements.txt b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
rich_text.py b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
tables.py a832672fdc strange changes 3 months ago
tests.py b68fea2d62 S92.7: publish editor-neutral Landing changes on master 1 month ago
urls.py 419bc996c8 fix import 6 months ago
utils.py a832672fdc strange changes 3 months ago
views.py a16de1b65b fix patch 3 months ago

README.md

ShariX Open Landing — migration history

Optional News navigation

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.

Module-owned runtime environment

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.