Nima Eskandary

We should verify with @rebstar6 or @pauljamescleary, but believe we want to keep those change histories forever regardless of zone deletes

Hi Dave, thanks for the suggestion! I agree that more powerful searching would be useful for Administrators. The way the listing of zones is done from the API is that...

This seems to be an issue faced from the DynamoDB implementation since it was seen from a local `api/reStart`, but investigating the sql code that repo likely has the same...

may be able to get rid of that script all together and use a docker compose health check (https://docs.docker.com/compose/compose-file/) e.g. adding something like ``` healthcheck: test: ["CMD", "curl", "-f", "http://localhost"]...

@pauljamescleary I have not tried it myself, though this thread https://stackoverflow.com/questions/31746182/docker-compose-wait-for-container-x-before-starting-y does describe the behavior as component `b` will not start until component `a` is healthy if `b` depends on...

Note that when releasing to Docker Hub we will all have keys on notary, we should list our key ids wherever we put this too

In the developers guide I added a section for our notary keys

Looking into this, it may be that akka always returns UTF-8 as the charset in httpentity but will have to confirm later with some tests

I think we need to investigate if this is done for any other headers other than charset. It may be a spec that UTF-8 should be uppercase

For this case I think the model akka uses to pull it does not give you access to the case of the inputted charset from the request https://github.com/akka/akka-http/blob/master/akka-http-core/src/main/scala/akka/http/scaladsl/model/MediaType.scala#L344, e.g. application/json...