History

DrDrrae e887871bf1 Update README to remove automatically updating the config file and to specify that it doesn't update. Also, specify how the certificate is saved and where to point the config file to.		2017-08-12 09:54:19 -04:00
..
apache.sh	deploy apache script: fix comment (dovecot/apache)	2017-03-02 08:39:31 +01:00
cpanel.sh	add doc	2017-02-11 13:24:00 +08:00
dovecot.sh	fix format	2017-02-19 20:40:53 +08:00
exim4.sh	spelling: oops	2017-03-26 05:29:11 +00:00
haproxy.sh	fix format	2017-02-19 20:40:53 +08:00
keychain.sh	deploy for OSX Keychain	2017-03-06 11:09:12 +09:00
kong.sh	Update the notes	2017-04-28 00:25:30 +08:00
lighttpd.sh	Fix indenting	2017-08-10 22:25:14 -04:00
myapi.sh	exe	2017-02-05 23:14:25 +08:00
mysqld.sh	fix format	2017-02-19 20:40:53 +08:00
nginx.sh	fix format	2017-02-19 20:40:53 +08:00
opensshd.sh	fix format	2017-02-19 20:40:53 +08:00
pureftpd.sh	fix format	2017-02-19 20:40:53 +08:00
README.md	Update README	2017-08-12 09:54:19 -04:00
unifi.sh	Add deployment script for unifi controller	2017-07-30 12:21:20 +01:00
vsftpd.sh	spelling: oops	2017-03-26 05:29:11 +00:00

README.md

Using deploy api

Before you can deploy your cert, you must issue the cert first.

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.)

Then you can deploy now:

export DEPLOY_CPANEL_USER=myusername
export DEPLOY_CPANEL_PASSWORD=PASSWORD
acme.sh --deploy -d example.com --deploy-hook cpanel

2. Deploy ssl cert on kong proxy engine based on api.

Before you can deploy your cert, you must issue the cert first. Currently supports Kong-v0.10.x.

acme.sh --deploy -d ftp.example.com --deploy-hook kong

3. Deploy the cert to remote server through SSH access.

(TODO)

4. Deploy the cert to local vsftpd server.

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:

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:

export DEPLOY_VSFTPD_RELOAD="/etc/init.d/vsftpd restart"

acme.sh --deploy -d ftp.example.com --deploy-hook vsftpd

5. Deploy the cert to local exim4 server.

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:

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:

export DEPLOY_EXIM4_RELOAD="/etc/init.d/exim4 restart"

acme.sh --deploy -d ftp.example.com --deploy-hook exim4

6. Deploy the cert to OSX Keychain

acme.sh --deploy -d ftp.example.com --deploy-hook keychain

7. Deploy the cert to Lighttpd

The config file does not get updated automatically. Configure Lighttpd config file SSL settings to point to /etc/acme.sh/lighttpd/primarydomain.pem. For example, /etc/acme.sh/lighttpd/ftp.example.com.pem.


acme.sh --deploy -d ftp.example.com --deploy-hook lighttpd

The default command to restart Lighttpd server is service lighttpd restart, if it doesn't work, you can specify one:

export DEPLOY_LIGHTTTPD_RELOAD="/etc/init.d/lighttpd restart"

acme.sh --deploy -d ftp.example.com --deploy-hook lighttpd