- インフラ・ミドルウェア・アプリケーション構成の設定・管理フレームワーク
- CUIコマンドベースでなく、Rubyベースで記述する
- 一度書けば、誰でも実行できたり、再利用できるのが嬉しい
- 類似フレームワークとしては、Puppetが有名
Chefのメリット
<?php | |
namespace H57\Util; | |
class Serializor { | |
/** | |
* Converts the Doctrine Entity into a JSON Representation | |
* | |
* @param object $object The Object (Typically a Doctrine Entity) to convert to an array |
{% macro recursiveCategory(category) %} | |
<li> | |
<h4><a href="{{ path(category.route, category.routeParams) }}">{{ category }}</a></h4> | |
{% if category.children|length %} | |
<ul> | |
{% for child in category.children %} | |
{{ _self.recursiveCategory(child) }} | |
{% endfor %} | |
</ul> |
/* | |
Infinite List View | |
creates <ul> with triggers for infinite scrolling | |
@author Kevin Jantzer, Blacktone Audio Inc. | |
@since 2012-11-06 | |
USE - listen for: |
;SMBDIS.ASM - A COMPREHENSIVE SUPER MARIO BROS. DISASSEMBLY | |
;by doppelganger ([email protected]) | |
;This file is provided for your own use as-is. It will require the character rom data | |
;and an iNES file header to get it to work. | |
;There are so many people I have to thank for this, that taking all the credit for | |
;myself would be an unforgivable act of arrogance. Without their help this would | |
;probably not be possible. So I thank all the peeps in the nesdev scene whose insight into | |
;the 6502 and the NES helped me learn how it works (you guys know who you are, there's no |
imports: | |
# .... | |
- { resource: services/session.yml } | |
framework: | |
# .... | |
session: | |
handler_id: session.handler.memcached |
upstream servers-frontend { | |
ip_hash; | |
server 10.10.137.100:80; # server-1 | |
server 10.10.126.101:80; # server-2 | |
} | |
upstream server-2 { | |
server 10.10.137.101:80; | |
} |
Jenkins × PHP環境構築の巻 | |
■目的 | |
PHP環境に対応したJenkins設定を行い、 | |
コミットされる度にサーバ上でのPHPUnitの実行 及び | |
カバレッジレポート出力を"全自動"で行えるようにすること。 | |
1) PHP Pear系のインストール | |
sudo pear channel-discover pear.phing.info | |
sudo pear channel-discover pear.pdepend.org |
I have managed to install this… and make it work. I implemented it for Facebook and Google, but you can extend it. My solution it is mostly as described in #116, with a bit of more code presented. The key aspects that lack in the #116 presentation (IMO) are:
oauth_user_provider
in the security.yml
with your custom created serviceHere are the steps:
routing.yml
I have added all the routes for both bundles.config.yml
mostly as it is presented in the HWIOAuthBundle.security.yml
mostly as it is presented in the HWIOAuthBundle (though my routes are using /login
pattern, not /connect
). Also, the oauth_user_provider
is set for my custom service.var fs = require("fs"); | |
var path = require("path"); | |
var util = require("util"); | |
var styl = require("stylus"); | |
var wrench = require("wrench"); | |
function compileTSS(root, view) { | |
var data = fs.readFileSync(path.join(root, view), "utf8"), | |
tss; | |
styl.render(data, function (err, css) { |