Skip to content

Docker container to automate letsencrypt certificate serve for namecheap domains

Notifications You must be signed in to change notification settings

abulava/lexicon-dehydrated-namecheap

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 

Repository files navigation

lexicon-dehydrated-namecheap

Based on:

Why

Some providers (like Route53 and TransIP) require additional dependencies. You can install provider specific dependencies separately

Also a small tuning inside and "sugar" outside

What

Container to run certificate obtaining preconfigured to v2 endpoints and namecheap. But technically you can use any provider. Just set env variables PROVIDER and auth related.

Requirements

  • docker
  • namecheap API token & username

Usage

Create 2 files, 1 of them bash for easy use run.sh:

#!/usr/bin/env bash
set -e

docker run --rm -it \
    -v ${PWD}:/data \
	-e [email protected] \
	-e LEXICON_NAMECHEAP_USERNAME=example \
    -e LEXICON_NAMECHEAP_TOKEN=201927quien5Afei2vaem8choh0ooFah \
	tomfun/lexicon-dehydrated-namecheap:latest \
	$@

And domains.txt with domains:

*.example.com
www.tomfun.co demo.tomfun.co

First time

Create account and accept terms

./run.sh /srv/dehydrated/dehydrated --register --accept-terms
# Or
# ./test-run.sh /srv/dehydrated/dehydrated --register --accept-terms

See configs

Create account and accept terms

./run.sh /srv/dehydrated/dehydrated -e
# Or
# ./test-run.sh /srv/dehydrated/dehydrated -e

Staging mode

STAGING=true means enable staging endpoint for CERTIFICATES, but not for namecheap Create bash file for easy use like run.sh but with -e STAGING=true \ in test-run.sh and use it

About

Docker container to automate letsencrypt certificate serve for namecheap domains

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 61.8%
  • Dockerfile 38.2%