- How do I install dbravoan/dbcms on Plesk or cPanel?
- Download the dbcms-installer-v1.2.0.zip from the GitHub release, upload and extract it on your Plesk or cPanel host, then open your domain in a browser and complete the setup wizard. The v1.2.0 release notes say no Composer, Node, Artisan, or SSH is required. Make sure the target directory is writable and the panel's PHP execution limits are sufficient for the installer's migrations.
- Can I install dbravoan/dbcms with composer require in an existing Laravel app?
- dbravoan/dbcms is not positioned as a library you require into an existing Laravel application. v1.2.0 is distributed as a self-contained installer ZIP for Plesk/cPanel plus a source tree for Composer-based development, and the technical assessment says integration into an existing Laravel codebase is not the intended path. If you need a CMS as a dependency, evaluate dedicated Composer-installable Laravel CMS packages instead.
- Which Laravel and PHP versions does dbravoan/dbcms support?
- The v1.2.0 release notes do not state supported Laravel, PHP, or database versions. The assessment assumes a standard Laravel LAMP/LEMP stack with MySQL or MariaDB, but that is not confirmed by the release notes. Verify requirements with the project documentation before deploying, especially on managed panels where PHP versions and extensions are fixed.
- How do I upgrade dbravoan/dbcms from v1.1.0 to v1.2.0?
- There is no documented upgrade procedure for moving an existing v1.1.0 installation to v1.2.0; the release notes describe a fresh install only. It is not stated whether the installer ZIP performs in-place upgrades or preserves .env, storage, and uploaded assets. Back up files and database, test on a staging copy, and treat the upgrade as unsupported until the maintainer publishes steps.
- Is the GitHub Source code zip the dbravoan/dbcms installer?
- No. The v1.2.0 release notes explicitly say GitHub's auto-generated Source code (zip) and Source code (tar.gz) artifacts are not installers. You must use dbcms-installer-v1.2.0.zip for the intended Plesk/cPanel deployment. CI or CD pipelines that pull release tarballs from the GitHub API will silently produce a broken deployment.
- Does dbravoan/dbcms work on shared hosting without SSH or Node?
- Yes, the v1.2.0 distribution is designed for shared hosting and reseller panels such as Plesk and cPanel, with pre-built front-end assets and a browser-driven setup wizard. That removes the usual Node and SSH blockers. Watch for PHP execution time limits during migrations and confirm that the installer has writable filesystem permissions on your panel.
- Is dbravoan/dbcms documentation available in English?
- The v1.2.0 release notes are Spanish-only, and an English version of the install or upgrade documentation is not mentioned. For multi-region teams this adds translation overhead and raises misconfiguration risk during installation. Ask the maintainer whether English documentation is planned before standardizing on the package.
- Is there a CLI or headless deployment path for dbravoan/dbcms?
- No supported CLI or headless deployment path is documented. The described execution model is a browser-based installer for Plesk/cPanel, which implies migrations and setup run through the web entry point rather than Artisan. Teams with SSH may use the source tree, but reproducible CLI deploys should not be assumed without confirmation from the maintainer.
- Is the dbravoan/dbcms installer ZIP checksummed or signed?
- The release notes do not mention a checksum or signature for the installer ZIP. Manually downloaded ZIPs bypass Composer lock-file hash pinning, so artifact provenance should be verified independently. Record your own checksum, compare downloads against the GitHub release source, and avoid automating unverified ZIP pulls.
- What are alternatives to dbravoan/dbcms, and what is its release cadence?
- The project does not publish a semantic versioning statement, a full changelog, or a security-disclosure channel, so release cadence and backward-compatibility guarantees are unclear from v1.2.0 alone. Alternatives are Laravel CMS packages distributed as Composer libraries with versioned changelogs and lock-file pinning, which suit teams wanting reproducible dependency management. Choose DBCMS when you need a hosted full application on shared hosting, and a Composer library when you need drop-in integration.