Migrating away from symfony1: strategies, tricks, ideas #324
Replies: 2 comments
-
I am working on two legacy codes at the moment, neither of them symfony1, but both will be symfony7. The first one is a 20 year old code, organized in files but with a shared scope. Smarty, Adodb and some service classes (Class named constructors!!! hoooly moly). In both cases I define services and push the application logic towards ServiceSubscriber, with Request input and Response output. Once that's done, symfony will eat it without any problem whatever the layout. |
Beta Was this translation helpful? Give feedback.
-
Well this is certainly timely. The application I work on is on 1.4 and we've talked for years about eventually upgrading, but there wasn't a good path for it. We decided to carve some time out in March/April to really devote to figuring out what our path forward is, and this is a great set of resources. I'm excited to see some existing Bundles to try and mess with! |
Beta Was this translation helpful? Give feedback.
-
I think at least a fair share of those still using symfony1 would like to replace it with something more modern but, despite it's name, Symfony2+ is a very different framework, so migration away from symfony1 is quite a big task that is often hard to justify for large projects.
Nonetheless, I think this is a topic that interests some, so I'm starting a discussion on it so that there's a place to share experiences and ideas on that.
Over the years I collected a few links related to this, mostly in the form of symfony2+ wrappers around a symfony1 project:
and some to wrap any generic legacy project:
Now most links all quite outdated, but perhaps they can still be useful for ideas and strategies on how go about it.
With this, have you tried (successfully or not) to migrate a project built with symfony1? What were the main hurdles you found? How long did it take?
Beta Was this translation helpful? Give feedback.
All reactions