dpanel-build

Build an application artifact from a dPanel application definition.

Requirements

The target host must already have the runtime binaries required by the application definition, for example Go, Node.js, PHP, Python, Ruby, or Bun.

Role Variables

• build_id: artifact id. dPanel uses this as the build log boundary.
• build_appname: application definition filename when reading from disk.
• build_application_from_input: application definition object passed by dPanel.
• build_upload_artifact: archive/upload enabled flag.
• build_user: Linux user that runs the build.
• build_destination: cloned repository location.
• build_log: deprecated. Build command output is emitted to stdout/stderr for the dPanel Ansible callback and is no longer appended to local log files.

Each build step is read from build_application.build.target.machine.steps. Step name is used as the frontend log group label. Commands can be provided with either cmd or command.

The role emits a structured metadata marker before each command. The embedded dPanel Ansible callback removes that marker from visible logs and attaches these attributes to every output line:

• artifact_id
• build_id
• build_step_index
• build_step_number
• build_step_name
• build_step_key
• build_command_index
• build_command_number
• build_command

Dependencies

None.

Example Playbook

- hosts: servers
  roles:
     - role: dpanel-build
       build_id: 2852
       build_user: dpanel
       build_destination: /home/dpanel/apps/my-app
       build_application_from_input:
         setup:
           language:
             name: go
             version: "1.24.2"
         build:
           target:
             machine:
               workdir: "."
               steps:
                 - name: Build application from GitHub
                   command:
                     - ./scripts/build.sh

License

BSD

Author Information

An optional section for the role authors to include contact information, or a website (HTML is not allowed).