Skip to main content

Site Editor — Site Configuration Viewer

The Site Editor shows the raw configuration file for the currently selected site — the YAML host/inventory file that defines that deployment's network functions, infrastructure, and settings. It is a read-only, syntax-highlighted view, so you can see exactly what OmniWeb is working from for a site without opening a shell on a host.

← Operations Guide

What it shows

OmniWeb drives every site from a per-site configuration file. That file lists the site's elements (which NFs are present and at what addresses), its infrastructure hosts, its monitoring role, its fivegc block (see 5G Core), and so on — everything the sidebar, topology, element pages, and dashboards derive from.

The Site Editor loads that file for the site chosen in the top-bar site dropdown and displays it in a full editor pane (Monaco, the same editor VS Code uses) with YAML highlighting, line numbers, folding, and a minimap. The header shows the customer, the site, and the source filename.

If no site is selected, the page prompts you to pick one from the dropdown first.

Read-only by design

The Site Editor is a viewer — the pane is read-only (marked with a read-only chip in the header). It is there to inspect the effective configuration, not to change it.

Site configuration is not edited from the browser. As noted throughout this guide, OmniWeb deployment and configuration is managed via Ansible — do not edit configuration files directly on hosts, and adding or changing an element is a configuration change made through that pipeline (see the configuration model). The Site Editor lets you read the result of that pipeline for the selected site.

When to use it

  • Confirm what a site is configured with — which elements, hosts, and 5GC NFs OmniWeb thinks are present, and at which addresses.
  • Troubleshoot the UI against the config — if an element, a sidebar entry, or a 5GC section is missing or pointing at the wrong host, the raw file is the source of truth to check against.
  • Reference the exact filename and contents when preparing an Ansible change.