acmesh-official / acmesh-official/acme.sh

Feature request: multideploy.yaml support customize path and domain config centrilized in one file

オープン
#7,173 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
Shell
スター
47.6k
フォーク
5.7k
平均マージ
6日 5時間
マージ済み PR(30日)
15

説明

currently the multideploy is not friendly for docker, the multideploy.yaml path hard code as like `$DOMAIN_PATH/$file`
https://github.com/acmesh-official/acme.sh/blob/2feb392bd0e3964d9bf68871ae804578d9d5ca80/deploy/multideploy.sh#L92
Is it possbile make the path be a setting, and the file content like:
```
# check your acme.sh version in wiki!
version: "1.0"

"*.example.com":
services:
- name: "traefik"
hook: "docker"
environment:
DEPLOY_DOCKER_CONTAINER_LABEL: "sh.acme.autoload.service=traefik"
DEPLOY_DOCKER_CONTAINER_KEY_FILE: "/certs/example.com/key.pem"
DEPLOY_DOCKER_CONTAINER_CERT_FILE: "/certs/example.com/cert.pem"
DEPLOY_DOCKER_CONTAINER_CA_FILE: "/certs/example.com/ca.pem"
DEPLOY_DOCKER_CONTAINER_FULLCHAIN_FILE: "/certs/example.com/fullchain.pem"
- name: "adguardhome"
hook: "docker"
environment:
DEPLOY_DOCKER_CONTAINER_LABEL: "sh.acme.autoload.service=dns01"
DEPLOY_DOCKER_CONTAINER_KEY_FILE: "/opt/adguardhome/work/data/encryption/example.com/key.pem"
DEPLOY_DOCKER_CONTAINER_FULLCHAIN_FILE: "/opt/adguardhome/work/data/encryption/example.com/fullchain.pem"
- name: "technitium-dns"
hook: "docker"
environment:
DEPLOY_DOCKER_CONTAINER_LABEL: "sh.acme.autoload.service=dns02"
DEPLOY_DOCKER_CONTAINER_PFX_FILE: "/etc/dns/certs/example.com.pfx"
- name: "router01"
hook: "routeros"
environment:
ROUTER_OS_USERNAME: "certuser"
ROUTER_OS_HOST: "router.example.com"
ROUTER_OS_PORT: "22"
- name: "nas01"
hook: "synology_dsm"
environment:
SYNO_SCHEME: "http"
SYNO_HOSTNAME: "localhost"
SYNO_PORT: "5000"
SYNO_CREATE: "1"
SYNO_CERTIFICATE: "PROD-$_cdomain"
"domain2.com":
......
"domain3.com":
......
"domain4.com":
......
```

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

The issue points to deploy/multideploy.sh line 92 where the path is hardcoded. Start by reading the multideploy.sh script to understand how it loads configuration. Then examine the proposed YAML structure and decide how to parse it. The change involves modifying the script to read a configurable path and support a centralized YAML file with domain-specific settings. Test by creating a sample multideploy.yaml and running the deploy script to see if it picks up the new settings.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
docker, shell
領域
cli, devops
issue の種類
機能追加
難易度
3/5
見積もり時間
1〜2日
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
55/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。