-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
Allow multiple origins #79
Comments
But I agree that it would make sense to update our option to include some server logic that checks the referrer and adds the correct origin for a list of origins. Or none if there's no matching domain. |
Got it, that makes sense! In my case the wildcard will be perfect. The list of origins would be a useful feature but it also makes a lot of sense that Thank you! |
The next version (v1.6.0) will support multiple domains thanks to @jaryl. |
Hello! Thanks so much for the work on the project, it's extremely helpful to have an open-source self-hosted analytics solution like this.
I'm working on a project where I'd like to track multiple origins with a single Heroku Ackee server. I have config vars set and working:
ACKEE_ALLOW_ORIGIN=https://example.com
But I'd also like to track from a subdomain of this origin:
ACKEE_ALLOW_ORIGIN=https://subdomain.example.com
Either of these configs work on their own, but I can't add both with a comma or wildcard:
Is there any config-var-only solution I'm missing here, or is this feature not available? Thanks again for your time!
The text was updated successfully, but these errors were encountered: