Weave Code
Cli Laravel Package
aerocommerce/cli
AeroCommerce CLI gives Laravel developers a command-line toolkit for the AeroCommerce e-commerce platform: scaffold stores, run migrations and seeders, manage products, orders and configuration, and automate routine setup and maintenance tasks straight from the terminal.
AeroCommerce CLI provides the command-line tooling needed to install and manage an AeroCommerce storefront on top of Laravel. It streamlines setup by scaffolding configuration, running migrations, and publishing required assets, so you can go from a fresh Laravel app to a working store with a single command.
- One-command AeroCommerce installation and scaffolding
- Artisan commands for publishing config and assets
- Automated database migrations and seeders
- Environment setup helpers for local and production
- Extensible command structure for custom store workflows
Frequently asked questions about Cli
- What is aerocommerce/cli and what does it do?
- It is the command line installer for AeroCommerce projects, giving Laravel and PHP developers terminal access to common setup and store management tasks. Its scriptable interface makes it useful for local development workflows and CI pipelines, not just one-off installs.
- How do I install aerocommerce/cli with Composer?
- Install it with Composer from your project root, for example composer require aerocommerce/cli, then invoke the binary it provides from vendor/bin. Check the repository README for the exact package name, binary name, and available commands, since these can change between releases.
- Should I install aerocommerce/cli as a dev dependency?
- Because it is command line tooling for setting up and managing AeroCommerce projects, it usually belongs under require-dev rather than in production dependencies. Keeping it out of production reduces the packages shipped to your live store while still giving every developer and CI job access to the same commands.
- Which Laravel and PHP versions does aerocommerce/cli support?
- Version constraints are declared in the package's composer.json, so check that file and the AeroCommerce documentation for the supported PHP and Laravel ranges. Because AeroCommerce tracks Laravel releases closely, match the CLI version to your application's framework version and test upgrades in a staging branch first.
- Can I run aerocommerce/cli commands in CI/CD pipelines?
- Yes, the CLI is designed to be scriptable, so you can call it from shell steps in GitHub Actions, GitLab CI, or similar pipelines. Use non-interactive flags where available and avoid commands that write to production data; run install or setup steps against disposable environments.
- How do I update aerocommerce/cli to the latest version?
- Run composer update aerocommerce/cli to pull the newest release allowed by your version constraint, then clear any cached config or compiled files your workflow relies on. Review the changelog and tag history on the repository before jumping major versions, and commit the updated lock file so teammates and CI use identical builds.
- Is aerocommerce/cli the same as the AeroCommerce storefront package?
- No. aerocommerce/cli only provides the command line installer and developer tooling; the storefront, admin, and commerce features come from the AeroCommerce application packages. You still need a Laravel application with the AeroCommerce platform installed for the CLI to operate on.
- Can I use aerocommerce/cli to install AeroCommerce into an existing Laravel application?
- The package is primarily an installer for AeroCommerce projects, so its commands expect a project laid out the way AeroCommerce expects. Installing into an existing Laravel app only works when that app's structure matches those assumptions, so review the documented requirements and back up your code before running setup commands.
- What should I do if an aerocommerce/cli command fails or is not found?
- First confirm the binary exists in vendor/bin and that Composer install finished without conflicts, then rerun the command with verbose output to see the underlying error. If the command name is not recognized, list the commands the CLI offers, since names can change between versions. After that, check the repository's open issues for the same error.
- Where can I get support or report bugs for aerocommerce/cli?
- Use the GitHub repository's issue tracker for bug reports and feature requests, and consult the AeroCommerce documentation for setup guidance. Include your PHP, Laravel, and aerocommerce/cli versions plus the full command output when opening an issue.
Weaver
How can I help you explore Laravel packages today?