Laraboot/Cli
CommunityExtendig
1.0.0
1.0.0
  • Introduction
  • Requirements
  • Getting started
  • F.A.Q
  • Concepts
    • Workspace
    • laraboot.json
    • Build tasks
      • Core tasks
      • Community tasks
  • Usage
    • Create a project
    • Configure
      • Data model
      • Configure
      • Starter kits
      • Views and layouts
    • Build your project
    • Run your project
    • Share your project
  • Build
    • Process
    • Hooks
  • Tutorials
    • Create a laraboot application
    • Collaborative
  • Extending
    • Create a build task
    • Github actions
    • Publish a build task
Powered by GitBook
On this page
  • Adding a build task to the project
  • Core build tasks
  • Community build tasks

Was this helpful?

  1. Concepts

Build tasks

Previouslaraboot.jsonNextCore tasks

Last updated 3 years ago

Was this helpful?

Build tasks are the fuel that propels Laraboot. A build task is a small piece of logic that is sequentially called at its own time and performs an operation against or based on the status of the workspace and the project configuration.

There are two types of build tasks, , and . The latter sits over the former.

Adding a build task to the project

Build tasks can be added via CLI using the task add command which has the following structure:

laraboot task add <name> [options]

Core build tasks

can be added by specifying their name.

# For instance
laraboot task add @core/laravel-foundation-provider --format=file

Community build tasks

These tasks do not form part of the core and are maintained by the community.

Community tasks can be added by specifying their name and id. This information is often found on the build task homepage.

# For instance
laraboot task add hello-task --buildTaskID xxxxxxxx

core
community
Core tasks