Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
phpc.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A server for PHP programmers & friends. Join us for discussions on the PHP programming language, frameworks, packages, tools, open source, tech, life, and more.

Administered by:

Server stats:

837
active users

phpc.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

Alexander M. Turek

Did you attend my talk on Modernizing with Symfony at or ? I've uploaded my slides. slidr.io/derrabus/modernizing-

slidr.ioModernizing with Symfony (SymfonyCon 2022) by Alexander M. TurekA legacy application. It still earns the money, but maintaining the old code base is getting harder and harder. Feature development is too slow and the bug tracker is full of severe defect reports. Rewriting the whole application is something your developers would simply love to do. But the rewrite probably won't go live before it's running out of budget. Let's have a look at simple techniques that allow us to transform our legacy application step by step into a modern Symfony application.
Dec 09, 2022, 02:26 PM·Public
1boost·2favorites
Public
Emanuele Panz

@derrabus thanks for sharing them and for the talk at SFCon! Cool to see the same code I used to start modernising a SF 1.5 project few years ago :)
BTW:
1. Did you find a way to integrate the runtime component, you also had a question for Nikolas about that :)
2. The solution requires to define as "public" the services you'll need to load from the legacy code (with the 'global $kernel). This could get not so nice if such services are growing in numbers. WDYT?

Public
Alexander M. Turek

@thepanz 1. No and I'm not sure it's worth it tbh.

2. Yes, the services have to be public as long as you access them publicly. Given that this is a temporary state, I don't see an issue with that.

SearchLive feeds
About