You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have basic analytics of podcast listeners.
I'm currently planning on generating the RSS feed in Hugo from the posts. This will be a separate url, perhaps available at "www.pure-pandemonium.club/podcastrss.xml".
I don't know how to set up server-side code to add custom handling for a specific URL hosted by our website, so I suspect we'll have to set up an HTTP proxy which logs the HTTP request to Google Analytics or where-ever, and forwards the request to the real RSS feed.
So, the next easiest way to do add custom server code on our domain is a new subdomain, perhaps "rss.pure-pandemonium.club", which reverse-proxies to whatever URL we put it at on Hugo, like "/podcastrss.xml". If we do this, we would set up a Google Cloud Function or AWS Lambda Function, then put a DNS record in to resolve "rss.pure-pandemonium.club" to the URL given to us by the function hosted by that FaaS provider
I think it's pretty important to maintain control over the URL we advertise as our RSS feed, and doing it this way seems like a good balance of simple, low-cost, and retaining control of the advertising URL.
Any thoughts?
The text was updated successfully, but these errors were encountered:
I would like to have basic analytics of podcast listeners.
I'm currently planning on generating the RSS feed in Hugo from the posts. This will be a separate url, perhaps available at "www.pure-pandemonium.club/podcastrss.xml".
I don't know how to set up server-side code to add custom handling for a specific URL hosted by our website, so I suspect we'll have to set up an HTTP proxy which logs the HTTP request to Google Analytics or where-ever, and forwards the request to the real RSS feed.
So, the next easiest way to do add custom server code on our domain is a new subdomain, perhaps "rss.pure-pandemonium.club", which reverse-proxies to whatever URL we put it at on Hugo, like "/podcastrss.xml". If we do this, we would set up a Google Cloud Function or AWS Lambda Function, then put a DNS record in to resolve "rss.pure-pandemonium.club" to the URL given to us by the function hosted by that FaaS provider
I think it's pretty important to maintain control over the URL we advertise as our RSS feed, and doing it this way seems like a good balance of simple, low-cost, and retaining control of the advertising URL.
Any thoughts?
The text was updated successfully, but these errors were encountered: