- Does sebtm/inwx-api-bundle work with Laravel?
- It is a Symfony bundle rather than a Laravel package, so it does not ship a native Laravel service provider or facade. The underlying INWX client code runs fine inside a Laravel app because Laravel already vendors many Symfony components, but you will usually instantiate and configure the client yourself or write a small wrapper provider. Treat the bundle's container wiring as Symfony-only and port the configuration values into your Laravel config files.
- How do I install sebtm/inwx-api-bundle with Composer?
- Install it with composer require sebtm/inwx-api-bundle and pin an explicit constraint such as ^1.0.1 instead of letting it float. In Symfony you then register the bundle in bundles.php or AppKernel, a step that has no direct Laravel equivalent. Commit your composer.lock so any change to the INWX integration arrives as a reviewed diff rather than transitive churn.
- How do I configure INWX API credentials for this bundle?
- The bundle provides a Symfony configuration tree for credentials and connection settings, which normally lives in a file under config/packages. In Laravel, mirror those keys into config/services.php or a dedicated config/inwx.php and read them from environment variables so nothing is hardcoded. Keep separate credential sets for the INWX production system and its test environment, and never reuse production credentials in local development.
- Which Laravel and Symfony versions does this bundle support?
- The v1.0.1 release fixes a Signature change introduced between Symfony 3.4 and 4.x, so the composer.json constraints are the only reliable answer for your stack. As a rough mapping, Symfony 3.4 corresponds to Laravel 5.7 and older, Symfony 4.x to Laravel 5.8 through 6, and Symfony 5.x to Laravel 7 and 8. Check whether the fix narrowed or dropped the Symfony 3.4 path before you commit to an upgrade plan.
- How do I manage DNS records through the INWX API in PHP?
- The bundle hands you a configured INWX client that exposes DNS record operations for the zones you manage, including creating, updating, and removing records. You call those methods from your own service or queued job instead of hand-building XML-RPC requests. Compute a diff and dry-run bulk record changes first, because a single bad update can take a live domain offline.
- Can I register and transfer domains programmatically with this package?
- Yes, the integrated client covers domain operations such as registration and transfers alongside nameserver and DNS management. Registrations cost real money and are difficult to reverse, so validate contact handles and test the full flow against the INWX test system first. Log every request and response so failed or partial operations can be audited and replayed.
- Is the v1.0.1 Signature change a breaking change for my application?
- It is labelled a patch, but the fix was written against a Signature change between Symfony 3.4 and 4.x, so it may have narrowed or removed the older code path. If Signature refers to request signing, a one-line change there can reject valid callers or accept invalid ones, which is a far larger blast radius than the version number suggests. Review the diff and its test coverage before deploying, and confirm Symfony 3.4 support still exists if you need it.
- How should I test an INWX integration in a Laravel application?
- Put the INWX client behind your own interface and mock it in your test suite so unit tests never hit the network. Add a focused round-trip test that asserts both accept-valid and reject-invalid cases for any signature or credential path, not merely that a request returns 200. Reserve real API calls for a staging environment pointed at the INWX test system.
- Is sebtm/inwx-api-bundle safe for production DNS management?
- It is a thin layer over the INWX XML-RPC API, so its stability tracks Symfony's internal contracts more than Laravel's public API, and Laravel upgrades that move the underlying Symfony major become its breaking surface. Before adopting it, check the repository activity, maintainer count and bus factor, license, and security disclosure policy, since a dormant single-maintainer repo is a real operational risk for anything touching DNS. Pin the version, review the signature-related diff, and deploy to one low-traffic service with failure metrics watched before expanding.
- What are the alternatives to this bundle for INWX in Laravel?
- You can call the INWX XML-RPC API directly, or use a generic XML-RPC client plus a small INWX-specific wrapper that you control. That is worth considering if the bundle turns out to be pinned to Symfony 3.4 or the repository looks unmaintained. Whichever route you take, hide the API behind your own interface so the implementation can be swapped without touching business logic.