Couple weeks ago speaking with @ocramius about Annotated Container. He brought up something about Attributes I had heard a few times before. Something along the lines of:
"I don't want container wiring code littered throughout my codebase."
So, I wrote a blog article that talks about how Attributes aren't really the point of Annotated Container and how you can use the library with no Attributes or highly limit their spread through your code.
@cspray@edorian one stronger feeling I have at the moment is that I don't want my domain (or "good") code to be have symbols that couple it to a framework or DI container. So prefer orchestrating "externally" to the class. I.e. aiming for "closed for modification" even if it's modifying an attribute...
@dantleech@edorian From my conversations, this appears to be a popular line of thinking. One I understand the reasoning for and I hope my article shows AC can support!
I'm planning on continuing to eat my own dogfood with AC and create an app using the per-module DefinitionProvider design. Hopefully I might discover ways that the library can be improved when using this style of DI config.
I have a FREE book on object-oriented programming available for you to download and enjoy. It's my way of giving back to the #php community. Check it out: https://masteringobjectorientedphp.com
Have you ever stood up, from scratch, a completely new version of your application in a production-ready state?
If you haven't, you should.
You may never need to fully stand up a complete production instance, but what happens if a part goes down like your database, your webservers, or your jobs? Are you prepared for emergencies?
@sarah I had to do this some time last year. Proud to say: it only took us a few hours, in part because we had copious backups and had trained for this. 👍
@sarah We do that, several times a year, one where we restore crashed servers, one where we restore single installations, one where we restore multiple, one for hot backup, one for cold backups.
Everytime we review the procedures, and fix any changes we encounter.
I am seeking speakers for my @phpugffm & @phpugmrn meetups. We prefer in-person presentations in Frankfurt or the Mannheim area, but remote talks are also an option. If you have anything interesting to share with us, let us know. We'd be more than happy to have you! Thx! #php#phpc#phpugffm#phpugmrn
@vanamerongen There might be... Options ... as @shochdoerfer already mentioned. But in general we (as in The Usergroups) are (sadly) also missing the budged. 😉
After asking the community, I have decided to release a v12 version of the #TYPO3#Crawler which is compatible with TYPO3 12 LTS. There are some smaller know issues, but I hope the community will engage and help improve the code base.