conf: document gpg_keys, and the three keys the man page lacks

gpg_keys was missing from debian/aptly.conf, and the man page had no
entry for ppaBaseURL, enablePprofEndpoint or gpgKeys. The wording
follows the existing template comments where there is one.

debian/aptly.conf

@@ -157,6 +157,10 @@ gpg_disable_sign: false
 # Disable signature verification of remote repositories
 gpg_disable_verify: false
 
+# GPG key IDs to sign with when a publish does not name one itself
+# (the -gpg-key flag, or GpgKey in the API's signing options)
+gpg_keys: []
+
 
 # Publishing
 #############

man/aptly.1

@@ -100,6 +100,9 @@ The legacy json configuration is still supported (and also supports comments):
   // Codename for short PPA url expansion
   "ppaCodename": "",
 
+  // PPA Base URL
+  "ppaBaseURL": "http://ppa.launchpad.net",
+
   // OBSOLETE
   // in aptly up to version 1\.0\.0, package files were stored in internal package pool
   // with MD5\-dervied path, since 1\.1\.0 package pool layout was changed;
@@ -121,6 +124,9 @@ The legacy json configuration is still supported (and also supports comments):
   // Enable API documentation on /docs
   "enableSwaggerEndpoint": false,
 
+  // Enable pprof profiling endpoints on /api/debug/pprof/*
+  "enablePprofEndpoint": false,
+
   // OBSOLETE: use via url param ?_async=true
   "AsyncAPI": false,
 
@@ -181,6 +187,10 @@ The legacy json configuration is still supported (and also supports comments):
   // Disable signature verification of remote repositories
   "gpgDisableVerify": false,
 
+  // GPG key IDs to sign with when a publish does not name one itself
+  // (the \-gpg\-key flag, or GpgKey in the API's signing options)
+  "gpgKeys": [],
+
 
 // Publishing
 //////////////

man/aptly.1.ronn.tmpl

@@ -89,6 +89,9 @@ The legacy json configuration is still supported (and also supports comments):
       // Codename for short PPA url expansion
       "ppaCodename": "",
 
+      // PPA Base URL
+      "ppaBaseURL": "http://ppa.launchpad.net",
+
       // OBSOLETE
       // in aptly up to version 1.0.0, package files were stored in internal package pool
       // with MD5-dervied path, since 1.1.0 package pool layout was changed;
@@ -110,6 +113,9 @@ The legacy json configuration is still supported (and also supports comments):
       // Enable API documentation on /docs
       "enableSwaggerEndpoint": false,
 
+      // Enable pprof profiling endpoints on /api/debug/pprof/*
+      "enablePprofEndpoint": false,
+
       // OBSOLETE: use via url param ?_async=true
       "AsyncAPI": false,
 
@@ -170,6 +176,10 @@ The legacy json configuration is still supported (and also supports comments):
       // Disable signature verification of remote repositories
       "gpgDisableVerify": false,
 
+      // GPG key IDs to sign with when a publish does not name one itself
+      // (the -gpg-key flag, or GpgKey in the API's signing options)
+      "gpgKeys": [],
+
 
     // Publishing
     //////////////

system/t02_config/CreateConfigTest_gold

@@ -157,6 +157,10 @@ gpg_disable_sign: false
 # Disable signature verification of remote repositories
 gpg_disable_verify: false
 
+# GPG key IDs to sign with when a publish does not name one itself
+# (the -gpg-key flag, or GpgKey in the API's signing options)
+gpg_keys: []
+
 
 # Publishing
 #############