I followed the instructions on how to embed Discourse as a comment engine by @eviltrout and I’m having some issues that I can’t seem to resolve on my own. I’m hoping that someone here can point me in the right direction.
About the Setup
My domain points to a static GitHub Pages organization site baked with Jekyll. The root domain is configured, as per GitHub’s instructions, with two
A records. The
www sub-domain is configured with a
CNAME record. Both the apex and sub-domain point to the same place.
My Discourse installation is using the DigitalOcean 1GB / Docker setup. The
discourse sub-domain is configured with an
A record that points to the IP of my droplet. I am using version 0.9.9.12 of Discourse.
Here is my Discourse embedding configuration:
Here is the client bit:
When I push a new post to the blog, it takes forever to show up as a topic on Discourse. Yesterday, after completing the configuration, it took several hours for the one blog post we have to show up in Discourse. Today, after pushing two new blog posts at the same time, the first showed up almost immediately while it has been at least an hour and a half and the second post has yet to show up.
Additionally, when I visit a blog post that does not have a corresponding topic in Discourse, this is the result:
Loading Discussion... message is displayed in the iFrame for a minute or two, then the above error is displayed in the console. I thought I read somewhere that when a post is visited, the topic would be automatically created if it doesn’t exist. I could be wrong about this.
Also, I don’t know if this is related or not, but when I type in my root domain, I notice that the browser will flash for a split second the
www prefixed sub-domain. I read that GitHub will automatically create redirects between the apex and www sub-domain.
Any help would be greatly appreciated! Thanks