Weave Code
Phpcr Shell Laravel Package
phpcr/phpcr-shell
Command-line shell for PHPCR repositories. Build and run as a PHAR for easy distribution, and use it to connect to a PHP Content Repository, browse nodes, and execute repository commands. Documentation available on Read the Docs.
PHPCR Shell
Frequently asked questions about Phpcr Shell
- Can I use phpcr/phpcr-shell in a Laravel project without Symfony components?
- Yes, but only if your Laravel app relies on PHPCR/JCR (e.g., Jackrabbit, ModeShape) for content storage. The shell is a standalone CLI tool and doesn’t require Symfony. However, Symfony 8 compatibility (v1.7.0) may indirectly help if you’re using Symfony’s HTTP Client to proxy PHPCR API calls in Laravel.
- How do I install and run phpcr/phpcr-shell in Laravel?
- The package is distributed as a PHAR file. Build it using Box (`box build` in the project root), then copy the generated `phpcrsh.phar` to your system’s `bin` directory (e.g., `/usr/local/bin/phpcrsh`). No Composer installation is needed—it’s a standalone executable. Ensure the PHP extension `phpcr` and a Java runtime (for Jackrabbit/ModeShape) are installed.
- Does phpcr/phpcr-shell work with Laravel’s Eloquent ORM?
- No, this package is not a replacement for Eloquent. It’s designed for PHPCR/JCR repositories, which use a hierarchical node-based model (e.g., for CMS or DAM systems). If your Laravel app uses relational databases, Eloquent or Spatie’s packages are better suited. You’d need to manually sync PHPCR data with Eloquent models.
- What Laravel versions does phpcr/phpcr-shell support?
- The shell itself has no direct Laravel version dependency—it’s a CLI tool for PHPCR. However, if you’re using Symfony 8 components (e.g., HTTP Client) in Laravel to interact with PHPCR APIs, ensure your Laravel app (v8+) aligns with Symfony 8’s requirements. The shell’s core functionality remains version-agnostic for Laravel.
- How can I debug PHPCR repositories in Laravel using this shell?
- Use the shell to connect to your PHPCR repository (e.g., `phpcrsh --host localhost --port 8080`) and browse nodes, execute queries, or inspect content directly. For Laravel integration, log shell commands in your application logs or pipe output to a file. If using Symfony’s HTTP Client, you can proxy PHPCR API calls and debug responses in Laravel’s logging system.
- Are there alternatives to phpcr/phpcr-shell for Laravel content management?
- For Laravel, consider Spatie’s packages (e.g., `spatie/laravel-medialibrary` for file storage) or Laravel Scout with Elasticsearch for search-heavy apps. If you’re tied to PHPCR, alternatives like PostgreSQL JSONB with Laravel Collections or Filament CMS might simplify content management. The shell is niche—only useful if PHPCR is a mandatory backend.
- Will phpcr/phpcr-shell work in production with Laravel?
- Yes, but it’s a CLI tool, not a web service. Use it for administrative tasks (e.g., content migration, debugging) via SSH or CI/CD pipelines. For production content operations, integrate PHPCR with Laravel using Symfony’s HTTP Client or a custom API layer. Ensure Java dependencies (e.g., Jackrabbit) are containerized (Docker) for stability.
- How do I authenticate with PHPCR from Laravel using this shell?
- Authentication depends on your PHPCR server (e.g., Jackrabbit’s credentials or repository-specific methods). The shell supports command-line flags like `--username` and `--password`. For Laravel, pass these credentials via environment variables or use Symfony’s HTTP Client to authenticate API calls. Avoid hardcoding credentials in the shell’s config.
- Can I use phpcr/phpcr-shell to sync PHPCR data with Laravel models?
- No, the shell doesn’t automate syncing. You’ll need to manually map PHPCR nodes to Laravel models or use event listeners to trigger updates. For complex syncs, consider Symfony’s Property Access Component (in Symfony 8) to simplify node-to-collection hydration, but this requires custom bridging logic.
- What are the performance implications of using PHPCR with Laravel?
- PHPCR’s hierarchical model can introduce latency compared to relational databases. Benchmark queries in the shell to identify bottlenecks. For Laravel, use caching (e.g., Redis) for frequent PHPCR reads or offload heavy operations to queue workers. Containerize PHPCR servers (Docker) to isolate performance impacts from Laravel’s PHP processes.
Weaver
How can I help you explore Laravel packages today?