تشغيل أي مهارة في Manus بنقرة واحدة

zolinga-setup

النجوم٤

التفرعات٠

آخر تحديث٥ مايو ٢٠٢٦ في ١٨:٤٧

Use when setting up a basic Zolinga installation, checking prerequisites, fixing writable-path problems, configuring the local URL, and starting the framework for the first time.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

webdevelopers-eu

webdevelopers-eu/zolinga

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	zolinga-setup
description	Use when setting up a basic Zolinga installation, checking prerequisites, fixing writable-path problems, configuring the local URL, and starting the framework for the first time.
argument-hint	[host:port or setup goal]

Zolinga Setup

Use When

Preparing a fresh Zolinga checkout to run locally.
Fixing first-run problems such as missing permissions or wrong base URL.
Starting the built-in server or wiring the project into Apache.
Verifying that the framework bootstraps correctly before working on modules.

Workflow

Confirm the PHP version is at least 8.2.
Make sure these paths are writable by the user running PHP: /.agents/skills/, /data/, /public/data/, and /public/dist/.
Check config/local.json first, then config/global.json, for the effective baseURL.
Use bin/zolinga --help to confirm the CLI entrypoint is working.
Start the local server with bin/zolinga --server=<host>:<port>.
If you use Apache instead, generate an example config with bin/zolinga skeleton:apache ... and serve the public/ directory.
Open the local site and then visit /wiki/ to confirm the framework booted and documentation is available.
If startup fails, check writable-path errors first, then review data/system/logs/messages.log.
The framework by itself does nothing much you need modules installed to see real behavior. Use bin/zolinga install --list to see available modules and bin/zolinga install --module=<module-name> to install them.
Sensitive configuration data must never be put in module's zolinga.json files - they belong strictly only to ./config/.

Quick Checks

bin/zolinga runs without fatal bootstrap errors.
public/dist/ and public/data/ are created and writable.
Module manifests load correctly and the local wiki opens.
The configured URL matches the way the project is actually being served.

Troubleshooting

If bootstrap reports permission errors, fix ownership or write access for the required directories.
If the site opens on the wrong host or port, re-check baseURL and how the server was started.
If module assets are missing, run bin/zolinga (no parameters) to trigger the install/update flow so public/dist/{module} symlinks are refreshed.
If a module behaves as if it is not loaded, inspect data/system/system.cache.json and the module zolinga.json file.

References

README.md
system/wiki/Zolinga Core/Running the System.md
system/wiki/Zolinga Core/Running the System/Command Line.md
system/wiki/Zolinga Core/Module Installation and Updates.md
system/wiki/ref/event/skeleton/apache.md
system/src/Loader/Bootstrap.php

المزيد من هذا المستودع

نفس المستودع

system-create-mcp-resource

webdevelopers-eu/zolinga

Use when creating or updating MCP resources — static files exposed to MCP clients via `resources/list` and `resources/read`. Covers `.meta.json` descriptors, URI rewriting, dynamic resources via `mcp:resources/list` event hook, and the `mcp-system` scheme.

2026-07-224

system-convert-remote-event-to-mcp-tool

webdevelopers-eu/zolinga

Use when exposing an existing `origin: ["remote"]` listener as an MCP tool without rewriting the handler. Covers the one-line manifest pattern that re-uses the same class+method, plus the minimal schema work needed to satisfy `McpToolsListHandler::collectTools()`. Complements system-create-mcp-tool (which covers the greenfield case).

2026-07-214

system-create-mcp-tool

webdevelopers-eu/zolinga

Use when exposing a Zolinga event handler as an MCP (Model Context Protocol) tool — i.e. a method clients can invoke via JSON-RPC `tools/call`. Covers handler class, manifest binding, JSON Schemas, the `Tools\CallEvent` contract, and the `schema.response` requirement enforced by `McpToolsListHandler::collectTools()`.

2026-07-214

system-events-client

webdevelopers-eu/zolinga

Use when working with the JavaScript client-side event system in Zolinga. Covers the Event class, Api gateway, dispatching events from JS to PHP, receiving broadcastBack responses, inter-component communication via BroadcastChannel, and web component integration.

2026-07-154

system-translations

webdevelopers-eu/zolinga

Use when adding localized strings in PHP or HTML, including gettext usage patterns and context-aware translation strings for Zolinga Intl.

2026-07-064

system-php-coding-style

webdevelopers-eu/zolinga

Use when writing or reviewing PHP code in this repository to enforce strict typing, naming, file layout, and listener/service interface conventions.

2026-06-274

Zolinga Setup

Use When

Preparing a fresh Zolinga checkout to run locally.

Fixing first-run problems such as missing permissions or wrong base URL.

Starting the built-in server or wiring the project into Apache.

Verifying that the framework bootstraps correctly before working on modules.

Workflow

Confirm the PHP version is at least 8.2.

Make sure these paths are writable by the user running PHP: /.agents/skills/, /data/, /public/data/, and /public/dist/.

Check config/local.json first, then config/global.json, for the effective baseURL.

Use bin/zolinga --help to confirm the CLI entrypoint is working.

Start the local server with bin/zolinga --server=<host>:<port>.

If you use Apache instead, generate an example config with bin/zolinga skeleton:apache ... and serve the public/ directory.

Open the local site and then visit /wiki/ to confirm the framework booted and documentation is available.

If startup fails, check writable-path errors first, then review data/system/logs/messages.log.

The framework by itself does nothing much you need modules installed to see real behavior. Use bin/zolinga install --list to see available modules and bin/zolinga install --module=<module-name> to install them.

Sensitive configuration data must never be put in module's zolinga.json files - they belong strictly only to ./config/.

Quick Checks

bin/zolinga runs without fatal bootstrap errors.

public/dist/ and public/data/ are created and writable.

Module manifests load correctly and the local wiki opens.

The configured URL matches the way the project is actually being served.

Troubleshooting

If bootstrap reports permission errors, fix ownership or write access for the required directories.

If the site opens on the wrong host or port, re-check baseURL and how the server was started.

If module assets are missing, run bin/zolinga (no parameters) to trigger the install/update flow so public/dist/{module} symlinks are refreshed.

If a module behaves as if it is not loaded, inspect data/system/system.cache.json and the module zolinga.json file.

References

README.md

system/wiki/Zolinga Core/Running the System.md

system/wiki/Zolinga Core/Running the System/Command Line.md

system/wiki/Zolinga Core/Module Installation and Updates.md

system/wiki/ref/event/skeleton/apache.md

system/src/Loader/Bootstrap.php