letsencrypt-rails-heroku 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 05ee4912e0826370d5e74c310b425ba6e4143921
-  data.tar.gz: 889c2a4c16e672481c1db9d42a5dfe2a45f8424e
+  metadata.gz: e656c9229f6a8721d684ec0909a229d9fd80ea23
+  data.tar.gz: 3627d2cf277d9bc3c3310d43d646cfbe5f16c426
 SHA512:
-  metadata.gz: f0cf0b6f588d1a91fbe590d55d44cc211c51865241392379d8fe8b4ea90f4a4033ba1eff5dbf79ed1c4aa2819fec77b6bf49934a0d61defe9ac5f69a29b876ff
-  data.tar.gz: 82269e1b169a4ddc091882d42b970a82cfe880cd37c183248e3c733129b6bf63a8f740fbc93d3cb266468a8a0443e3a871b8f3ae1a5be0622c166caac755989e
+  metadata.gz: f2e12aa812981cd9fceb7b38830df18448e774524e3e8a8dd43f862875fac250a650084ce29cf1b01be2427a8ba5b22a0beaf8b14e95d0833886b700e6faf3d8
+  data.tar.gz: 51ad28ed49e4fd61647014a35d34d249f6ea4caee0678ac91cc91a1e8e612bf74cfc949a3b68ccec7232a44533dc8de5864ad63e1f34c9fcf9336fcda510ad42

data/CHANGELOG.md

@@ -1,3 +1,9 @@
+# 1.1.0
+
+ - Make `ACME_DOMAIN` optional by using the Heroku API to get a full list of
+   configured domains for the app. Useful for apps with lots of domains.
+   Configuring `ACME_DOMAIN` is still supported.
+
 # 1.0.0
 
 The major version bump reflects the backwards-incompatible change around how

data/README.md

@@ -67,6 +67,9 @@ which you should set.
    certificates, e.g. `example.com,www.example.com`. Your Heroku app should be
    configured to answer to all these domains, because LetsEncrypt will make a
    request to verify ownership.
+
+   If you leave this blank, the gem will try and use the Heroku API to get a 
+   list of configured domains for your app, and verify all of them.
  * `ACME_EMAIL`: Your email address, should be valid.
  * `HEROKU_TOKEN`: An API token for this app. See below
  * `HEROKU_APP`: Name of Heroku app e.g. bottomless-cavern-7173
@@ -159,6 +162,12 @@ following security considerations:
 
    The gem performs some cursory checks to make sure the filename is roughly
    what is expected to try and mitigate this.
+   
+## Troubleshooting
+
+### Common name invalid errors (security certificate is from *.herokuapp.com)
+
+Your domain is still configured as a CNAME or ALIAS to `your-app.herokuapp.com`. Check the output of `heroku domains` matches your DNS configuration. When you add an SNI cert to an app for the first time [the DNS target changes](https://devcenter.heroku.com/articles/custom-domains#view-existing-domains).
 
 ## To-do list
 

data/VERSION

@@ -1 +1 @@
-1.0.0
+1.1.0

data/letsencrypt-rails-heroku.gemspec

@@ -2,16 +2,16 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Juwelier::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: letsencrypt-rails-heroku 1.0.0 ruby lib
+# stub: letsencrypt-rails-heroku 1.1.0 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "letsencrypt-rails-heroku"
-  s.version = "1.0.0"
+  s.version = "1.1.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib"]
   s.authors = ["Pixie Labs", "David Somers", "Abigail McPhillips"]
-  s.date = "2017-02-17"
+  s.date = "2017-02-22"
   s.description = "This gem automatically handles creation, renewal, and applying SSL certificates from LetsEncrypt to your Heroku account."
   s.email = "team@pixielabs.io"
   s.extra_rdoc_files = [

data/lib/letsencrypt-rails-heroku/letsencrypt.rb

@@ -31,7 +31,7 @@ module Letsencrypt
     end
 
     def valid?
-      heroku_token && heroku_app && acme_email && acme_domain
+      heroku_token && heroku_app && acme_email
     end
   end
 end

data/lib/tasks/letsencrypt.rake

@@ -8,7 +8,7 @@ namespace :letsencrypt do
   desc 'Renew your LetsEncrypt certificate'
   task :renew do
     # Check configuration looks OK
-    abort "letsencrypt-rails-heroku is configured incorrectly. Are you missing an environment variable or other configuration? You should have a heroku_token, heroku_app, acme_email and acme_domain configured either via a `Letsencrypt.configure` block in an initializer or as environment variables." unless Letsencrypt.configuration.valid?
+    abort "letsencrypt-rails-heroku is configured incorrectly. Are you missing an environment variable or other configuration? You should have a heroku_token, heroku_app and acme_email configured either via a `Letsencrypt.configure` block in an initializer or as environment variables." unless Letsencrypt.configuration.valid?
 
     # Set up Heroku client
     heroku = PlatformAPI.connect_oauth Letsencrypt.configuration.heroku_token
@@ -27,7 +27,14 @@ namespace :letsencrypt do
     registration.agree_terms
     puts "Done!"
 
-    domains = Letsencrypt.configuration.acme_domain.split(',').map(&:strip)
+    domains = []
+    if Letsencrypt.configuration.acme_domain
+      puts "Using ACME_DOMAIN configuration variable..."
+      domains = Letsencrypt.configuration.acme_domain.split(',').map(&:strip)
+    else
+      domains = heroku.domain.list(heroku_app).map{|domain| domain['hostname']}
+      puts "Using #{domains.length} configured Heroku domain(s) for this app..."
+    end
 
     domains.each do |domain|
       puts "Performing verification for #{domain}:"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: letsencrypt-rails-heroku
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Pixie Labs
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-02-17 00:00:00.000000000 Z
+date: 2017-02-22 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: acme-client