- What is romanzipp/laravel-make-file-permissions used for?
- It is a Laravel package that automatically applies unix file permissions to files and directories created by Artisan make commands. Instead of new classes, migrations, and other stubs landing with default or overly permissive modes, the package sets sensible permissions right after generation. It is aimed at teams deploying to unix servers who want to avoid manual chmod steps.
- How do I install laravel-make-file-permissions in a Laravel app?
- Install it with Composer using composer require romanzipp/laravel-make-file-permissions, but review the constraints first. Confirm PHP and illuminate/* compatibility, then pin a version such as ^1.1 only after a dependency check. Test the install in a throwaway branch before merging into your main application.
- Which Laravel versions does this package support?
- The 1.1.0 release explicitly adds Laravel 7 support, and that is the only compatibility signal available in this assessment. Whether it also works on Laravel 6 or Laravel 8 and later is not evidenced here, so check composer.json and the README before assuming. Keep in mind Laravel 7 is end-of-life, so this is a near-term fit rather than a long-term stack choice.
- Do I need to register a service provider or publish a config file?
- Standard Laravel package conventions suggest auto-discovery and no manual provider registration, but verify this against the repository README. If the package ships a publishable config, use artisan vendor:publish to review or adjust the permission modes. Do not assume config keys exist; read the source before overriding defaults.
- Which file permissions does it apply, and can I change them?
- The package is designed to apply sensible unix modes to newly generated files and directories by default. The exact mode values should be confirmed in the source or published config, which is where you would override them if supported. Compare the defaults against your server umask and deployment user before relying on them.
- Does it only affect files created by artisan make commands?
- Its scope is the output of artisan make: commands, meaning new classes, migrations, controllers, and similar stubs. Existing files and directories are not the target, so it is not a general-purpose permission fixer for your whole codebase. Plan a separate approach for legacy files that already have incorrect modes.
- Is it safe to use in production?
- Because it runs after code generation, it typically adds no runtime overhead to HTTP requests, queues, or database work. The main risk is dependency and version compatibility, not runtime behavior. Validate in staging with a rollback plan, especially since the supported Laravel 7 release is end-of-life.
- Is this package actively maintained and tested?
- The available assessment shows only a terse 1.1.0 release note with no evidence of CI, test coverage, a security policy, or long-term support. That makes maintenance risk moderate to high until you verify activity in the repository. Pin versions and track upstream releases so unexpected minor changes do not break your build.
- What are the alternatives to this package?
- You can set permissions manually with chmod, configure a restrictive umask for the deployment user, or enforce modes in deploy scripts, git hooks, or CI pipelines. Filesystem ACLs are another option for finer-grained control. This package simply automates the permission step at file generation time.
- How should I evaluate it before adopting it?
- Install it in a disposable Laravel 7 application first, then in a staging branch of the real application. Run composer why-not and your existing test suite, plus smoke tests that create files via artisan make and inspect their resulting modes. Deploy to staging or a canary with a rollback plan before using it in production.