Weave Code
Asgardcms Installer Laravel Package
asgardcms/asgardcms-installer
The official command-line installer for AsgardCMS, letting you scaffold a new modular, multilingual Laravel CMS project quickly. Handles package setup and initial configuration so you can start building content-driven sites right away.
AsgardCms installer
Frequently asked questions about Asgardcms Installer
- How do I install AsgardCMS using the official installer?
- Install it globally with composer global require asgardcms/asgardcms-installer, make sure your global Composer bin directory is on your PATH, then run asgardcms new and follow the prompts. The command shells out to composer create-project asgardcms/platform and then starts the platform's own installer.
- Do I need to require asgardcms/asgardcms-installer in my project's composer.json?
- No. It is a disposable scaffolding tool, not a runtime dependency. Installing it globally keeps it out of your application's composer.json and vendor directory; once the project is created, the installer has no presence in the codebase.
- Which Laravel and PHP versions does the AsgardCMS installer support?
- The installer bootstraps the AsgardCMS platform, which targets the Laravel 5.4 to 5.7 and PHP 7.1 to 7.4 era. It is not a supported path for Laravel 9, 10, 11, or PHP 8.1+. Treat version pairing as an explicit decision and verify constraints before running.
- Can I use the AsgardCMS installer on an existing Laravel application?
- No. It is greenfield-only tooling built around composer create-project, so it cannot augment or drop into an existing Laravel application. If you already have a Laravel app, this package is out of scope by definition.
- What does the AsgardCMS installer actually do during project creation?
- It runs composer create-project asgardcms/platform <name>, then hands off to the platform's interactive installer for package setup and initial configuration. The resulting project is pinned to the AsgardCMS platform and its legacy Laravel baseline.
- Why does the AsgardCMS installer hang or fail in CI?
- The platform installer is interactive, so prompts can fail or hang in non-TTY CI environments and produce silent partial installs. Run it only in a disposable container or on a developer machine with a TTY, and never in a shared build agent where it writes into the current working directory.
- Is AsgardCMS still maintained and safe for production?
- The ecosystem is effectively dormant: low star count, no upstream CVE response, and no fixes for Composer 2 or PHP 8. Running it in production means accepting an end-of-life Laravel version and abandoned transitive packages. For a new build, use it at most for a timeboxed capability evaluation.
- Does the AsgardCMS installer work with PHP 8 and Composer 2?
- Not reliably. AsgardCMS predates Composer 2 and modern PHP, so constraint resolution and create-project behavior may break. Use a PHP 7.x container with the matching Composer version, and pin exact versions before a second run.
- What are the alternatives to AsgardCMS for a modular Laravel CMS?
- If the value is modularity, pair nwidart/laravel-modules with a maintained admin panel such as Filament or Nova on a supported Laravel release. That preserves the module concept while discarding the legacy CMS wrapper. Forking asgardcms/platform is effectively a rewrite across six Laravel majors.
- How do I uninstall the AsgardCMS global installer and clean up?
- Remove it with composer global remove asgardcms/asgardcms-installer and confirm the binary is gone from your global bin directory. Global installs can cause bin-dir conflicts and version drift, so clean up CI images and onboarding scripts that reference it.
Weaver
How can I help you explore Laravel packages today?