-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: add Rack application skeleton for automatic deployment #45
release: add Rack application skeleton for automatic deployment #45
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
このファイルを追加してユーザーを追加したと言い張るのは強引かな。。。
Rackアプリケーションのスケルトンを追加、とかを最初のステップにした方がいいんじゃないかな。 |
次の項目の作業を並列して進めようと思っていたので、作業directoryを先に用意したかったんですが、
ref: #43 |
a5aa194
to
65c25d7
Compare
GitHub: groongaGH-43 In this PR, we set up a rack application skeleton of webhook auto signer. At the following PRs, we will implement the logic.
65c25d7
to
e8a3a3b
Compare
Rackアプリケーションのスケルトンを追加してみました。
$ tree .
.
├── config.ru
├── Gemfile
├── Gemfile.lock
└── lib
└── app.rb 直下に tree .
.
├── app.rb
├── config.ru
├── Gemfile
└── Gemfile.lock |
base_dir = Pathname(__FILE__).dirname | ||
lib_dir = base_dir + "lib" | ||
|
||
$LOAD_PATH.unshift(lib_dir.to_s) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
これなしで全部require_relative
でやってもいいかも。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: 48c0c04
@@ -0,0 +1,7 @@ | |||
module WebhookSigner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
webhook/
ディレクトリーの下だからWebhook
いらなくない?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: fe00849 deployer
に命名を変えたので、signer
だけでも違和感がなくなったので削除しました!
あぁ、やっぱり、 最終的に、サインだけじゃなくてパッケージ諸々を使えるようにするためのすべてをやるんだよ。 |
ありがとうございます! |
Because this user will handle everything about Groonga deployment.
ここまで頂いたレビューコメントの対応をしました。 |
@@ -0,0 +1,7 @@ | |||
module Signer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
こいつもDeployer
にしない?
デプロイの一貫でサインするみたいな位置づけにできないかな。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: 12e61a3 なるほどです!
Because Deployer will do sign not Signer.
ライセンスヘッダーと アプリケーションだからGPLv3 or laterかな。 |
ansible/files/home/deployer/COPYING
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: f4c7ccf にて、ライセンスヘッダーと |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
これにも入れておいて。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: a799593 了解です!
GitHub: GH-43
In this PR, we set up a Rack application skeleton for automatic deployment using webhook.
At the following PRs, we will implement the logic of automatic sign as first steps.
Call webhook