- Is ijanki/ftp-bundle a Laravel package?
- No. ijanki/ftp-bundle is a Symfony2 bundle that ships a Bundle class, DependencyInjection extension, and Resources/config service definitions targeting the Symfony 2.x container and event system, none of which Laravel's service container consumes. What is actually reusable in a Laravel app is the thin domain layer: a connection object and a client that wraps ext-ftp calls such as ftp_connect, ftp_login, ftp_put, and ftp_nlist and converts PHP warnings into exceptions.
- How do I install ijanki/ftp-bundle in a Laravel app?
- Install it with Composer using composer require ijanki/ftp-bundle, then immediately check what it pulls in with composer why symfony/* to see whether Symfony components arrive transitively. Confirm the package's PSR-0 or PSR-4 autoload mapping works in isolation, and instantiate the connection and client manually in a tinker session against a sandbox FTP endpoint before wiring anything into your app.
- How do I configure FTP credentials for ijanki/ftp-bundle in Laravel?
- There is no publishable config file, no facade, and no ServiceProvider, so you configure it yourself. Feed host, port, username, and password from config/filesystems.php or a dedicated config/ftp.php into the package's connection object, then bind the client as a singleton in AppServiceProvider behind a small interface so application code never touches the bundle's namespace directly.
- Does ijanki/ftp-bundle support Laravel 10, 11, or 12?
- There is no declared Laravel version support: the package does not ship a Laravel service provider, facade, or Laravel-specific constraints, and its last release was April 2023. The reusable FTP client layer may run on modern Laravel if your PHP version is compatible and no Symfony runtime dependencies are hard-required, but both of those need verification in your environment before you commit.
- What FTP operations does ijanki/ftp-bundle support?
- The reusable client wraps standard ext-ftp calls: connect and login, upload with ftp_put, download, directory listing with ftp_nlist, folder creation with ftp_mkdir, and deletion with ftp_delete. It is a thin wrapper rather than a full FTP abstraction, so features like recursive transfers, resume, or atomic writes are not part of the advertised API.
- Does ijanki/ftp-bundle support SFTP or FTPS?
- SFTP is not supported; the package is built on ext-ftp, so it speaks FTP only. Whether explicit or implicit FTPS, passive mode, and binary transfer mode are handled needs to be verified in the source, because plaintext FTP sends credentials over the wire and is unsuitable for production without TLS.
- Can I use ijanki/ftp-bundle as a Laravel filesystem disk driver?
- No. Laravel's filesystem abstraction expects a League\Flysystem\FilesystemAdapter, and this package does not implement one, so it cannot be registered as a disk driver without a custom adapter. If you want FTP behind Laravel's built-in ftp disk, use league/flysystem-ftp instead.
- What are the best alternatives to ijanki/ftp-bundle for FTP in Laravel?
- Use league/flysystem-ftp behind Laravel's existing ftp disk driver: it gives you the same ext-ftp behaviour with a maintained dependency, a stable API, and Laravel-native configuration. If you proceed with ijanki/ftp-bundle instead, wrap it behind your own RemoteFileTransfer interface so switching to Flysystem later is a one-line rebind in your service provider.
- Is ijanki/ftp-bundle actively maintained and safe for production?
- Its maintenance profile is low-signal: around 22 stars, 0 dependents, and a last release in April 2023, meaning no downstream population is exercising it and edge cases are unvalidated. Secondary production risks include unverified PHP 8.2/8.3 compatibility, no SFTP, and plaintext credentials unless FTPS is explicitly handled. The code surface is small enough that forking and owning it is cheap if you decide the exception semantics or connection reuse are worth it.
- How do I test an ijanki/ftp-bundle integration in a Laravel app?
- Instantiate the connection and client manually in tinker against a sandbox FTP endpoint first, then wrap them behind an interface such as RemoteFileTransfer so tests can swap in a fake instead of hitting a live server. Check the repository's test posture before relying on it, and keep all application code talking to your interface rather than iJanki namespaces so the integration stays testable and replaceable.