web-info

Report Apache runtime status, published 1C bases, and recent error.log entries.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill web-info-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-info
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/web-info
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill web-info-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psutil, and includes scripts (resource) components.

What problem does it solve?

This Skill resolves operational uncertainty about the local 1C web stack by checking whether Apache is installed and running, what 1C databases are published, and what the most recent web/server errors are.

Core Features & Use Cases

  • Apache runtime status: Detects whether httpd.exe from the configured Apache directory is running and reports PID(s).
  • Published 1C bases discovery: Parses httpd.conf publication blocks and reads each publication’s default.vrd to display published information and the likely service types (WS/HTTP/OData) and the external URL.
  • Diagnostics from error log: Reads the last lines from logs/error.log to help troubleshoot failed requests or publishing issues.
  • Typical use case: When developers report that a previously working 1C web endpoint stopped responding, use this Skill to quickly confirm Apache status, verify which bases are published, and inspect the latest error messages.

Quick Start

Ask the Skill to show Apache and 1C publication status for the default Apache path in this project.

Frequently Asked Questions about web-info

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if Apache is running and list published 1C bases?

To check Apache status and list 1C bases, you can parse httpd.conf publication markers and read default.vrd files. This process detects running httpd.exe processes by PID and displays published database metadata alongside their likely WS, HTTP, or OData service types.

How do I troubleshoot 1C web publication issues when endpoints stop responding?

To troubleshoot 1C web publication issues, read the latest lines from the Apache logs/error.log file. Combining this error log tail with a status check of the Apache runtime and a review of currently published bases isolates the cause of failed local web requests.

What is the best way to discover which 1C databases are published on a local Apache server?

Discovering published 1C databases involves parsing httpd.conf publication blocks and extracting metadata from each publication's default.vrd file. This reveals the specific published information, external URLs, and service types configured for the local web endpoints.

Can I use this approach to verify Apache and 1C publications on my local server?

Yes, you can verify local Apache and 1C publications by checking if httpd.exe is running and reading project configuration to select the Apache root. The process requires the psutil dependency to accurately detect running processes and report their PIDs.

Why does my 1C web endpoint return errors after restarting Apache?

If your 1C web endpoint returns errors after restarting Apache, inspect the recent messages in logs/error.log. Parsing the httpd.conf file confirms whether the publication blocks and default.vrd metadata are correctly configured for the expected port and URL paths.