- How do I install melasistema/mela-cms in a Laravel application?
- Install it as a standard Composer dependency with composer require melasistema/mela-cms. Then publish any package config and assets, run migrations, and wire the admin route prefix into your application. As of v0.9.1 the core package resolves from Packagist, so you should not need a GitHub personal access token for the package itself.
- Does melasistema/mela-cms still require a GitHub token or private VCS repository?
- No for the core package as of v0.9.1: it is resolvable from Packagist rather than through a GitHub VCS repository that needed a personal access token. If your composer.json still contains a repositories block pointing at the GitHub repo, remove it, because a stale VCS entry can silently shadow Packagist. The release note does not establish that every transitive dependency is token-free, so verify in a clean CI run.
- Which PHP and Laravel versions does melasistema/mela-cms support?
- The provided release material does not state the declared php or laravel/framework constraints, so check the package composer.json on Packagist before committing to it. The technical assessment flags the missing supported LTS matrix as the largest compatibility gap. Validate against your target PHP runtime and Laravel major version in a staging app first.
- Does melasistema/mela-cms publish config and migrations, and can I uninstall it?
- It is described as following familiar Laravel conventions, which usually means publishable config and migrations, but the release note does not confirm this. Treat reversibility and clean uninstall as unverified until you inspect the package service provider and migration files. Test publish, migrate, and rollback in a disposable Laravel app before using it in an existing project.
- Is melasistema/mela-cms production-ready at v0.9.x?
- At v0.9.x it is explicitly pre-1.0, and the maintainer has reserved the right to introduce breaking changes before a 1.0 stability commitment. Expect possible churn in config keys, database schema, and public APIs. It is most defensible for greenfield or internal-tool Laravel apps, and riskier for mature applications with strict dependency governance.
- How do I upgrade melasistema/mela-cms from 0.9.0 to 0.9.1?
- The 0.9.1 change is a packaging fix rather than a code, schema, or config change. Remove the GitHub repositories VCS block and any COMPOSER_AUTH or GITHUB_TOKEN secret that existed only to satisfy that repository, then run composer update. Treat the secret removal as its own reviewed change so unrelated pipelines that share the token are not disrupted.
- Can I run melasistema/mela-cms on a cheap shared host?
- The package is positioned for exactly that: a Laravel app on inexpensive shared hosting with a clean admin panel for the client. You still need Composer 2, a supported PHP runtime, and a database for Laravel and the CMS tables. Confirm the package PHP constraint against your host before promising a deployment target.
- How does melasistema/mela-cms compare to WordPress for client sites?
- Mela CMS is not a standalone WordPress replacement; it is a Laravel package that adds content management and admin functionality to a Laravel application. The pitch is that a coding agent builds the site, the client gets a clean admin panel, and it runs on a cheap shared host. Choose it when you already want a Laravel codebase and Composer-based dependency management.
- How do I secure the Mela CMS admin panel behind authentication?
- The documented integration approach is to wire the admin route prefix behind your existing Laravel auth middleware rather than exposing it directly. That lets you reuse your application's current login, roles, and access rules. The provided material does not describe built-in role management, so verify what the package ships before relying on it for permissions.
- Who maintains melasistema/mela-cms and what support model does it use?
- It is published under the melasistema namespace with a young release history, and the assessment flags single-maintainer concentration as a bus-factor and abandonment risk. The support model is not documented in the provided material, so assume issues-only until you confirm otherwise. For long-lived client sites, plan for upgrade ownership and a fallback if maintenance stalls.