Webroot path should be per domain

[hlandau]

Webroot path should be per domain

[hlandau]

I'd suggest you use symlinks, or add an alias in your webserver configuration. It seems to me to make sense to have one repository on the system for challenge files, so I'd like to stick with that.

By the way, the "standard" webroot path is /var/run/acme/acme-challenge. Files are put here (e.g. for the redirector) if you aren't using webroot mode.

I guess multiple webroots could be supported, but it also seems superfluous. I'll think about it for a while.

[hlandau]

After thinking about it for what according to GitHub is two minutes, I think multiple webroot support would at least be a good refactoring internally. I'll probably at least change it to always try and put files in /var/run/acme/acme-challenge for now, and maybe support multiple custom paths later.

[kkofler]

On recent distributions, /var/run is a tmpfs (actually a symlink to the tmpfs mount /run), so if one symlinks $VHOST_WEBROOT/.well-known → /var/run/acme (or $VHOST_WEBROOT/.well-known/acme-challenge → /var/run/acme/acme-challenge), that symlink will point to nowhere after a reboot. The dangling symlink might actually be mostly harmless, but I thought it's worth pointing out.

[hlandau]

I've added multiple webroot support. No support in the quickstart interface at this time, you'll need to edit the file in conf. One path per line. Challenges will be deposited in all of them. v0.0.14.

[hlandau]

See also: #25

[kkofler]

How about something like:
acmetool --challenge-dir=/path/to/.well-known/acme-challenge want example.com
(which of course should remember the setting in the config files)?

[hlandau]

Not sure what you're asking; you can set the path via quickstart or via editing the conf dir. I haven't implemented it per-domain; it just drops a given challenge file into all configured directories, which is fine. I don't think there's much point segmenting it by domain. It's not like there's a performance or disk usage issue.