Status Addon

[sayamcoder]

Summary by CodeRabbit

• New Features
  • Status Page addon is now available with node monitoring and incident logging capabilities.
• Documentation
  • Added installation guide for the Status Page addon setup and configuration process.

[coderabbitai]

Walkthrough

Two JSON files are added to define and document the Status Page addon: info.json contains addon metadata, features, and source links, while install.json provides installation and build steps for the AirLink panel.

Changes

Status Page Addon Documentation

Layer / File(s)	Summary
Status Page addon metadata and installation guide status-page/info.json, status-page/install.json	Addon metadata defines the Status Page name (v1.0.0), author, description, icon, and feature list (node monitoring, incident logging). Installation guide provides three steps: clone the addon, run npm install and npm run build, and restart the airlink-panel service, with a note on required addSidebarItem API support.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

📋 A status page addon, fresh and bright,
With metadata gleaming and docs shining right,
Install steps guide you through build and deploy,
Monitoring nodes fills the heart with great joy! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Status Addon' is vague and generic, lacking specificity about what the addon does or what changes are being introduced.	Consider a more descriptive title that clarifies the addon's purpose, such as 'Add Status Page addon with installation guide' or 'Introduce Status Page addon for node monitoring'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@status-page/info.json`:
- Line 20: The install note key "installNote" currently claims a restart is
required "for database migrations" but no migration step exists in install.json;
update the "installNote" string to either (a) include the explicit migration
command that operators must run (add that migration step into install.json as
well) or (b) remove/adjust the reference to migrations so it only instructs
restarting for sidebar items; modify the "installNote" entry and, if adding a
migration, add the corresponding step into install.json so the note matches the
actual installation steps.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 250de2b7-f565-40ac-8dd4-36ce9ef59b87

📥 Commits

Reviewing files that changed from the base of the PR and between b710357 and cc21a5e.

📒 Files selected for processing (2)

• status-page/info.json
• status-page/install.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify migration wording in installNote or add the migration step.

Line 20 says restart is needed “for database migrations,” but status-page/install.json does not include a migration command. This can mislead operators during installation.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@status-page/info.json` at line 20, The install note key "installNote"
currently claims a restart is required "for database migrations" but no
migration step exists in install.json; update the "installNote" string to either
(a) include the explicit migration command that operators must run (add that
migration step into install.json as well) or (b) remove/adjust the reference to
migrations so it only instructs restarting for sidebar items; modify the
"installNote" entry and, if adding a migration, add the corresponding step into
install.json so the note matches the actual installation steps.

[sayamcoder]

i ma working on new addons