Account key and domain keys written as files regardless of storage backend?

[fffonion]

Account key and domain keys written as files regardless of storage backend?

[chewi]

Thanks for your quick reply!

I figured out the problem. I hadn't noticed that autossl.init takes two tables and api_uri needs to go in the second one. Other settings like account_email are copied over so this is a bit confusing.

Unfortunately I didn't get my project working in time but I was close so maybe I'll continue it. Some problems stemmed from testing with Pebble and I'll be filing a couple of pull requests to address those. I'll keep this issue open until it is resolved.

[fffonion]

This is already implemented in #16

[fffonion]

Hi @chewi , account key is currently read ad file if defined, or generate on the fly when autossl initializes. Patches are definitely welcomed to load account key from storage backend. You will want to do that in AUTOSSL.init_worker while cosocket api is available.

Domain keys however are always stored together with certificates in storage. (You can use domain_keys_path to desiginite one but that's mainly used for testing, in production you will want omit that and generate different keys per domain on the fly).

Could you share with me an example on how you are using api_uri and it's not effective?