CtrlK
BlogDocsLog inGet started
Tessl Logo

project-navigation

Reference for the NetAlertX codebase structure, key file paths, and configuration locations. Use this when exploring the codebase or looking for specific components like the backend entry point, frontend files, or database location.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Project Navigation

Key Paths

ComponentPath
Workspace root/workspaces/NetAlertX
Backend entryserver/__main__.py
API serverserver/api_server/api_server_start.py
Plugin systemserver/plugin.py
Initializationserver/initialise.py
Frontendfront/
Frontend JSfront/js/common.js
Frontend PHPfront/php/server/*.php
Pluginsfront/plugins/
Plugin templatefront/plugins/__template
Database helpersserver/db/db_helper.py
Device modelserver/models/device_instance.py
Messagingserver/messaging/
Workflowsserver/workflows/

Architecture

NetAlertX uses a frontend–backend architecture: the frontend runs on PHP + Nginx (see front/), the backend is implemented in Python (see server/), and scheduled tasks are managed by a supercronic scheduler.

Runtime Paths

DataPath
Config (runtime)/data/config/app.conf
Config (default)back/app.conf
Database/data/db/app.db
API JSON cache/tmp/api/*.json
Logs/tmp/log/
Plugin logs/tmp/log/plugins/

Environment Variables

Use these instead of hardcoding paths:

  • NETALERTX_DB
  • NETALERTX_LOG
  • NETALERTX_CONFIG
  • NETALERTX_DATA
  • NETALERTX_APP

Documentation

TopicPath
Plugin developmentdocs/PLUGINS_DEV.md
System settingsdocs/SETTINGS_SYSTEM.md
API docsdocs/API_*.md
Debug guidesdocs/DEBUG_*.md
Repository
netalertx/NetAlertX
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.