alex

Ok, let's go with a separate `acme renew`. The command usage text will be simpler, too, as it'll require less flags.

AFAIK re-issuing a cert does not revoke the existing one, so it should be safe. But, like you said, we can always add '-force' arg to `acme cert` in the...

@jdub what is it exactly that you'd need? `acme cert ...` using an account which was previously granted the authorization for a domain will create a new certificate, effectively doing...

if you have already issued at least one certificate in the past, the next time invocation of merely `acme cert `, i.e. without additional flags like -dns, will give you...

That is strange. I've just done it about 30 min ago. Are you sure you used the same account? The reason it works is, Let's Encrypt remembers all identifiers (domains)...

@chr4 I don't think so. This bug is just a helper to renew the certs easier. But it should already work regardless. What challenge type are you using?

Thanks for this. Quite useful. I would make it an additional command line arg first and then add `ACME_CHALLENGE_DIR` as an alternative way of defining flags. Otherwise, we start mixing...

Right, there's indeed `ACME_CONFIG` but it's an alternative to `-c` cmd line flag. We could replace `-s host:port` flag with `-l `, trying to avoid too many flags. wdyt?

> Is there a scenario where it is useful when it's possible to specify the path using a flag? Well, yeah. for instance, https://getmdl.io is served from a [GCS](https://cloud.google.com/storage/) bucket...

Forgot to add, having `-http01-dir` arg will also allow future implementations for non-fs storages: ``` # GCS bucket -http01-dir=gs://bucket # AWS S3 -http01-dir=s3://bucket # ssh/scp -http01-dir=ssh://user@host:path/to/root ```