Project recipe · Beta

Abotlogixfile.json

A small, declarative project recipe that lets VPServ prepare a supported project workflow from its root folder.

What it is

Abotlogixfile.json is a VPServ project recipe placed in the project root. It describes the optional preparation commands and services VPServ should use when someone taps Run Environment.

A developer can prepare a project and its recipe. Another user can add that project to VPServ and run the prepared workflow without manually entering every setup and startup command.

Run a prepared project without using the terminal

01
Receive a prepared project from a trusted developer or project author.
02
Confirm that Abotlogixfile.json is in the project root with the exact filename and capitalization.
03
Add or open the project in VPServ.
04
Review the project configuration when it is available in the application.
05
Tap Run Environment.
06
VPServ prepares any missing supported tools identified by the configured service executables.
07
VPServ runs optional setup_commands in their listed order.
08
VPServ processes the configured services in their listed order.
09
View the available output and logs.
10
Open the configured project URL when VPServ presents one.

Execution lifecycle

01
VPServ reads Abotlogixfile.json from the selected project folder.
02
VPServ examines the configured service executables.
03
Missing supported tools for an enabled tunnel and service executables are prepared before the workflow continues.
04
Optional setup_commands run synchronously in their listed order.
05
Services are processed in their listed order.
06
A positive delay_after_start_ms applies a fixed delay after that service's launch step.
07
Existing .sql files in init_scripts use the MariaDB initialization path.
08
After the services are processed, an enabled named tunnel starts after VPServ's fixed post-service wait.
09
The user can view available output and open the configured application URL when it is presented.

Preparing a project

01
Test the project manually inside VPServ.
02
Identify the executable each long-running service needs.
03
Put one-time preparation work in optional setup_commands.
04
Put long-running processes in services.
05
Store the executable and every argument as separate JSON array items.
06
Add delay_after_start_ms only where a fixed pause is genuinely needed.
07
Use init_scripts only for supported MariaDB SQL initialization files.
08
Configure a tunnel only when the project actually needs public access.
09
Remove tokens and other secrets before sharing a project.
10
Test again from a clean VPServ installation, then explain what the recipe installs and executes.

Trust and security

Never put a real Cloudflare token, API key, password, private domain, or production credential in a public recipe.
Use placeholders in examples and templates.
Never commit secrets to GitHub or another shared repository.
Rotate a tunnel token immediately if it is exposed.