NAME
Developer::Dashboard::FileRegistry - logical file registry for Developer Dashboard
SYNOPSIS
my $files = Developer::Dashboard::FileRegistry->new(paths => $paths);
my $json = $files->read('global_config');DESCRIPTION
This module maps logical file names to concrete runtime files and provides small convenience methods for reading and writing them.
METHODS
new
Construct a registry bound to a path registry.
resolve_file, read, write, append, touch, remove
Resolve and manage named files.
prompt_log, collector_log, dashboard_log, global_config, dashboard_index, auth_log, web_pid, web_state
Return known runtime file paths.
PURPOSE
Perl module in the Developer Dashboard codebase. This file resolves named runtime files and keeps file-backed resources consistent. Open this file when you need the implementation, regression coverage, or runtime entrypoint for that responsibility rather than guessing which part of the tree owns it.
WHY IT EXISTS
It exists to keep this responsibility in reusable Perl code instead of hiding it in the thin dashboard switchboard, bookmark text, or duplicated helper scripts. That separation makes the runtime easier to test, safer to change, and easier for contributors to navigate.
WHEN TO USE
Use this file when you are changing the underlying runtime behaviour it owns, when you need to call its routines from another part of the project, or when a failing test points at this module as the real owner of the bug.
HOW TO USE
Load Developer::Dashboard::FileRegistry from Perl code under lib/ or from a focused test, then use the public routines documented in the inline function comments and existing SYNOPSIS/METHODS sections. This file is not a standalone executable.
WHAT USES IT
This file is used by whichever runtime path owns this responsibility: the public dashboard entrypoint, staged private helper scripts under share/private-cli/, the web runtime, update flows, and the focused regression tests under t/.
EXAMPLES
perl -Ilib -MDeveloper::Dashboard::FileRegistry -e 'print qq{loaded\n}'That example is only a quick load check. For real usage, follow the public routines already described in the inline code comments and any existing SYNOPSIS section.