meeting notes
1.0.0
使用 GPT-3.5 总结 Google Meet 通话。
该项目使用OpenAI的gpt-3.5-turbo-16k模型。
请参阅下面的演示以获取示例。
步骤：
在 Google Cloud 中创建服务帐号并下载 JSON 密钥文件。有关更多详细信息，请参阅此或此示例。
将 JSON 密钥保存到credentials.json文件中。
Docker 构建规范会将credentials.json文件复制到容器映像。
请记住为服务帐户启用域范围委派，以访问其他用户拥有的 Google 云端硬盘文件。
此构建示例使用 AWS ECR 来存储容器映像。但是，您可以使用任何容器注册表。
将
xxx.dkr.ecr.us-east-1.amazonaws.com替换为您的容器注册表。
登录 AWS ECR：
aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 261082948988.dkr.ecr.us-east-1.amazonaws.com构建 Docker 镜像：
docker build -t meeting-notes .标记图像：
docker tag meeting-notes:latest 261082948988.dkr.ecr.us-east-1.amazonaws.com/autohost-meeting-notes:latest将镜像推送到ECR：
docker push 261082948988.dkr.ecr.us-east-1.amazonaws.com/autohost-meeting-notes:latest创建 CloudFormation 参数文件：
cp stack-params.json stack-params-prod.json使用以下参数的值更新stack-params-prod.json文件：
使用aws-cli部署 CloudFormation 模板：
aws cloudformation create-stack
--stack-name meeting-notes-prod
--capabilities CAPABILITY_NAMED_IAM
--tags Key=service,Value=meeting-notes Key=Environment,Value=prod
--parameters file:// $( pwd ) /stack-params-prod.json
--template-body file:// $( pwd ) /cloudformation.yaml --profile default使用aws-cli更新 CloudFormation 模板：
aws cloudformation update-stack
--stack-name autohost-meeting-notes-prod
--capabilities CAPABILITY_NAMED_IAM
--tags Key=service,Value=meeting-notes Key=Environment,Value=prod
--parameters file:// $( pwd ) /stack-params-prod.json
--template-body file:// $( pwd ) /cloudformation.yaml --profile default首先构建容器镜像。
创建一个包含以下内容的.env文件：
AWS_DEFAULT_REGION=us-east-1
OPENAI_API_KEY=xxx
OPENAI_ORG_ID=org-xxx
AWS_ACCESS_KEY_ID=xxx
AWS_SECRET_ACCESS_KEY=xxx
MAILGUN_API_KEY=xxx
MAILGUN_DOMAIN=xxx.xyz
S3_BUCKET=xxx
PROMPT_HUB_API_KEY=xxx
LANGCHAIN_TRACING_V2=true
LANGCHAIN_PROJECT=meeting-notes
LANGCHAIN_API_KEY=xxx构建并运行图像：
docker build -t meeting-notes . && docker run -p 9000:8080 --env-file=.env --rm meeting-notes打开一个新的终端窗口，并使用curl测试以下端点。
将 Google Drive webhook 事件发送到 API：
curl -XPOST " http://localhost:9000/2015-03-31/functions/function/invocations "
-d ' {"headers":{"x-goog-resource-uri":"https://www.googleapis.com/drive/v3/changes?alt=json&pageToken=511460",
"x-goog-channel-token":"roy%40autohost.ai"}} '供工人总结会议记录的 SQS 活动：
curl -XPOST " http://localhost:9000/2015-03-31/functions/function/invocations "
-d ' {"Records":[{"messageId":"1JlgPkv5j_N9ul39dWRV-cVcVPIB-lfUK9OcKMALhxgg","body":"{"title":"Roy / Nam (2024-08-16 14:33 GMT-4) – Transcript","id":"1dyoTC5HG4Sfc75jSfeFUU-Rq52XuOnz5aief_mfzirQ","link":"https://docs.google.com/document/d/1dyoTC5HG4Sfc75jSfeFUU-Rq52XuOnz5aief_mfzirQ/edit?usp=drivesdk","owner_email":"[email protected]"}","attributes":{"ApproximateReceiveCount":"1","AWSTraceHeader":"Root=1-6470f9b0-xxxx;Parent=xxxx;Sampled=0;Lineage=85108a56:0","SentTimestamp":"1685125554295","SenderId":"change-me:meeting-notes-prod-api","ApproximateFirstReceiveTimestamp":"1685125554296"},"messageAttributes":{},"md5OfBody":"11268099d001110f04757778362ddb11","eventSource":"aws:sqs","eventSourceARN":"arn:aws:sqs:us-east-1:change-me:meeting-notes-prod-prod-queue","awsRegion":"us-east-1"}]} ' 发送给与会者的电子邮件示例：
Git Bootcamp (2023-05-29 14:03 GMT-4) - Transcript
Attendees:
Gilfoyle, Dinesh, Richard Hendricks, Jared Dunn, Monica Hall, Erlich Bachman
Summary:
In the workshop, Gilfoyle provided an in-depth explanation of Git, focusing on the differences
between merging and rebasing. He emphasized the safety of using git fetch for downloading updates
from the remote repository and used visual aids to illustrate the differences between merging and rebasing.
He advised against squashing commits from develop to master to avoid confusion and duplication.
He also stressed the importance of updating branches and creating feature branches off of develop,
recommending the rule of two for branching off feature branches and merging changes into develop in
small increments. He introduced the concept of WIP or draft PRs for ongoing work and the need for a clear
team workflow. He also touched on the interactive rebase command and its options, and concluded with a
brief discussion on git log and its search options.
Key Decisions:
- Git fetch should be used for safely downloading updates from the remote repository.
- Squashing commits from develop to master should be avoided to prevent confusion and duplication.
- The rule of two should be followed for branching off feature branches and changes should be merged into develop in small pieces.
- A clear workflow should be established for the team, including the use of WIP or draft PRs for ongoing work.
Next Steps:
- Team members should familiarize themselves with the differences between merging and rebasing.
- Team members should practice using git fetch for downloading updates.
- Team members should avoid squashing commits from develop to master.
- Team members should follow the rule of two for branching off feature branches and merge changes into develop in small increments.
- Team members should use WIP or draft PRs for ongoing work.
- Team members should establish a clear workflow.
- Team members should familiarize themselves with the interactive rebase command and its options.
- Team members should learn how to use git log and its search options.
Full transcript:
https://docs.google.com/document/d/xxxxxx/edit?usp=drivesdk
---
Sent by Meeting Notes AI ?
