Google Cloud DNS for Let's Encrypt / ACME dns-01 challenges with ACME.js and Greenlock.js
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
 
 
AJ ONeal e612d57912 update docs and examples for auth il y a 5 ans
lib update docs and examples for auth il y a 5 ans
.gitignore add template, implement auth and zones il y a 5 ans
AUTHORS add template, implement auth and zones il y a 5 ans
LICENSE Initial commit il y a 5 ans
README.md update docs and examples for auth il y a 5 ans
example.env update docs and examples for auth il y a 5 ans
index.js add template, implement auth and zones il y a 5 ans
oauth2l-test-token.sh update docs and examples for auth il y a 5 ans
package-lock.json update docs and examples for auth il y a 5 ans
package.json add package.json il y a 5 ans
test.js update docs and examples for auth il y a 5 ans

README.md

acme-dns-01-googlecloud.js

Google Domains + Let's Encrypt for Node.js - ACME dns-01 challenges w/ ACME.js and Greenlock.js

In Progress. Would love help. Please contact @coolaj86 on Keybase.

  • zones
  • set
  • get
  • remove

Implementation Details

Authenticating

Google has made things way too complicated.

Test This First!

Edit the file oauth2l-test-token.sh

Change the location of service_account.json to whatever it needs to be.

Change the PROJECT to the name of your project.

If that doesn't work, something is wrong with your credentials, nothing else will work.

Usage

First you create an instance with your credentials:

var dns01 = require('acme-dns-01-googlecloud').create({
	baseUrl: 'https://www.googleapis.com/dns/v1/', // default

	// contains private_key, private_key_id, project_id, and client_email
	serviceAccountPath: __dirname + '/service_account.json'
});