forked from wangziqi/gongxue-base
chore: add PNVS provider configuration script
This commit is contained in:
@@ -156,6 +156,28 @@ Taro H5 构建存在 webpack asset size warning,这是前端包体优化事项
|
||||
- 线上 H5 公开配置文件在 `/srv/tiku-saas/www/*/runtime-config.json`,密钥只允许放 `supabasePublishableKey` 这类公开 key。
|
||||
- 短信登录推荐生产使用 `AUTH_SMS_PROVIDER=aliyun-pnvs`。阿里云 AccessKey/Secret 只写入 `app_private.tenant_secrets(secret_scope='sms', secret_key='aliyun-pnvs')`,不要写进 `/etc/tiku-saas/api.env` 或 H5 `runtime-config.json`。
|
||||
|
||||
配置 PNVS provider 推荐用仓库脚本写入数据库,避免手写 SQL 时把密钥打进命令历史。生产环境建议临时关闭 shell history,再用 `read -s` 输入 AccessKeySecret:
|
||||
|
||||
```bash
|
||||
cd /opt/tiku-saas/repo
|
||||
set -a
|
||||
source /etc/tiku-saas/api.env
|
||||
set +a
|
||||
set +o history
|
||||
read -r -p 'Aliyun AccessKeyId: ' ALIYUN_ACCESS_KEY_ID
|
||||
read -r -s -p 'Aliyun AccessKeySecret: ' ALIYUN_ACCESS_KEY_SECRET; echo
|
||||
read -r -p 'PNVS SignName: ' ALIYUN_PNVS_SIGN_NAME
|
||||
read -r -p 'PNVS TemplateCode: ' ALIYUN_PNVS_TEMPLATE_CODE
|
||||
PNVS_TENANT_ID=00000000-0000-0000-0000-000000000001 \
|
||||
ALIYUN_ACCESS_KEY_ID="$ALIYUN_ACCESS_KEY_ID" \
|
||||
ALIYUN_ACCESS_KEY_SECRET="$ALIYUN_ACCESS_KEY_SECRET" \
|
||||
ALIYUN_PNVS_SIGN_NAME="$ALIYUN_PNVS_SIGN_NAME" \
|
||||
ALIYUN_PNVS_TEMPLATE_CODE="$ALIYUN_PNVS_TEMPLATE_CODE" \
|
||||
npm run configure:aliyun-pnvs
|
||||
unset ALIYUN_ACCESS_KEY_ID ALIYUN_ACCESS_KEY_SECRET ALIYUN_PNVS_SIGN_NAME ALIYUN_PNVS_TEMPLATE_CODE
|
||||
set -o history
|
||||
```
|
||||
|
||||
接管服务器时先做只读检查:
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user