I can't see any documentation in the repo for how to go about creating a new tree.

The preferred mechanism to create & init a tree is now:

go run cmd/createtree/main.go --admin_server=${ADMIN_SERVER}

This isn't mentioned in any documentation. The closest we have is a pointer to https://medium.com/google-cloud/trillian-on-google-cloud-platform-621a37f2431c which does this the legacy way in

The following things should be fixed:

• Inserts that trigger an upsert should be logged as an update
• An update should log the identifier/value the old value (or none) and the new value, eg: column: old => new
• Avoid duplicate code for scoped/unscoped that only differ in color codes

Also, consider:

• Reuse the one-line representation in select as a base for detailed

I think the entire PEM-encoded certificate chain should be fed to the script over stdin. Cert Spotter should ignore broken pipes in case the script closes stdin before reading anything. Question: what if the script forks with stdin still open and never reads?

Follow up to letsencrypt/ct-woodpecker#5

We should also have the certSubmitter submit multiple copies of the same new cert in parallel. If distinct SCTs are returned then all of them should be stored and checked for inclusion.

Can we get a script, which calls submit-cert.py and automatically calls write-sct.py with the correct parameters afterwards to write the .sct file.

BTW: Is it useful to do this for all responses you got from all certificate transparency servers? Is it useful to include all those logs in CT?