On Taming Repository Classes in Doctrine
Over at the easybib/dev Blog Anne posted an entry about their usage of Doctrine Repositories with a growing amount of query responsibilities. I want to respond to this blog post with two alternative approaches, because I have seen the easybib approach multiple times in different projects by different teams and think it can be approved upon a lot. The problems with the approach outlined are: The Re
Domain-Driven Design in PHP
In 2014, after two years of reading about and working with Domain-Driven Design, Carlos and Christian, friends and workmates, traveled to Berlin to participate in Vaughn Vernon's Implementing Domain-Driven Design Workshop. The training was fantastic, and all the concepts that were swirling around in their minds prior to the trip suddenly became very real. However, they were almost no PHP developer
Symfony2ã®ç¾å®Ÿçš„ãªé«˜é€ŸåŒ–テクニック | ホームページ作æˆã€ã‚·ã‚¹ãƒ†ãƒ è¨è¨ˆ glicæ ªå¼ä¼šç¤¾
Symfony2ã¯é…ã„フレームワークã¨è¨€ã‚れるã“ã¨ãŒã‚ˆãã‚ã‚Šã¾ã™ã€‚ 確ã‹ã«è‰²ã€…ãªã‚µã‚¤ãƒˆã§PHPフレームワークã®ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ãŒæ¯”較ã•ã‚Œã¦ã„ã¦ã€Symfonyã¯é…ã„æ–¹ã¨ã•ã‚Œã¦ã„ã‚‹ã“ã¨ãŒå¤šã„ã§ã™ã€‚ ãŸã æ°—ã«ãªã‚‹ã®ãŒã€ã“れらã®ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ãŒã©ã‚Œã ã‘ç¾å®Ÿã®ã‚¢ãƒ—リケーションã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’åæ˜ ã—ã¦ã„ã‚‹ã‹ã§ã™ã€‚テンプレートエンジンを使ã†ã¨(ã¾ãŸã¯å¤‰æ›´ã™ã‚‹ã¨)ã©ã†ãªã‚‹ã‹ã€ORMã§å¤§é‡ã®DBアクセスを行ã†ã¨ã©ã†ãªã‚‹ã‹ã€ã‚ャッシュメカニズムを有効ã«ã—ãŸå ´åˆã«ã©ã†ãªã‚‹ã‹â€¦ ã“れらをè¸ã¾ãˆã¦ã‚‚ã‚ãˆã¦ãŠã™ã™ã‚ã—ãŸã„ã®ãŒSymfony2ã§ã™ã€‚ ç†ç”±ã¨ã—ã¦ã¯é«˜é€ŸåŒ–ã™ã‚‹ä½™åœ°ãŒå分ã«ã‚る点ã§ã™ (ã¨ã¦ã‚‚ç°¡å˜ã«ã§ãã‚‹ã‚‚ã®ã‚‚ã‚ã‚Šã¾ã™!) 特ã«ä»¥ä¸‹ã®ç‚¹ã«æ³¨ç›®ã—ã¦ã„ãŸã ããŸã„ã§ã™ã€‚ 実ã¯å†…部ã«ãƒªãƒãƒ¼ã‚¹ãƒ—ãƒã‚ã‚·ã®å®Ÿè£…ã‚’æŒã£ã¦ã„ã¾ã™ ESI (Edge Side Includes) ãŒä½¿ãˆã‚‹ ãªã‚“ã§ã‚‚ã‚ャッシュã§ãã‚‹! ã“ã“ã§ã¯Sym
Doctrine2 四方山話 ( Fetch mode, Index by, Criteria ã«ã¤ã„ã¦) - OTOBANK Engineering Blog
ã¯ã˜ã‚ã¾ã—ã¦ã€‚4月ã‹ã‚‰ã‚ªãƒˆãƒãƒ³ã‚¯ã§åƒã始ã‚ã¾ã—㟠@kalibora ã¨ç”³ã—ã¾ã™ã€‚よã‚ã—ããŠé¡˜ã„ã—ã¾ã™ã€‚ ã•ã¦ã€ã‚ªãƒˆãƒãƒ³ã‚¯ã§ã¯ Symfony2 を使ã£ã¦ãŠã‚Šã€ORマッパーã«ã¯ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã® Doctrine2 を使用ã—ã¦ã„ã‚‹ã®ã§ã™ãŒã€ ãã‚“ãªä¸ã§ç§ãŒå¾—ãŸçŸ¥è¦‹ã‚’ã„ãã¤ã‹ç´¹ä»‹ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ Fetch mode ã®è©± Doctrine2 ã«ã¯ fetch mode ã¨ã„ã†æ¦‚念ãŒã‚ã‚Šã¾ã™ã€‚ Annotations Reference - Doctrine Object Relational Mapper (ORM) を見ã¾ã™ã¨ Doctrine2ã«ã¯ä¸‹è¨˜ã® fetch mode ãŒã‚るよã†ã§ã™ã€‚ fetch mode 定義ã§ãã‚‹å ´æ‰€ EAGER @ManyToOne @ManyToMany @OneToOne @OneToMany LAZY @ManyToOne @ManyToMany @O
自作クラスをDoctrine ORM@Columnã«ãƒžãƒƒãƒ”ングã™ã‚‹ | QUARTETCOM TECH BLOG
Doctrine Custom Mapping Typeを定義ã—ã¦è‡ªä½œã‚¯ãƒ©ã‚¹ã‚’ORM@Columnã«ãƒžãƒƒãƒ”ングã™ã‚‹æ–¹æ³•ã‚’紹介ã—ã¾ã™ã€‚ Doctrine DBAL 2 documentation http://docs.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/types.html#custom-mapping-types ã“ã®è¨˜äº‹ã‚’書ã„ãŸç’°å¢ƒ Symfony 2.6 Doctrine/ORM 2.5 Doctrine/dbal 2.5 サンプルケース 月次レãƒãƒ¼ãƒˆã‚’示ã™Reportエンティティ Reportエンティティã¯æœˆæ¬¡ãƒ¬ãƒãƒ¼ãƒˆã‚’管ç†ã™ã‚‹ã‚¯ãƒ©ã‚¹ã§ã™ã€‚年月をyyyymmå½¢å¼ã®æ•´æ•°ã§æŒã£ã¦ã„ã¾ã™ã€‚ <?php namespace MyProject\Bundle\AcmeDemoBundle\Entity
Google ã® Feed API ãŒäº¡ããªã£ãŸãã†ãªã®ã§ã€Symfony 3.0 ã®ãƒ†ã‚¹ãƒˆã‚‚å…¼ãã¦ã€ä¼¼ãŸã‚ˆã†ãªã‚‚ã®ã‚’作ã£ã¦ã¿ã¾ã—㟠- OTOBANK Engineering Blog
ã—ã‚ã£ã™ï¼@riaf ã§ã™ï¼ タイトルã©ãŠã‚Šãªã‚“ã§ã™ãŒã€æœ€è¿‘ã©ã†ã‚„ら Google Feed API ㌠Deprecated ã«ãªã‚Šã€ã¡ã‚‡ã£ã¨ã—ãŸã¨ã“ã‚ã«æ´»ç”¨ã—ã¦ãŸäººãŸã¡ãŒæ‚²é³´ã‚’ã‚ã’ã¦ã‚‹ã®ã‚’ç›®ã«ã—ãŸã®ã§ã€ãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã°ã‹ã‚Šã® Symfony 3.0 ã®ãƒ†ã‚¹ãƒˆã‚‚å…¼ãã¦ã€ä¼¼ãŸã‚ˆã†ãªã‚µãƒ¼ãƒ“スを作ã£ã¦ã¿ã‚ˆã†ã¨æ€ã„ã¾ã—ãŸã€‚ ã¤ã„ã§ã«ã€é–‹ç™ºä¸ã ã£ãŸ otobank/facebook-bundle も一緒ã«ä½¿ã£ã¦ã—ã¾ãŠã†ã€‚ã¨ã€ç„¡æ„味㫠Facebook ãƒã‚°ã‚¤ãƒ³ãŒå¿…é ˆã«ãªã£ã¨ã‚Šã¾ã™ãŒã€ãƒ¦ãƒ¼ã‚¶ãƒ¼æƒ…å ±ã®ä¿å˜ã¨ã‹ã€é¢å€’ã§å®Ÿè£…ã—ã¦ãªã„ã®ã§ã€ã‚³ãƒã‚¯ãƒˆã—ãŸã¨è¨€ã£ã¦ã‚‚特ã«æ‚ªã•ã—ãŸã‚Šã—ã¾ã›ã‚“ã®ã§ã€å®‰å¿ƒã—ã¦ãã ã•ã„(ãã‚Œã§ã„ã„ã®ã‹) 作ã£ãŸã®ã¯ã“ã¡ã‚‰ã§ã™ã€‚ https://feedjson.otolabo.jp サービスã®ä½¿ã„æ–¹ã¨ã‹ã«é–¢ã—ã¦ã¯ã‚‚ã†ã¡ã‚‡ã£ã¨ã¡ã‚ƒã‚“ã¨ä½œã£ãŸå¾Œã«ã§ã‚‚紹介ã—ã¾ã™ã。 Symfony 3.0 ã‚’
Symfony 2.8ã¨PHP-DIã®Auto Wiring - プãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ãƒ¡ãƒ¢
ã“ã®è¨˜äº‹ã¯Â Symfony Advent Calendar 2015 ã®16日目ã§ã™ã€‚昨日ã¯@Issei_Mã•ã‚“ã®ã€Œæœ€è¿‘ã®Symfony Standard Editionã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªæ§‹æˆã€ã§ã—ãŸã€‚ 内製フレームワークã‹ã‚‰ã®ç§»è¡Œå…ˆã‚’探ã—ã¦Symfonyを調査ä¸ã§ã™ã€‚ãã®éŽç¨‹ã§DIã®Auto Wiringã®ä½¿ã„方を確èªã—ãŸã®ã§ã€ã“ã“ã«ã¾ã¨ã‚ã¾ã™ã€‚ æ¦‚è¦ Symfony 2.8ã§ã¯ã‚µãƒ¼ãƒ“スã®Auto WiringãŒå¯èƒ½ã«ãªã‚Šã¾ã—㟠(New in Symfony 2.8: Service Auto Wiring (Symfony Blog))。ã“ã‚Œã¾ã§ã¯ã€services.ymlã«ã‚µãƒ¼ãƒ“スã®åå‰ã¨ã‚¯ãƒ©ã‚¹åã®å®šç¾©ã€ä¾å˜å…ˆã®ã‚µãƒ¼ãƒ“スも(ãŸã¨ãˆã°ã‚³ãƒ³ã‚¹ãƒˆãƒ©ã‚¯ã‚¿ã®å¼•æ•°ã¨ã—ã¦)指定ãŒå¿…è¦ã§ã—ãŸã€‚Auto Wiring有効時ã¯ã€ã‚³ãƒ³ã‚¹ãƒˆãƒ©ã‚¯ã‚¿ã®ã‚¿ã‚¤ãƒ—ヒンティングを利用ã—ã¦ã€ã“れらã®å®šç¾©ãŒç°¡ç•¥åŒ–ã§ãるよã†ã«
Configuration Organization Tips
Configuration organization tips How to organize the app/config directory What's the best piece of code for a developer? What if we must manage it? Lets start feeling comfortable... feeling comfortable is better than best practices (so next tips are suggestions, not rules) Is it so important? Keep control while the application grows Prevent big configuration files Be ready for changes Default value
Symfony 2.7入門 ãã®1 インストールã¨Hello World · DQNEO日記
Symfony 2.7入門ã§ã™ã€‚ Symfonyã¯ã€ç¾åœ¨ã®PHPフレームワークã®ä¸ã§æœ€ã‚‚使ã‚ã‚Œã¦ã„ã‚‹ã‚‚ã®ã®ï¼‘ã¤ã§ã™ã€‚ 特徴ã¨ã—ã¦ã¯ã€ 徹底ã—ãŸç–Žçµåˆã®è¨è¨ˆæ€æƒ³ 部å“ã®å†åˆ©ç”¨æ€§ãŒé«˜ã„ ソースコードãŒèªã¿ã‚„ã™ã„ 世界的ã«ãƒ¦ãƒ¼ã‚¶ãŒå¤šã„ 柔軟性ãŒé«˜ã„ ãªã©ãŒã‚ã‚‹ã‹ã¨æ€ã„ã¾ã™ã€‚ 個人的ãªæ„Ÿæƒ³ã¨ã—ã¦ã¯ä¸Šè¨˜ã«åŠ ãˆã¦ 「クセãŒå°‘ãªã„ã€ã¨ã„ã†ã®ãŒã‚ã‚‹ã¨æ€ã„ã¾ã™ã€‚ã¤ã¾ã‚Šæ±Žç”¨çš„ã§ã‚ã‚‹ã¨ã„ã†ã“ã¨ã§ã™ã€‚ Symfonyã§å¦ã‚“ã 知è˜ã‚„哲å¦ã¯ã€ä»–ã®ãƒ•ãƒ¬ãƒ¼ãƒ ワークや他ã®è¨€èªžã§é–‹ç™ºã™ã‚‹ã¨ãã«ã‚‚ãã£ã¨å½¹ã«ãŸã¤ã“ã¨ã§ã—ょã†ã€‚ 想定èªè€…ã¨æŽ¨å¥¨ç’°å¢ƒ PHPã¯å°‘ã—使ãˆã‚‹ã‘ã©Symfonyã¯åˆã‚ã¦ã¨ã„ã†æ–¹ã‚’対象ã«ã—ã¦ã„ã¾ã™ã€‚ Linux/Unixã®åŸºæœ¬çš„ãªã‚³ãƒžãƒ³ãƒ‰ã¯ä½¿ãˆã‚‹ã“ã¨ã‚’想定ã—ã¦ã„ã¾ã™ã€‚ 動作環境ã¯LinuxåŠã³Macã§ã™ã€‚(Windowsã®æ–¹ã¯Vagrantç‰ã®ä»®æƒ³ç’°å¢ƒã‚’使ã£ã¦ãã ã•ã„） PHP5.4以上ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’推奨ã—ã¾
2.7ã‹ã‚‰å§‹ã‚ã‚‹Symfony2[PHP][Symfony] - ã‚ã–らã—備忘録。
Symfony2ã®LTSã§ã‚ã‚‹ã€Symfony2.7ãŒã¡ã‚‡ã£ã¨å‰ã«ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã—ãŸã€‚ LTSã¨ã„ã†ã“ã¨ã§ã€Symfony2.7ã¯3å¹´é–“ã¯ã‚µãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆï¼ã£ã¦ã„ã†ãªã‹ãªã‹å®‰å®šæ„Ÿã®ã‚ã‚‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã«ãªã£ã¦ã„ã¾ã™ã€‚ The Release Process (Contributing to Symfony) サãƒãƒ¼ãƒˆæœŸé–“ãŒé•·ã„ã®ã§ã‚®ãƒ§ãƒ¼ãƒŸãƒ¼ãªéƒ¨åˆ†ã«ã‚‚Symfony2ã‚’å°Žå…¥ã™ã‚‹ãƒãƒ¼ãƒ‰ãƒ«ã‚‚下ãŒã‚‹ã—Symfony2ã‚’æ–°è¦ã§å°Žå…¥ã™ã‚‹ã“ã¨ã‚‚増ãˆã‚‹ã‚“ã˜ã‚ƒãªã„ã‹ãªãã¨æ€ã„ã¾ã™ã€‚ ã¨ã„ã†ã“ã¨ã§ä»Šå›žã¯ã€Œã“ã‚Œã‹ã‚‰Symfony2を始ã‚ã‚‹ã«ã¯ã€ã¨ã„ã£ãŸã¨ã“ã‚ã®è¨˜äº‹ã‚’書ã“ã†ã‹ãªã¨æ€ã„ã¾ã™ï¼ 「今ã¾ã§ä½¿ã£ãŸã“ã¨ãªã„ã‘ã©ã€è©¦ã—ã¦ã¿ã‚ˆã†ã‹ãªï¼Ÿã€çš„ãªã¨ã“ã‚ã®åŠ©ã‘ã«ãªã‚Œã°å¹¸ã„ã§ã™ã€‚ 今回ã¯Symfony2ã®å°Žå…¥ã‹ã‚‰ç°¡å˜ãªæ§‹é€ ã®èª¬æ˜Žã¾ã§ã‚’ã§ããŸã‚‰ã¨æ€ã„ã¾ã™ã€‚ インストーラーã®å°Žå…¥ Symfony2ã¯ã€2015/03/26ã‹ã‚‰ã€æ–°ã—ã„
![2.7ã‹ã‚‰å§‹ã‚ã‚‹Symfony2[PHP][Symfony] - ã‚ã–らã—備忘録。](https://cdn-ak-scissors.b.st-hatena.com/image/square/3c6791785dff94d5c64b0be7feebcfdd60245f9e/height=288;version=1;width=512/https%3A%2F%2Fogimage.blog.st-hatena.com%2F12704830469095606045%2F8454420450098300051%2F1434819500)
How we Upgraded to Symfony 2.7 (+ deprecation notices)
Symfony 2.7 - the next LTS release - came out on Saturday, with bells and whistles like 100+ new features/enhancements and a surprise new bridge component to PSR-7. So, we decided to upgrade immediately and report back. Let's go! Upgrading composer.json Since Symfony protects backwards-compatibility, upgrading is mostly easy, but we did hit a few minor things. Btw, there's a new upgrade section on
Using PSR-7 in Symfony - Kévin Dunglas
Kévin Dunglas Founder of Les-Tilleuls.coop (worker-owned cooperative). Creator of API Platform, FrankenPHP, Mercure.rocks, Vulcain.rocks and of some Symfony components. PSR-7, the last PHP Standard Recommendation, was adopted by the PHP Framework Interoperability Group on May 19. That PSR defines PHP interfaces representing HTTP messages: request and response (client and server side), uploaded fil
Symfonyã‚‚ãã‚‚ã会 #4 を開催ã—ã¾ã—㟠- kseta's blog
Symfonyã‚‚ãã‚‚ã会も今回ã§ï¼”回目を迎ãˆã‚‹ã“ã¨ãŒã§ãã¾ã—ãŸã€‚ Symfonyã‚‚ãã‚‚ã会 #4 - 日本Symfonyユーザー会 | Doorkeeper 今回ã¯æ ªå¼ä¼šç¤¾ãƒ’トメディアã•ã‚“ã® the p@rk ã‚’ä¼šå ´ã§ã®é–‹å‚¬ã§ã—ãŸã€‚今ã¾ã§ç•°å¸¸ã« Symfony ã«ãƒ•ã‚©ãƒ¼ã‚«ã‚¹ã—ãŸä¼šã¨ãªã‚Šã¨ã¦ã‚‚内容ã®æ¿ƒã„会ã¨ãªã£ãŸã¨æ„Ÿã˜ã¾ã™ã€‚å‚åŠ è€…ã®æ–¹ã‹ã‚‰ã‚‚「楽ã—ã‹ã£ãŸã€ã€Œå‹‰å¼·ã«ãªã£ãŸã€ã¨å¥½è©•ã®å£°ã‚’ã¡ã‚‰ã»ã‚‰èžãã“ã¨ãŒã§ãã¦å¬‰ã—ãæ„Ÿã˜ã¾ã—ãŸã€‚ ã¨ã„ã†ã“ã¨ã§ç¬¬å››å›žç›®ã®è¨˜éŒ²ã§ã™ã€‚ ã©ã‚“ãªå ´æ‰€ã ã£ãŸï¼Ÿ æ ªå¼ä¼šç¤¾ãƒ’トメディアã•ã‚“ã® the p@rk ã‚’ä¼šå ´ã§ã®é–‹å‚¬ã§ã—ãŸã€‚ã¨ã¦ã‚‚広々ã¨ã—ãŸç©ºé–“ã§éŸ³éŸ¿è¨å‚™ã‚‚ã°ã£ã¡ã‚Šã€‚Wi-Fiã€é›»æºã€ãƒ—ãƒã‚¸ã‚§ã‚¯ã‚¿ãƒ¼ã‚‚ã‚‚ã¡ã‚ん完備。åã©ã‚‚ã‚’éŠã°ã›ã‚‹ã‚¹ãƒšãƒ¼ã‚¹ã¾ã§ã‚ã‚Šã¾ã—ãŸã€‚仕事ã§ã¯ã„ã¤ã‚‚音楽をèžã„ã¦ã„ã‚‹ã®ã§ã€Œã“ã‚“ãªç´ 敵ãªéŸ³éŸ¿ã§æ¯Žæ—¥ä»•äº‹ã§ããŸã‚‰ãªã〜ã€ã¨æ„Ÿã˜ã¾ãã‚Šã¾ã—ãŸã£ï¼å¤šãã®å‚åŠ è€…ã®æ–¹ãŒå¿ƒåœ°
Scaling Silex applications
In my humble opinion Silex is great. It’s perfect to create prototypes, but when our application grows up it turns into a mess. That was what I thought until the last month, when I attended to a great talk about Silex with Javier Eguiluz. OK. Scaling Silex it’s not the same than with a Symfony application, but it’s possible. It’s pretty straightforward to create a Silex application with composer:
ランã‚ング
メンテナンス
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Guzzle 6 Logging with Symfony: what's the right way to create a callback service? — !&# — bangpound
Symfony2: How to mock services during functional tests
Define Symfony access control rules in a database
Symfony3
after upgrade to 2.7.0 , kpnpaginator complains service "templating.helper.router" is non-existent · Issue #14790 · symfony/symfony
Bringing Symfony Components into Your Legacy Code
{{#tags}}- {{label}}
{{/tags}}