Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

AtlasApollo's avatar

Porting Laravel 4.2 application to Spark?

Hi,

I have a live membership site running on Laravel 4.2, with Cashier and paying customers.

I would like to rebuild the site and base it on Spark as the platform.

Does anyone know what I should be concerned about in doing this?

I am thinking of approaching it like this:

  • Create fresh spark install
  • Migrate the tables (except for user) to the new system
  • Turn off auto increment in the users table
  • Port each user from the old users table into the new users table, keeping the user ID from the old table
  • With each user that's ported, get all of their data from all of the other tables and import the data.
  • Turn on auto increment and continue new user registrations on the new database.

Would this break anything with Stripe? Or anything else? Is there a better way to do this?

Many thanks, Mike

0 likes
4 replies
jekinney's avatar

First, why? Adding some amazing feature only available in spark?

Maybe lazy, maybe smart, it's all argumentative. :).

Unless I need to, I personally tend to not upgrade. Seen it's not a security issue and it works why bother. I have clients still running l3 with out an issue.

FYI, you don't need to remove auto increment, you can explicitly set it. Obviously it need to be unique, but you can set it like any column. Also you can export from sql in a variety of formats and reseed a new db with a few clicks or commands.

1 like
AtlasApollo's avatar

Thanks :)

Why? The framework has gone through many changes since 4.2, and I've also become a bit better with the tools. I think I'd like to recreate what I have, make it better...

ejdelmonico's avatar

I can tell you that you will have tremendous difficulty porting a 4.2 app to Spark. If even thinking about it, forget it. If necessary, plan on rebuilding the app based on Laravel 5.3. The problem is that Spark is heavily opinionated and really difficult to attempt to modify. Add on sure, modifying opens up a vicious cycle of technical debt. It would take far less time to rebuild it using Spark. The main purpose for Spark is subscription management with only free, monthly and yearly provisions. Everything else must be done through Cashier...which Spark is built on. Other than that, you build any laravel 5.3 site around it.

2 likes
AtlasApollo's avatar

Thank you everybody, I will rebuild the app in Spark.

All the best, Mike

Please or to participate in this conversation.