- What is aichadigital/lara100 and what does it do?
- Lara100 is a Laravel package by aichadigital that provides a simple, configurable toolkit for common application needs. It follows Laravel conventions and is designed to reduce boilerplate so teams can build and maintain PHP applications faster. The Composer package is a distribution mirror, with active development happening on the project's GitLab repository.
- How do I install aichadigital/lara100 with Composer?
- Install it like any other Laravel package by running composer require aichadigital/lara100 from your project root. Because the package is distributed as a mirror, Composer will pull the tagged release rather than a development branch. After installation, check the package README for any publishable config or migration steps.
- Which Laravel versions does lara100 support?
- The supported Laravel and PHP version constraints are declared in the package's composer.json require section. Check that file or the GitLab repository before adding lara100 to an existing application. If your Laravel version falls outside the constraint, Composer will refuse the install and tell you which requirement conflicts.
- Why is the GitHub repository read-only with no issues or pull requests?
- The GitHub repository is only a distribution mirror used to serve the package to Composer and Packagist. Development, issue tracking, and merge requests all happen on gitlab.castris.com/aichadigital/lara100. Open issues or merge requests there rather than on the mirror, since the mirror accepts no PRs and runs no CI.
- How do I report a bug or request a feature for lara100?
- File your report on the GitLab repository at gitlab.castris.com/aichadigital/lara100, which is the canonical development home. Include your Laravel and PHP versions plus a minimal reproduction so the maintainer can act quickly. Issues opened against the read-only distribution mirror will not be seen.
- How do I configure lara100 after installing it?
- Most Laravel packages of this type ship a publishable configuration file, typically exposed via php artisan vendor:publish. Run vendor:publish and select the lara100 provider tag if one is documented in the README. Configuration values should live in your .env file where possible so they stay out of version control.
- Is lara100 safe to use in production?
- Lara100 is a conventional Composer package with no unusual runtime requirements, so it can be used in production like any Laravel dependency. Pin a specific version in composer.json and commit your composer.lock so deployments are reproducible. Test the upgrade path in staging before bumping the constraint, since mirror releases may land without the usual GitHub CI signals.
- How do I write tests for code that uses lara100?
- Because it is a standard Laravel package, you can test against it with your normal PHPUnit or Pest setup inside a Laravel application. For package-level testing, the orchestra/testbench convention usually applies if the repository ships a test suite. Always clear the config cache between tests when your assertions depend on published configuration values.
- Does lara100 support Laravel package auto-discovery?
- Laravel package auto-discovery applies when a package declares an extra.laravel providers entry in its composer.json. Check that file in the installed vendor/aichadigital/lara100 directory to confirm whether manual provider registration is needed. If auto-discovery is not declared, add the service provider to the providers array in config/app.php.
- Who maintains lara100 and how actively is it developed?
- The package is maintained by aichadigital, with all development activity hosted on gitlab.castris.com/aichadigital/lara100. The GitHub mirror is read-only, so commit history and release notes are best reviewed on GitLab. Check the repository's recent commits and tags there before adopting the package for a long-lived project.