-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support rails relative_root_url #26
Comments
This gem is based on Rails Engine, but I am not sure the Rails is supported There have a rails/rails#31476 discuss it, but the PR seems not active and didn't be merged. |
@elct9620 I dug into this one a bit more, I don't think it's possible. The ACME challenge requires this to be at the root of the domain: There could be support for a DNS-01 challenge, which the ACME client does support: If I put together something to support multiple DNS services with a setup for Route53, would you be open to a PR for that? |
This gem depends on the Rails Engine, it didn't directly use The DNS support is required the plugin support for this gem and changes the current flow. For example, we may want to add Route53, CloudFlare support, but it adds a lot of dependency for others didn't need it. |
I create an issue (#27) for DNS-challenge feature. |
Doesn't seem like this gem supports this configuration:
https://guides.rubyonrails.org/configuring.html#deploy-to-a-subdirectory-relative-url-root
it always assumes the engine can be mounted at
/.well_known
The text was updated successfully, but these errors were encountered: