-
Notifications
You must be signed in to change notification settings - Fork 4
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
Research on how to run conf.builderscon.io in GAE #37
Comments
これ、ちょっとキャッシュまわりの戦略のために考えたかったので今日見ちゃいました。 でも色々問題はあるので、とりあえず自分がやったところまであげておきます。 |
Notes: * Still unclear how we should handle secret information such as keys and tokens. * app.wsgi better be renamed to app.py * In GAE, we would have to use memcached, so Redis must be changed. * For https, certificates will have to be handled differently :/ So we still can't just migrate to GAE, but this is a start, so I will commit, and keep it. refs #37
忘れないうちに調査内容の書きとめ。 標準のAppEngine向けSSL証明書更新手順標準のやり方では、SSL証明書の更新はWeb上のAppEngineコンソールから手動でやらないといけないようです。(自分でこの辺をエミュレートするツールを書くなどしない限り)
gcloud APIの調査このコマンドは"gcloud compute"コマンドで、同レファレンスを見ても"gcloud app"で同様のコマンドはありません。 AppEngine Web Consoleがどう動いているか?さいごにWeb上のAppEngineコンソールもデバッグしてみましたが、以下のようなコンソール用のURLに対して https://console.cloud.google.com/m/sslCertificate?pid=conf-test-1470265052103 証明書と鍵とPOSTするリクエストを送っているので、ログインせずに証明書をアップロードできるAPIは存在しないようです、という結論。 |
ニュアンス違うw |
Notes: * Still unclear how we should handle secret information such as keys and tokens. * app.wsgi better be renamed to app.py * In GAE, we would have to use memcached, so Redis must be changed. * For https, certificates will have to be handled differently :/ So we still can't just migrate to GAE, but this is a start, so I will commit, and keep it. refs #37
(assigned to myselfのつもり)
conf.builderscon.ioはシンプルなのでGAEで走らせます。
八月に入ってから取り掛かる予定です。
The text was updated successfully, but these errors were encountered: