/explore
|
You are here 
|
blog.syntaxseed.com | ||
| | | | |
brunty.me
Developer and problem solver |
|
| | | | | ||
| | | | |
fabien.potencier.org
The blog of Fabien Potencier about web technology and the symfony framework |
|
| | | | | ||
| | | | |
www.tobymackenzie.com
[AI summary] A developer shares a step-by-step guide on upgrading a Symfony 3 project to version 4 without using the Flex plugin, covering dependency management, configuration changes, and file cleanup. |
|
| | | | | ||
| | | | |
tomasvotruba.com
There are two types of upgrades. One follows only `UPGRADE.md` files on every release, replacing what has been removed with new alternatives. It works, and we could say that the codebase will be "up-to-date." The other upgrade doesn't stop at the required minimum but **makes use of all modern features the framework provides**. It will be faster, easier to understand, and easier to upgrade to the next version. I [wrote a post](/blog/two-kinds-of-legacy-code-upgrade) that explains why the latter is better. There are no sources about Symfony upgrades spanning multiple major versions-time to fix that. |
|
| | | |||
