Frequently Asked Questions

Does Shift upgrade everything?

Not everything.

Shift attempts to upgrade your Laravel application so you just need to run composer update. However, given the dynamic nature of PHP and the infinite customization of a Laravel application, this is not always possible. When Shift can not reliably perform a change, a detailed comment will be added to the Pull Request for you to review.

Does Shift upgrade more than the Laravel Upgrade Guide?

Yes.

The Upgrade Guide focuses on new features and breaking changes, treating the rest as optional. Over time, if you only follow the Laravel Upgrade Guide you will accumulate technical debt.

Shift attempts to upgrade all changes. This ensures your project is fully up-to-date with your version of Laravel and there are no future surprises.

Can I run several Shift's at once?

Yes, but it's not recommended.

You should complete the upgrade for each Shift before moving on to the next. Doing so incrementally allows you to verify each upgrade to ensure you don't miss anything. If there is a problem, you'll also have more context about which version broke the build.

What if my project is not on Bitbucket/GitHub/GitLab?

Currently Shift supports Bitbucket, GitHub, and GitLab. Using these services allows Shift to easily access your Laravel applications and perform the upgrade on a separate branch for your review.

These services offer free public repositories. If privacy is a concern, Bitbucket and GitLab offer free private repositories. So there's nothing stopping you using Shift.

What if my boss/client/legal/paranoia won't let me share my project?

No worries. That's why I built Shift for Docker - so you can run any Shift locally.

Why does Shift need write access to my repositories?

Having write access to your repositories allows Shift to create a new branch and open a Pull Request. This way the process can be seamlessly automated from start to finish.

Once you merge the Pull Request, you are welcome to deauthorize the Laravel Shift application.

Does Shift keep a copy of my code?

No.

Your Laravel application only lives on the Shift server when the upgrade process is running - which on average is less than a minute. Afterward your upgraded Laravel application is pushed to your repository and forcefully removed from the Shift server.

Can I pay with PayPal?

Yes.

Simply start your order process. Once you reach checkout, email your Shift number to shift@laravelshift.com to pay with PayPal.

What happens if things go wrong?

During checkout, Shift will verify access to your repository and charge your credit card. If anything goes wrong you will receive an error message so you may resolve the issue.

Once checkout is complete, your Shift is added to the job queue. If a Shift fails, you will receive an email notification with some things to check on your side before trying to run your Shift again.

Does Shift offer additional support?

Yes.

For quick support feel free to message @laravelshift on Twitter or email shift@laravelshift.com. If you need help upgrading your application, Shift offers human services.