Dynamically configure new vhosts for ejabberd #100

New Issue

raucao · 2019-09-19T11:10:36Z

raucao commented

2019-09-19 11:10:36 +00:00

I just found a way that we could do this: write a new vhost config file and then only write one additional line to the main config:

https://docs.ejabberd.im/admin/configuration/#include-additional-configuration-files

It's also possible to blacklist or whitelist options that can be set in the additional file. Furthermore, we can define macros to re-use shared options.

(That still doesn't solve the TLS certificate question for main domains, of course.)

I just found a way that we could do this: write a new vhost config file and then only write one additional line to the main config: https://docs.ejabberd.im/admin/configuration/#include-additional-configuration-files It's also possible to blacklist or whitelist options that can be set in the additional file. Furthermore, we can define macros to re-use shared options. (That still doesn't solve the TLS certificate question for main domains, of course.)

raucao commented

2019-10-10 17:01:36 +00:00

Tadaaa, the solution for TLS certs:

Instead of giving the digest value to your new customer and telling them to make a TXT record with it, tell your customer to configure a CNAME from _acme-challenge.www.example.com to a domain name that you control and that is unique to the domain being validated

https://letsencrypt.org/2019/10/09/onboarding-your-customers-with-lets-encrypt-and-acme.html

I think this is the way to go, unless I'm missing something.

Tadaaa, the solution for TLS certs: > Instead of giving the digest value to your new customer and telling them to make a TXT record with it, tell your customer to configure a CNAME from _acme-challenge.www.example.com to a domain name that you control and that is unique to the domain being validated https://letsencrypt.org/2019/10/09/onboarding-your-customers-with-lets-encrypt-and-acme.html I think this is the way to go, unless I'm missing something.

greg commented

2019-10-11 08:04:22 +00:00

That looks like a great solution indeed

raucao changed title from ~~Dynamically configure new vhosts~~ to Dynamically configure new vhosts for ejabberd

2020-02-07 17:22:07 +00:00

raucao added the

feature

label 2020-10-19 18:10:13 +00:00

raucao added the

service

xmpp

label 2020-12-09 13:07:30 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#100