2016年7月 – ページ 3 – 端くれプログラマの備忘録

[Laravel] 複数のDBにアクセスする方法

2016年7月11日2017年3月18日 @84kure

config/database.phpにDB接続を複数定義
クエリービルダーではDB:connection(‘DB接続’)->select(…)
Eloquentではモデルクラスに$connection=’DB接続’

参考サイト

[Laravel]Laravelで別々のDB（MySQL）に接続させる方法 – Qiita
http://qiita.com/qiita-kurara/items/2e3efb4ccbb2489b05c3

Database: Getting Started – Laravel – The PHP Framework For Web Artisans
https://laravel.com/docs/5.4/database#using-multiple-database-connections

Eloquent: Getting Started – Laravel – The PHP Framework For Web Artisans
https://laravel.com/docs/5.4/eloquent#eloquent-model-conventions

[PHP] エラーをHTML出力の一部として画面に出力する

2016年7月10日2017年3月18日 @84kure

ローカルで開発していた案件を本番環境にディプロイしたら500エラー。エラーログへのアクセスも制限されていたりすると、原因究明に時間がかかることもある。

そんなときには、とりあえずエラーをHTML出力の一部として画面に出力するようにして、かつ、エラー出力レベルをE_ALLにしておけば、PHPが吐き出すエラーを全てブラウザ画面上に表示できる。不具合の原因究明の助けになる。

ini_set("display_errors", On);
error_reporting(E_ALL);

1 2	ini_set("display_errors", On); error_reporting(E_ALL);

参考サイト

PHP: 実行時設定 – Manual
http://php.net/manual/ja/errorfunc.configuration.php

PHP: error_reporting – Manual
http://php.net/manual/ja/function.error-reporting.php

PHP: ini_set – Manual
http://php.net/manual/ja/function.ini-set.php

[Laravel] 次に割り当てられるIDを知るには

2016年7月9日2017年3月18日 @84kure

AUTO_INCREMENTで割り当てられるIDの次の値を知る方法。

「なんだ、そんなことか」という感じだけど念のためメモ。

$nextId = DB::table('items')->max('id') + 1;

1	$nextId = DB::table('items')->max('id') + 1;

[Git] BitBucketにPushして自動でサーバーにデプロイする

2016年7月8日2017年3月18日 @84kure

以下のツールのお世話になる。

alixandru / bitbucket-sync — Bitbucket
https://bitbucket.org/alixandru/bitbucket-sync/overview

参考サイト

BitbucketにGit PUSHしてサーバーに自動でデプロイしちゃうよ！ | ザサイベース
http://thesaibase.com/server/bitbucket-git-push-deploy

レンタルサーバに自動デプロイ – Laravel学習帳
http://laraweb.net/environment/1080/

[PHP] PSR コーディング規約

2016年7月7日2017年2月16日 @84kure

参考サイト

PHP-FIG — PHP Framework Interop Group
http://www.php-fig.org/

PHP Standard Recommendation – Wikipedia
https://en.wikipedia.org/wiki/PHP_Standard_Recommendation

PHPコーディング規約まとめ – Qiita
http://qiita.com/hshimo/items/04be1f432240c58300f4

PHPのコーディング規約 PSR-0、PSR-1、PSR-2、PSR-3とは | 9ensanのLifeHack
http://9ensan.com/blog/programming/php/php-psr-coding-standards/

【PSR】PHPの標準コーディング規約 – Qiita
http://qiita.com/katsukii/items/e68183f14407722de9cc

[PHP] 名前空間とクラスのオートローディング

2016年7月6日2017年2月16日 @84kure

参考サイト

PHP: クラスのオートローディング – Manual
http://php.net/manual/ja/language.oop5.autoload.php

PHPのオートロード(autoload) – Qiita
http://qiita.com/atwata/items/5ba72d3d881a81227c2a

PHP: FAQ: 名前空間について知っておくべきこと – Manual
http://php.net/manual/ja/language.namespaces.faq.php

PHP V5.3 の名前空間を利用して、理解しやすく保守の容易なコードを作成する
https://www.ibm.com/developerworks/jp/opensource/library/os-php-5.3namespaces/

PHPのオブジェクト指向入門 | オブジェクト指向PHP.NET
http://www.objective-php.net/basic/namespace

[Nginx] 超簡単コマンドリファレンス

2016年7月5日2017年2月16日 @84kure

起動

# nginx

# nginx

停止

# nginx -s stop

1	# nginx -s stop

再起動

# nginx -s reload

1	# nginx -s reload

設定ファイルのチェック

# nginx -t

1	# nginx -t

参考サイト

nginx コマンド超シンプル早見表 – Qiita
http://qiita.com/katzueno/items/44e02db2f1bfa0de5860

[Vagrant] ダウンロードしたboxの展開に失敗する場合の対処法

2016年7月4日2017年2月16日 @84kure

Vagrantをインストールし直したら以下のエラーが出るようになった。複数のBoxを試したけど必ずエラー。どうやら自分の環境の問題っぽい。

$ vagrant box add hashicorp/precise32
==> box: Loading metadata for box 'hashicorp/precise32'
box: URL: https://atlas.hashicorp.com/hashicorp/precise32
==> box: Adding box 'hashicorp/precise32' (v1.0.0) for provider: virtualbox
box: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise32/versions/1.0.0/providers/virtualbox.box
box:
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and try again. The
output from attempting to unpackage (if any):

$ vagrant box add hashicorp/precise32

==> box: Loading metadata for box 'hashicorp/precise32'

box: URL: https://atlas.hashicorp.com/hashicorp/precise32

==> box: Adding box 'hashicorp/precise32' (v1.0.0) for provider: virtualbox

box: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise32/versions/1.0.0/providers/virtualbox.box

box:

The box failed to unpackage properly. Please verify that the box

file you're trying to add is not corrupted and try again. The

output from attempting to unpackage (if any):

ネットを検索したら、Vagrant同梱の解凍ソフトを入れ替えて解決した例が見つかった。なぞってやってみたら自分も解決した。

Error while adding Vagrant box in windows xp · Issue #3869 · mitchellh/vagrant · GitHub
https://github.com/mitchellh/vagrant/issues/3869#issuecomment-48058728

my solution was to download the basic_bsdtar.exe from here http://sourceforge.net/projects/mingw/files/MinGW/Extension/bsdtar/ and rename it to bsdtar.exe and place it in C:\HashiCorp\Vagrant\embedded\gnuwin32\bin\

結果オーライだけど原因はわからず。

[Vagrant] Warning: Authentication failure. Retrying… が繰り返し表示される場合の対処

2016年7月3日2017年2月15日 @84kure

vagrant upでWarning: Authentication failure. Retrying…が繰り返し表示される問題に直面。

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: centos7_default_1487179154735_44077
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
  default: Adapter 1: nat
==> default: Forwarding ports...
  default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
  default: SSH address: 127.0.0.1:2222
  default: SSH username: vagrant
  default: SSH auth method: private key
  default:
  default: Vagrant insecure key detected. Vagrant will automatically replace
  default: this with a newly generated keypair for better security.
  default:
  default: Inserting generated public key within guest...
  default: Removing insecure key from the guest if it's present...
  default: Key inserted! Disconnecting and reconnecting using new SSH key...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
  default: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

$ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Importing base box 'centos7'...

==> default: Matching MAC address for NAT networking...

==> default: Setting the name of the VM: centos7_default_1487179154735_44077

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

==> default: Forwarding ports...

default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

default: SSH address: 127.0.0.1:2222

default: SSH username: vagrant

default: SSH auth method: private key

default:

default: Vagrant insecure key detected. Vagrant will automatically replace

default: this with a newly generated keypair for better security.

default:

default: Inserting generated public key within guest...

default: Removing insecure key from the guest if it's present...

default: Key inserted! Disconnecting and reconnecting using new SSH key...

default: Warning: Authentication failure. Retrying...

Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly

working and you're able to connect to the machine. It is a common

problem that networking isn't setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.

If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.

対処法

最初は認証用の鍵ファイルに問題があると思って調べていたのだけど、以下のページによるとどうやらVagrantのバグっぽい。

Vagrant 1.8.5でLinux boxをvagrant upするとエラーが出る件について – 素敵なおひげですね
http://stknohg.hatenablog.jp/entry/2016/07/26/190330

[インストール先]\embedded\gems\gems\vagrant-1.8.5\plugins\guests\linux\cap\public_key.rbの56行目に
chmod 0600 ~/.ssh/authorized_keys
を追加してからVMを再作成してやれば直ります。

説明に従って修正したら問題解決。感謝。

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos7'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: centos7_default_1487180106705_92946
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
  default: Adapter 1: nat
==> default: Forwarding ports...
  default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
  default: SSH address: 127.0.0.1:2200
  default: SSH username: vagrant
  default: SSH auth method: private key
  default:
  default: Vagrant insecure key detected. Vagrant will automatically replace
  default: this with a newly generated keypair for better security.
  default:
  default: Inserting generated public key within guest...
  default: Removing insecure key from the guest if it's present...
  default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
  default: The guest additions on this VM do not match the installed version of
  default: VirtualBox! In most cases this is fine, but in rare cases it can
  default: prevent things such as shared folders from working properly. If you see
  default: shared folder errors, please make sure the guest additions within the
  default: virtual machine match the version of VirtualBox you have installed on
  default: your host and reload your VM.
  default:
  default: Guest Additions Version: 5.0.14
  default: VirtualBox Version: 5.1
==> default: Mounting shared folders...
  default: /vagrant => C:/Temp/centos7

$ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Importing base box 'centos7'...

==> default: Matching MAC address for NAT networking...

==> default: Setting the name of the VM: centos7_default_1487180106705_92946

==> default: Fixed port collision for 22 => 2222. Now on port 2200.

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

default: Adapter 1: nat

==> default: Forwarding ports...

default: 22 (guest) => 2200 (host) (adapter 1)

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

default: SSH address: 127.0.0.1:2200

default: SSH username: vagrant

default: SSH auth method: private key

default:

default: Vagrant insecure key detected. Vagrant will automatically replace

default: this with a newly generated keypair for better security.

default:

default: Inserting generated public key within guest...

default: Removing insecure key from the guest if it's present...

default: Key inserted! Disconnecting and reconnecting using new SSH key...

==> default: Machine booted and ready!

==> default: Checking for guest additions in VM...

default: The guest additions on this VM do not match the installed version of

default: VirtualBox! In most cases this is fine, but in rare cases it can

default: prevent things such as shared folders from working properly. If you see

default: shared folder errors, please make sure the guest additions within the

default: virtual machine match the version of VirtualBox you have installed on

default: your host and reload your VM.

default:

default: Guest Additions Version: 5.0.14

default: VirtualBox Version: 5.1

==> default: Mounting shared folders...

default: /vagrant => C:/Temp/centos7

[Vagrant] snapshotコマンドで仮想マシンの状態を保存する

2016年7月2日2017年2月15日 @84kure

スナップショットの保存

snapshotコマンドは仮想マシンが停止しているときに実行。

$ vagrant halt
$ vagrant snapshot save backup1
==> default: Snapshotting the machine as 'backup1'...
==> default: Snapshot saved! You can restore the snapshot at any time by
==> default: using `vagrant snapshot restore`. You can delete it using
==> default: `vagrant snapshot delete`.

$ vagrant halt

$ vagrant snapshot save backup1

==> default: Snapshotting the machine as 'backup1'...

==> default: Snapshot saved! You can restore the snapshot at any time by

==> default: using `vagrant snapshot restore`. You can delete it using

==> default: `vagrant snapshot delete`.

スナップショットの一覧

$ vagrant snapshot list
backup1

1 2	$ vagrant snapshot list backup1

スナップショットのリストア

$ vagrant snapshot restore backup1

1	$ vagrant snapshot restore backup1

スナップショットの削除

$ vagrant snapshot delete backup1

1	$ vagrant snapshot delete backup1

参考サイト

VagrantのSnapshot機能で仮想マシンの状態を保存/復元しよう | WEB ARCH LABO
http://weblabo.oscasierra.net/vagrant-snapshot/