The gt command gathers the everyday WebEngine tasks behind one interface. Rather than remembering a list of package-specific commands, you can create, run, build, test, and manage a project from one place.

It is mainly a development convenience. A production deployment does not depend on gt itself. Underneath, the project is still a normal Composer-managed PHP application.

¶Core commands

The commands you will use most often are:

• gt create to create a new project
• gt run to start the local development setup
• gt serve to run only the PHP development server
• gt build to copy or compile client-side assets
• gt test to run the project’s test suite
• gt cron to run scheduled jobs locally

You do not need to memorise every flag immediately. The important thing early on is knowing which command belongs to which kind of task.

¶Typical daily workflow

A fairly normal day with WebEngine might look like this:

1. Create a project with gt create if you are starting something new.
2. Start the app with gt run.
3. Edit the page view, page logic, or application classes.
4. Run tests with gt test.
5. If you are changing client-side assets, let gt run or gt build --watch keep them up to date.

Commands such as gt create are used occasionally, while gt run and gt test tend to become part of the normal loop.

See the full reference of gt commands, or move on to the Hello World tutorial.