smithery/netalertx

netalertx-idempotent-setup

Reprovision and reset the devcontainer environment. Use this when asked to re-run startup, reprovision, setup devcontainer, fix permissions, or reset runtime state.

Installation

$ npx skills add smithery/netalertx --skill netalertx-idempotent-setup

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/netalertx · top by installs.

npx skills add smithery/netalertx

Browse all from smithery/netalertx

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,651 B
  • docs SUMMARY.md 198 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Devcontainer Setup

The setup script forcefully resets all runtime state (services, tmpfs ramdisks, symlinks, log files) unconditionally on every run. Persistent DB/config content under /data is the one exception - it's preserved by default; see step 7 below.

Command

/workspaces/NetAlertX/.devcontainer/scripts/setup.sh

What It Does

  1. Kills all services (php-fpm, nginx, crond, python3)
  2. Mounts tmpfs ramdisks for /tmp/log, /tmp/api, /tmp/run, /tmp/nginx
  3. Creates critical subdirectories
  4. Links /entrypoint.d and /app symlinks
  5. Creates /data, /data/config, /data/db directories
  6. Creates all log files
  7. Runs /entrypoint.sh to start services - by default this preserves existing DB/config content; entrypoint.d/25-first-run-db.sh and 20-first-run-config.sh only wipe them when ALWAYSFRESHINSTALL=true is set in the environment
  8. Writes version to .VERSION

When to Use

  • After modifying setup scripts
  • After container rebuild
  • When environment is in broken state
  • To pick up a database/config reset done another way (setup.sh itself won't reset them - see step 7)

Philosophy

Runtime state (services, tmpfs, symlinks, logs) has no conditional logic - everything is recreated unconditionally, every run. DB/config are the one deliberate exception, gated behind ALWAYSFRESHINSTALL. If something in runtime state doesn't work, run setup again.