どうやったら使える？

インストールと使い方もすごく簡単です。まずインストールは git clone するだけです。.vim の下に clone してあげてください。

 

1	git clone http://github.com/gmarik/vundle.git ~/.vim/vundle.git

ただ dotfiles をすでに git で管理しているような環境だと vundle は外部リポジトリとして追加してあげた方が良さそうです。こんな感じですかね。

 

1 2 3 4

cd dotfiles # リポジトリに移動する git submodule add http://github.com/gmarik/vundle.git .vim/vundle.git git add . git commit -m "add vundle submodule"

あとは使いたいプラグインを .vimrc にちょろっと書いてあげるだけで使えるようになります。プラグインは .vimrc にこのように Bundle "plugin_name" と記述するだけ。.vimrc で使っているプラグインが一元管理できるのはすごく楽ですね～。

あ、4, 5行目はおまじないです。詳しくは こちら を参照ください。

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

set nocompatible filetype off   set rtp+=~/.vim/vundle.git/ call vundle#rc()   " vim-scripts リポジトリ (1) Bundle "rails.vim"   " github の任意のリポジトリ (2) Bundle "tpope/vim-fugitive"   " github 以外のリポジトリ (3) Bundle "git://git.wincent.com/command-t.git"   filetype plugin indent on

使いたいプラグインを指定するわけですが、プラグインの置かれている場所によって3つの方法があります。vim-scripts リポジトリ (http://vim-scripts.org/vim/scripts.html) に置かれていれば (1) のようにプラグイン名を、github の任意のリポジトリであれば (2) のようにリポジトリ名とプラグイン名を、github のリポジトリでは無い場合には (3) のようにフルパスで指定します。

で、最後に vim 上で :BundleInstall することで、プラグインが .vim/bundle 以下にさくっとインストールされます。あっという間です。もう使えます！！

 

 

 

 

If either of these conditions is true, follow these steps to configure the listener:

1. From a command prompt, type the appropriate command to stop the following services:
   • Windows Media Services: net stop wmserver
   • Internet Information Services: net stop iisadmin
   • Http.sys Listener: net stop http
2. Run the WMSHttpSysCfg utility (located at %systemroot%\system32\windows media\server\admin\mmc\WMSHttpSysCfg.exe).
3. Add the IP addresses that you want Http.sys to listen to. The addresses that Http.sys does not listen to are available for WMS to use. (If this list is blank, Http.sys listens to all non-loopback IP addresses).
4. Click OK to close the dialog box.
5. Restart the services that you stopped in step 1 (including, but not limited to):
   • Http.sys Listener: net start http
   • World Wide Web Publishing Service or IIS Admin: net start w3svc
   • Windows Media Services: net start wmserver
6. Configure WMS HTTP Server Control Protocol:
   1. Start WMS Admin MMC.
   2. Select the server name.
   3. Click the Properties tab, and then click Control Protocols.
   4. If it is not already disabled (or if it is In Error), right-click WMS HTTP Server Control Protocol, and then click Disable.
   5. Right-click WMS HTTP Server Control Protocol, and then click Properties.
   6. Click Allow selected IP addresses to use this protocol.
   7. Select the IP addresses that you want to deliver content over port 80.

      Note Do not select the same IP addresses as the ones that you added to the Http.sys listener in step 3, otherwise the plug-in might go into an error state when it is enabled.

   8. Set the plug-in to Use default port (80).
   9. Click Apply, and then click OK to close the dialog box.
   10. Right-click WMS HTTP Server Control Protocol, and then click Enable.

At this point, you can expect that WMS is streaming media content over port 80 for the IPs selected in the control plug-in, and that Http.sys is handling all other port 80 requests.

Important Other applications might make a configuration utility that can change the Http.sys IP listen list. When you restart the Http.sys service the next time, it can bind to port 80 on an address selected by WMS and might cause the control plug-in to go into an error state.

If you are using Microsoft Windows Server 2003 with Service Pack 1 installed, you can also prevent the Http.sys service from capturing all available IP addresses for port 80 by applying the hotfix that is mentioned in the following Microsoft Knowledge Base article:

892847  (http://support.microsoft.com/kb/892847/ ) FIX: IIS 6.0 incorrectly binds to ports when IP addresses are added to the IP inclusion list

This hotfix lets you set a registry value that makes the Http.sys service listen only to the specific IP addresses that IIS Web sites are configured to use.

For more information about running Windows Media Services v4.1 with IIS 5.0, click the following article number to view the article in the Microsoft Knowledge Base:

268585  (http://support.microsoft.com/kb/268585/ ) Running IIS 5.0 and Windows Media Services with HTTP streaming

As with aggregate(), the name for the annotation is automatically derived from the name of the aggregate function and the name of the field being aggregated. You can override this default name by providing an alias when you specify the annotation:

>>> q = Book.objects.annotate(num_authors=Count('authors'))
>>> q[0].num_authors
2
>>> q[1].num_authors
1

ここは、 aggregate()ではなくて　annotate() のような気がします。。。

対応法：

ココに記載があった。

ようはudevの設定を変更しろっ、との事

# vi /etc/udev/rules.d/70-persistent-net.rules
※こいつは複製前の情報なので削除
# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:fb:41:ae", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

※こっちが複製後のMACアドレスがセットされている(違ったら修正）。ただし、"NAME="eth1"を"NAME=eth0"に変更する必要
# PCI device 0x8086:0x100e (e1000)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:9f:cc:8d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


# reboot   ※再起動してネットワークの稼働状況を確認

django-tastypie

Using django-tastypie is like playing with pure Python while using the Django ORM. I find it very comfortable. Seems really fast too. The documentation is incredible, and I rarely have any problems figuring anything out. It also supports OAuth 1.0a out of the box, which is mighty awesome these days.

In fact, I wrote a custom OAuth2 handler for django-tastypie I wrote for consumer.io that I'm working to extract out for publication.

django-rest-framework

As it's based off Django 1.3 style Class Based Views (CBVs), it has a very familiar pattern. Actually, because of the quality of the documentation, I really prefer using django-rest-framework CBVs more than using Django's actual CBVs.

Maybe I should make an HTML renderer for django-rest-framework? :-)

But what about django-piston?

Don't use django-piston.

sign(self, digest, algo='sha1')

Signs a digest with the private key

Parameters:

• digest (str) - A digest created by using the digest method
• algo (str) - The method that created the digest. Legal values are 'sha1','sha224', 'sha256', 'ripemd160', and 'md5'.

Returns:

a string which is the signature

% git branch -a
* master
  hoge
  origin/hoge
% git branch -d hoge
% git push origin :hoge

:hoge でリモートブランチの削除になるの。

わかりづらい気がするよ！

共有スナップショットの使い方

スナップショットは、AWS Management Console またはAPI 呼び出しを使って共有できます。ユーザーは、AWS コミュニティ全体で共有するオプションを含めて、共有スナップショット別に設定することができます。

AWS Management Console:

1. 新しい Amazon EBS ボリュームを作成してそのボリュームで共有するファイルのみをコピーします。
2. AWS Management Console にログインし、[Amazon EC2] タブをクリックしてから、左側のナビゲーションペインにある [ボリューム] をクリックします。
3. [ボリューム] を右クリックしてスナップショットをとります。
4. 左側のナビゲーションペインで [スナップショット] をクリックします。
5. 共有する [スナップショット] を右クリックして、[スナップショットアクセス許可] を選択します。
6. アクセスを許可する開発者の AWS アカウント番号を追加する、または公開して共有します。
7. [保存] をクリックしてアクセス許可を適用します。

Error Messages Explained

Since PHP 4.2.0, PHP returns an appropriate error code along with the file array. The error code can be found in the error segment of the file array that is created during the file upload by PHP. In other words, the error might be found in $_FILES['userfile']['error'].

UPLOAD_ERR_OK

Value: 0; There is no error, the file uploaded with success.

UPLOAD_ERR_INI_SIZE

Value: 1; The uploaded file exceeds the upload_max_filesize directive in php.ini.

UPLOAD_ERR_FORM_SIZE

Value: 2; The uploaded file exceeds the MAX_FILE_SIZE directive that was specified in the HTML form.

UPLOAD_ERR_PARTIAL

Value: 3; The uploaded file was only partially uploaded.

UPLOAD_ERR_NO_FILE

Value: 4; No file was uploaded.

UPLOAD_ERR_NO_TMP_DIR

Value: 6; Missing a temporary folder. Introduced in PHP 4.3.10 and PHP 5.0.3.

UPLOAD_ERR_CANT_WRITE

Value: 7; Failed to write file to disk. Introduced in PHP 5.1.0.

UPLOAD_ERR_EXTENSION

Value: 8; A PHP extension stopped the file upload. PHP does not provide a way to ascertain which extension caused the file upload to stop; examining the list of loaded extensions with phpinfo() may help. Introduced in PHP 5.2.0.

Note:

These became PHP constants in PHP 4.3.0.

ini_set('error_reporting', E_ALL);
ini_set('display_errors', 'On');  //On or Off

Their are two ways to get out of this situation,

1. Changes in php.ini file

If you can have access to php.ini file then change the display error property to On.

display_errors = On

Also make sure that error reporting property is at least set to

error_reporting  =  E_ALL & ~E_NOTICE & ~E_STRICT

1. Changes in the file

In case where you don’t have access to php.ini file, you can set these property in PHP script itself. Simply add following at the very start of your PHP script

error_reporting(E_ALL);
ini_set('display_errors',TRUE);

If you are using some, open source package like Drupal, Joomla or WordPress then put these codes in the index.php file in the root directory, right at top.