RFC: domains.txt format #11

New Issue

adam · 2025-12-29T00:21:45+01:00

adam commented

2025-12-29 00:21:45 +01:00

Originally created by @LynxChaus on GitHub (Dec 8, 2015).

It's possible to change domains.txt format to include webroot type domain aliases?
i.e.
/var/www/example.org/ apache example.org www.example.org
/var/www/example.net/ nginx example.net www.example.net other.example.net
/var/www/common/ mail mailhost.example.org webmail.example.org

and modify hook calling to pass webroot and type to it.

Originally created by @LynxChaus on GitHub (Dec 8, 2015). It's possible to change domains.txt format to include webroot type domain aliases? i.e. /var/www/example.org/ apache example.org www.example.org /var/www/example.net/ nginx example.net www.example.net other.example.net /var/www/common/ mail mailhost.example.org webmail.example.org and modify hook calling to pass webroot and type to it.

adam closed this issue

2025-12-29 00:21:45 +01:00

adam commented

2025-12-29 00:21:46 +01:00

@lukas2511 commented on GitHub (Dec 8, 2015):

I like the idea, but i don't like the format.

Maybe something more like this which allows those parameters to be optional:

example.org www.example.org WEBROOT=/var/www/example.org USERINFO=apache
example.net www.example.net WEBROOT=/var/www/example.net
example.mx www.example.mx USERINFO=mail
example.com www.example.com

But maybe someone has an even better idea...

@lukas2511 commented on GitHub (Dec 8, 2015): I like the idea, but i don't like the format. Maybe something more like this which allows those parameters to be optional: ``` example.org www.example.org WEBROOT=/var/www/example.org USERINFO=apache example.net www.example.net WEBROOT=/var/www/example.net example.mx www.example.mx USERINFO=mail example.com www.example.com ``` But maybe someone has an even better idea...

adam commented

2025-12-29 00:21:46 +01:00

@M-M-M-M commented on GitHub (Dec 9, 2015):

I like the format of optional parameter PARAMETER=value

And passing these parameters as environment variables to hook script will be great and avoiding to surcharging hook parameter command line.

@M-M-M-M commented on GitHub (Dec 9, 2015): I like the format of optional parameter PARAMETER=value And passing these parameters as environment variables to hook script will be great and avoiding to surcharging hook parameter command line.

adam commented

2025-12-29 00:21:47 +01:00

@LynxChaus commented on GitHub (Dec 9, 2015):

Add minimal parser a0e62a4bca

Any suggestion?

@LynxChaus commented on GitHub (Dec 9, 2015): Add minimal parser https://github.com/LynxChaus/letsencrypt.sh/commit/a0e62a4bcabe30e976b72e97898bbbd2baf62761 Any suggestion?

adam commented

2025-12-29 00:21:47 +01:00

@lukas2511 commented on GitHub (Dec 14, 2015):

@LynxChaus from reading your parser it looks like it just supports things like VAR=value, but i'd like to also see support for VAR="value value value" and/or escaped values like VAR=value\ value\ value.
I think splitting the line at the right point and just passing it through declare would solve this.

@lukas2511 commented on GitHub (Dec 14, 2015): @LynxChaus from reading your parser it looks like it just supports things like `VAR=value`, but i'd like to also see support for `VAR="value value value"` and/or escaped values like `VAR=value\ value\ value`. I think splitting the line at the right point and just passing it through declare would solve this.

adam commented

2025-12-29 00:21:50 +01:00

@lukas2511 commented on GitHub (Jan 22, 2016):

This actually could be replaced by putting extra config files into the certificates directory. This may actually also be useful for storing per-certificate options like RENEW_DAYS and PRIVATE_KEY_RENEW. That would make this a lot easier to implement and it wouldn't have the whitespace issue.

@lukas2511 commented on GitHub (Jan 22, 2016): This actually could be replaced by putting extra config files into the certificates directory. This may actually also be useful for storing per-certificate options like RENEW_DAYS and PRIVATE_KEY_RENEW. That would make this a lot easier to implement and it wouldn't have the whitespace issue.

adam commented

2025-12-29 00:21:50 +01:00

@lukas2511 commented on GitHub (Jan 22, 2016):

Closing this, see #105 for a replacement for this.

@lukas2511 commented on GitHub (Jan 22, 2016): Closing this, see #105 for a replacement for this.

adam referenced this issue

2025-12-29 01:28:20 +01:00

[PR #11] [MERGED] fixed logic to check status from our challenge #658

Sign in to join this conversation.