VPServBeta
Documentation menu

Start here

Documentation homeGetting started

Project recipes

Abotlogixfile.jsonField referenceExamples

Workflows

Tools ManagerAdvanced terminalTroubleshooting
On this page
  1. Choose your path
  2. Guided application
  3. Project developers
  4. Advanced terminal

VPServ documentation

Get started with VPServ

Choose the workflow that fits you: a guided Android application flow, a repeatable project recipe, or optional advanced terminal control.

VPServ is a Beta Android developer environment with a guided application interface and an optional Linux-style terminal. A prepared project can be run through the app; terminal knowledge is not required for that workflow.

Choose the workflow that fits the project

PathBest forWhat you use
Guided applicationPrepared projectsGlobal Tools Manager, Projects, Run Environment, logs
Project developerReusable project setupAbotlogixfile.json, services, optional setup commands
Advanced terminalManual control and debuggingpkg, vpkg, custom commands, direct output

Guided application users

  1. 01

    Open VPServ.

  2. 02

    Open Global Tools Manager. VPServ retrieves the supported tool catalog from its server and shows available tools, versions, installation state, and supported daemon-tool state.

  3. 03

    Select a supported tool and tap Install. VPServ retrieves its manifest, manages the required dependencies, and shows installation progress and logs.

  4. 04

    Add or open a prepared project. Review its configured environment, files, and folders when available.

  5. 05

    Tap Run Environment. VPServ reads Abotlogixfile.json from the selected project root when the prepared project includes it.

  6. 06

    View the available execution output and logs.

  7. 07

    Open the configured project URL when VPServ presents one.

Project developers

  1. 01

    Test the project manually inside VPServ first.

  2. 02

    Add Abotlogixfile.json, with this exact capitalization, to the project root.

  3. 03

    Define only the optional setup commands the project needs before services start.

  4. 04

    Define each long-running process as a service, using an executable and separate argument-array items.

  5. 05

    Add a fixed startup delay only when the next stage needs time; it is not a health check.

  6. 06

    Add MariaDB SQL initialization files through init_scripts only when the project uses that supported path.

  7. 07

    Configure a named Cloudflare tunnel only when public access is required.

  8. 08

    Test from a clean VPServ installation and explain what the project will install and execute before sharing it.

Advanced terminal users

Open the local VPServ terminal when you want manual control. You can use pkg or vpkg for supported-tool workflows, run custom commands, and inspect direct output while you debug a project. This path complements a prepared application workflow; it does not replace it.

Illustrative terminal workflow
pkg install <supported-tool>

# Then run the command your project needs
<project-command>