Normally we host Discourse sites using a subdomain, e.g.
However we have a customer who wants
So we’re building out support for that. One thing we’ve run into is that this complicates the hosting scenario considerably, as
discourse.example.comcan point to a completely different IP address on our servers. This works great for hosting.
example.com/discoursehas to point to their domain. Not great for hosting. So this means either
we host their entire domain (not desirable for many reasons)
they proxy just the traffic in the
/discoursefolder to our server’s IP, which is complex and error prone for them.
We use Fastly as our CDN and have had great results with it, so we’re wondering, can we recommend they also purchase a Fastly plan, and use Fastly in front of their domain both as a CDN and as a proxy solution?
This would keep the complex proxying in the hands of third party experts (namely, Fastly), and we could share access to the Fastly credentials so we can both troubleshoot if something goes wrong.
Any tips for this kind of configuration, where you want to put a subfolder in control of a different IP address on the internet? Are there big price disparities if they need https vs http for this function?
Please sign in to leave a comment.