- Does elendev/roxyfileman-bundle work with Laravel?
- No. It is a Symfony 2 bundle registered in AppKernel with YAML routing and Symfony DI service definitions. There is no Laravel service provider, config/roxyfileman.php, facade, or publishable assets, so it cannot be installed as a normal Composer package in a Laravel app. Using it would require booting Symfony's container or rewriting the integration layer.
- How do I install elendev/roxyfileman-bundle?
- In Symfony 2 you require elendev/roxyfileman-bundle:~1.0 in composer.json, register ElendevRoxyFilemanBundle in AppKernel, import its routing.yml with a prefix, and configure elendev_roxy_fileman. For Laravel there is no supported installation path. RoxyFileman itself is also a standalone distribution outside Composer.
- Which Laravel and PHP versions are supported?
- None for Laravel. The package targets Symfony 2/3 and was last released on 2018-03-11, so it will not run on PHP 8.x without work. Laravel 10/11 and PHP 8.2+ are incompatible out of the box.
- Can I use it for CKEditor or TinyMCE image uploads in Laravel?
- Its stated use case is Roxyfileman integration mainly for CKEditor and TinyMCE, and it works with IvoryCKEditorBundle in Symfony. In Laravel you would need to reimplement route registration and the browse/upload endpoints behind auth middleware. For a narrow upload, browse, and insert need, a small Laravel controller is often simpler.
- How do I configure file paths and URLs?
- With the default LocalFileSystem you set local_file_system.base_path to an absolute directory and base_url to the URL prefix appended to relative file paths. Additional Roxyfileman options go under conf, such as dirlist_route and files_root. The bundle maps RoxyFileman's file paths to a host directory through this configuration.
- Does it support multiple profiles or custom filesystem services?
- Yes, the bundle documents multiple profiles and a custom filesystem service. That lets you map different Roxyfileman configurations or swap the local filesystem for another implementation. In Laravel terms this would be config profiles plus a Storage-backed adapter, which you would have to build yourself.
- Is it safe to expose Roxyfileman routes in production?
- Treat it as an untrusted upload component until it has been independently reviewed. The README says to add the route prefix to your firewall, which delegates a key security control to the integrator. PHP file managers have a long history of unrestricted-upload, extension-bypass, and path-traversal findings. An unmaintained upload endpoint becomes your CVE surface, not a vendor's.
- Can it store files on S3 or use Laravel Storage and Flysystem?
- Not directly. The bundle's filesystem abstraction predates Flysystem-era Laravel disks and is Symfony DI based. Moving to S3 or Laravel Storage is a rewrite of the adapter, not a configuration change. You would need a new Laravel package with a Storage-backed filesystem service.
- Is elendev/roxyfileman-bundle maintained?
- No. The last release was 2018-03-11, with 3 stars and 0 dependents, and the linked IvoryCKEditorBundle is also abandoned. That means little community testing or bug surfacing. RoxyFileman itself ships outside Composer, so there is no lockfile pinning or composer audit coverage. Plan for fork ownership and security patching if you use any part of it.
- What are the alternatives or migration path to Laravel?
- Do not adopt it as a dependency; use it as a design reference at most. Porting the glue means a Laravel service provider, config/roxyfileman.php with profiles, routes behind auth/can middleware, and a Storage-backed adapter, roughly 300 to 600 lines plus tests. Alternatively, adopt a maintained Laravel-native media or file-manager package, or Spatie Media Library with an upload UI.