- What is Laravel Slipway and what problem does it solve?
- Laravel Slipway is a lightweight Laravel package that lets you define your CI/CD pipeline once in config/slipway.php and compile it into provider-specific configuration for GitHub Actions, Bitbucket Pipelines, and GitLab CI. It reduces duplication when you support multiple CI platforms or maintain several Laravel repositories. It is intended as a simple launchpad-style tool rather than a full CI abstraction layer.
- How do I install Laravel Slipway in a Laravel app?
- Install it with Composer using composer require usamamuneerchaudhary/laravel-slipway. Then create or publish config/slipway.php as described in the repository README. Check the README for the exact publish and compile commands for your Laravel version.
- Which CI/CD providers does Laravel Slipway support?
- It compiles your single pipeline definition to GitHub Actions, Bitbucket Pipelines, and GitLab CI. The generated files target each provider's native configuration format. If you use another CI system, you would need to maintain that configuration separately.
- How does config/slipway.php work?
- You define your pipeline once in config/slipway.php, then use the package's Artisan commands to compile that definition into provider-specific CI files. The config file acts as the source of truth so you can keep GitHub, Bitbucket, and GitLab workflows in sync. Keep provider-specific overrides minimal to get the most benefit.
- Do I need to learn a new CI/CD syntax to use Laravel Slipway?
- You work with a Laravel config array rather than writing three separate YAML files by hand. The package translates that config into each provider's YAML format. You should still understand the target provider's CI concepts so you can review and extend generated files.
- Does Laravel Slipway work with GitHub Actions, Bitbucket Pipelines, and GitLab CI at the same time?
- Yes, the core value is compiling one pipeline definition to all three supported providers. You can generate only the files you need for your repositories. This is useful if different projects or clients use different CI platforms.
- What Laravel and PHP versions are supported by Laravel Slipway?
- Laravel Slipway is a Laravel package, so support depends on the version constraints declared in its composer.json. Check the repository's composer.json and README for the exact Laravel and PHP versions before adding it to an existing app. For older Laravel versions, verify compatibility or pin a package release that matches.
- Can I customize the generated GitHub Actions, Bitbucket, or GitLab CI files?
- The package generates provider-native CI files from config/slipway.php, so you can review and customize the output for provider-specific needs. For repeatable changes, prefer updating the shared config and recompiling. Avoid manual edits that will be overwritten the next time you compile.
- How should I test Laravel Slipway in a project before using it in production?
- Install it in a branch, define a small pipeline in config/slipway.php, and compile the output for one provider first. Review the generated YAML against your provider's documentation and run it on a test repository. Expand to additional providers once the first pipeline behaves as expected.
- Is Laravel Slipway a replacement for GitHub Actions, Bitbucket Pipelines, or GitLab CI?
- No. Laravel Slipway is a configuration compiler for CI/CD pipelines; it does not replace the CI platform that runs your jobs. You still need a GitHub, Bitbucket, or GitLab repository with the respective CI service enabled. The package helps you maintain one pipeline definition across those services.