Overview

In Arpia AI Workshop, you can create objects in either PHP or Python, depending on your coding preference.

This feature allows object creators to add an interactive configuration interface using a config.html file.
Instead of editing code directly, builders can configure an object through a form, with values passed directly to the startup script (index.py or index.php) at runtime.

Objects without a config.html file work exactly as before—opening in the file/code editor view.

---

Object Types

An object must be one of the following:

• Python — Startup file: index.py
• PHP — Startup file: index.php

The startup file is required and serves as the entry point for execution. It can import or include other files within the same object.

---

Configuration UI (config.html)

If an object contains config.html:

• The Workshop viewer renders it as an interactive configuration form.
• Inputs are sent directly to the startup script at execution time.
• You can still access View Code Mode to see and edit the object’s files.

If config.html is absent, the object opens in Code Mode by default.

Common Use Cases

Workshop objects with a config.html interface are ideal for scenarios where you want non-technical users—or even yourself—to adjust parameters without editing code. Examples include:

• Data Transformation Pipelines — Let users select data sources, filters, or transformation rules before processing.
• API Integration Configurations — Collect authentication keys, endpoints, and query parameters via form inputs.
• AI & Machine Learning Parameters — Adjust model settings, thresholds, or prompts before execution.
• Automation & Task Runners — Schedule or parameterize recurring backend tasks without code changes.
• Environment-Specific Settings — Switch between dev, staging, and production values dynamically.

---

Benefits

• Flexibility — Choose PHP or Python based on your workflow.
• Ease of Use — Configure via forms instead of editing code.
• Predictable Execution — Always starts from a single entry file.
• Modularity — Startup scripts can use helper files and libraries.
• Backward Compatibility — Works exactly as before if no config.html is present.

---

Summary Table