2017-02-11 06:24:00 +01:00
|
|
|
# Using deploy api
|
|
|
|
|
2017-02-23 12:04:08 +01:00
|
|
|
Before you can deploy your cert, you must [issue the cert first](https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert).
|
|
|
|
|
2017-02-11 06:24:00 +01:00
|
|
|
Here are the scripts to deploy the certs/key to the server/services.
|
|
|
|
|
|
|
|
## 1. Deploy the certs to your cpanel host.
|
|
|
|
|
|
|
|
(cpanel deploy hook is not finished yet, this is just an example.)
|
|
|
|
|
2017-02-23 12:04:08 +01:00
|
|
|
|
2017-02-11 06:24:00 +01:00
|
|
|
|
|
|
|
Then you can deploy now:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export DEPLOY_CPANEL_USER=myusername
|
|
|
|
export DEPLOY_CPANEL_PASSWORD=PASSWORD
|
2017-02-23 12:01:48 +01:00
|
|
|
acme.sh --deploy -d example.com --deploy-hook cpanel
|
2017-02-11 06:24:00 +01:00
|
|
|
```
|
|
|
|
|
|
|
|
## 2. Deploy ssl cert on kong proxy engine based on api.
|
|
|
|
|
|
|
|
Before you can deploy your cert, you must [issue the cert first](https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert).
|
2017-04-27 14:06:47 +02:00
|
|
|
Currently supports Kong-v0.10.x.
|
2017-02-11 06:24:00 +01:00
|
|
|
|
2017-04-27 14:06:47 +02:00
|
|
|
```sh
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook kong
|
|
|
|
```
|
2017-02-11 06:24:00 +01:00
|
|
|
|
|
|
|
## 3. Deploy the cert to remote server through SSH access.
|
|
|
|
|
|
|
|
(TODO)
|
|
|
|
|
2017-02-21 16:18:11 +01:00
|
|
|
## 4. Deploy the cert to local vsftpd server.
|
2017-02-11 06:24:00 +01:00
|
|
|
|
2017-02-21 16:18:11 +01:00
|
|
|
```sh
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook vsftpd
|
|
|
|
```
|
|
|
|
|
|
|
|
The default vsftpd conf file is `/etc/vsftpd.conf`, if your vsftpd conf is not in the default location, you can specify one:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export DEPLOY_VSFTPD_CONF="/etc/vsftpd.conf"
|
|
|
|
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook vsftpd
|
|
|
|
```
|
|
|
|
|
|
|
|
The default command to restart vsftpd server is `service vsftpd restart`, if it doesn't work, you can specify one:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export DEPLOY_VSFTPD_RELOAD="/etc/init.d/vsftpd restart"
|
|
|
|
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook vsftpd
|
|
|
|
```
|
2017-02-11 06:24:00 +01:00
|
|
|
|
2017-02-23 13:03:03 +01:00
|
|
|
## 5. Deploy the cert to local exim4 server.
|
|
|
|
|
|
|
|
```sh
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook exim4
|
|
|
|
```
|
|
|
|
|
|
|
|
The default exim4 conf file is `/etc/exim/exim.conf`, if your exim4 conf is not in the default location, you can specify one:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export DEPLOY_EXIM4_CONF="/etc/exim4/exim4.conf.template"
|
|
|
|
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook exim4
|
|
|
|
```
|
|
|
|
|
|
|
|
The default command to restart exim4 server is `service exim4 restart`, if it doesn't work, you can specify one:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
export DEPLOY_EXIM4_RELOAD="/etc/init.d/exim4 restart"
|
|
|
|
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook exim4
|
|
|
|
```
|
|
|
|
|
2017-03-08 00:00:17 +01:00
|
|
|
## 6. Deploy the cert to OSX Keychain
|
|
|
|
|
|
|
|
```sh
|
|
|
|
acme.sh --deploy -d ftp.example.com --deploy-hook keychain
|
|
|
|
```
|