-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add "single domain mode" for easier self-hosting #120
Labels
Comments
Closed
arp242
added a commit
that referenced
this issue
Jan 28, 2020
Basic TLS support based on .pem files. I looked at doing ACME, but it's rather complicated as this requires dns-01 verification, which requires setting a "_acme-challenge.domain.com" record. https://github.com/go-acme/lego includes support for this, but it still requires giving lego (and thus goatcounter) API access to the domain, which is rather meh. I solved this on goatcounter.com using CNAME to an unimportant domain: - goatcounter.com is managed by TransIP. - goatcount.com is managed by CloudFlare (it's the only domain on my account there) - _acme-challenge.goatcounter.com is a CNAME to goatcounter.goatcount.com - In the dns-01 verification we set the goatcount.com address, so we only need to have the cloudflare API keys. I think the best solution is to implement #120 first. With that, we don't need to muck about with wildcard certs, and can just use http-01 challenge for one domain.
arp242
added a commit
that referenced
this issue
Jan 28, 2020
Basic TLS support based on .pem files. I looked at doing ACME, but it's rather complicated as this requires dns-01 verification, which requires setting a "_acme-challenge.domain.com" record. https://github.com/go-acme/lego includes support for this, but it still requires giving lego (and thus goatcounter) API access to the domain, which is rather meh. I solved this on goatcounter.com using CNAME to an unimportant domain: - goatcounter.com is managed by TransIP. - goatcount.com is managed by CloudFlare (it's the only domain on my account there) - _acme-challenge.goatcounter.com is a CNAME to goatcounter.goatcount.com - In the dns-01 verification we set the goatcount.com address, so we only need to have the cloudflare API keys. I think the best solution is to implement #120 first. With that, we don't need to muck about with wildcard certs, and can just use http-01 challenge for one domain.
arp242
added a commit
that referenced
this issue
Feb 5, 2020
TODO: - Manage additional sites (maybe just disable this?) - Don't display code in Settings, change "custom domain" text. - Remove help etc. from footer. - Don't reserve domains. - Don't show "delete account". Fixes #120
Implemented with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now self-hosting GoatCounter is a bit more complicated than it needs to be because it assumes you want to run a SaaS, like GoatCounter.com
This doesn't apply to most self-host instances, it should be easier to set this up. For example:
That will just serve domain ID 1 on any domain (i.e. it won't attempt to check subdomain codes and whatnot). There should also be a command to create a site (
goatcounter -init-singledomain
).Depends on #108.
The text was updated successfully, but these errors were encountered: