I’m not sure I understand the difference either, but it’s good enough that my self-hosted miniflux install can see it, and the pictures at least load.
Interesting. Feedburner emails don’t have photos, which is the way I usually interact with RSS on my site. Good to know it’s at least working for some people!
What made you use Jekyll instead of one of the numerous other static-site systems? What else did you compare it to?
I looked at Hugo and Pelican, and mostly went with Jekyll because it directly imports from Blogger. I could move to the others if I wanted, but I don’t see a huge point. I’m pretty sure Jekyll is slower than the alternatives, but I just don’t care that much.
I spent about a month looking around at options and how to do stuff before deciding to just sit down and do it. I probably have 20h in the migration at this point, if not more, but it’s done and I don’t intend to do it again any time soon.
Ignoring speed and the importing, if you were starting from scratch, do you think you would have gone with one of the others?
I don’t know enough about the others to say.
I’m not a web dev. Wrangling blog moves with static site generators, HTML, Python scripts, etc, is something I don’t enjoy doing. I used to do web dev back in the early 2000s, but I’ve not touched it in most of a decade, and tbh almost everything I’m using is utterly foreign to me. Ruby, Gems, etc. It works, but I don’t entirely understand the plumbing, and I’m not at all certain how to hack on it.
I expect if I really wanted to, I could migrate from Jekyll to something else, but I see no reason to do so, or I would have done that in the first place.
There are plenty of people who enjoy comparing static site generators - I’ve read many of their posts. But I’m not one who has strong opinions beyond “I would like to get something working so I can get back to writing interesting content.” What I have now seems good enough for that.
Another issue noted: The “onebox” summaries don’t work.
I get the following trying to link to posts:
Sorry, we were unable to generate a preview for this web page, because the following oEmbed / OpenGraph tags could not be found: description, image
Links work fine, but… I’ll have to figure out the head section entries for that.
While not specifically blog related, I think I’m going to move images from Conversation to a CDN - Google Cloud Storage or similar. That should reduce my bandwidth needs for Conversation significantly, as part of a planned migration to local hosting.
I’ve unmuted the blog comment category, since there’s now enough topic above that dump to be something useful. Let me know if it feels too blog-comment-thready, or… just bump older stuff, if you feel so inclined. 
As a side note, I was logged out, and then logged in and got redirected to http://conversation.sevarg.net - note the lack of https - which gave me a default nginx page.
A similar thing is happening with the little blog logo: http://conversation.sevarg.net/uploads/default/original/1X/8fc8b8863735923424aa95ff4d67c64a708265ed.png
Good catch, thanks. The http to https redirect for Conversation was missing - apparently hsts made my browser just use https. Try now, please!
1 Like
Ah, that email box isn’t monitored… I should set it up to forward stuff to me, thanks!
I think the problem is that Discourse actually only serves over HTTP - there’s a proxy in front of it.
I just set force_https - can you see if that resolves it for you? I actually don’t see mixed content warnings or anything from my browsers.
//EDIT: Ok, found one for logos, it seems that re-uploading after setting force_https solves it. Try now?
//EDIT2: Ok, more issues with login fixed. Let’s see if that works.
Yay! It’s working now. Mixed content issues seem to be fully resolved. Thanks!
1 Like
Great, thanks for the feedback! I’ve routed the email to my account as well, so hopefully reports will actually get to me in the future.
For those curious, most of the issues from the server move are related to http/https. Previously, everything was exposed, it ran https internally, and managed its own cert. With the new server, the SSL termination is done at the frontend, and it proxies things to Discourse, which is running in a VM, http only. So the http link is internal to the system. However, Discourse didn’t quite understand this, and there were a few mixed content related issues as a result. I had to enable force_https on Discourse (“Look, I know you think you’re http, I don’t care, you’re https, use it”), have the proxy report that it was really passing https traffic back, and reupload the top images for some reason. That seems to have fixed it.
Ok, added SEO tag support for Graph Whatever, which means blog previews should work properly.
Now, if I link a post, it should actually have the proper image and such!
I’d recommend making it easier (I know there’s a link at the bottom) to get from the forum copy of each blog post to the blog post itself since the forum versions of the blog posts aren’t formatted as nicely and lack images.
That might be as simple as also putting a link at the top of the forum post - which could communicate that the best reading experience can be had on the blog…
“This is a companion discussion topic. For the best reading experience see the original entry at {url}”
1 Like
That’s a good idea. I’ll see if I can automate it, otherwise it’s easy enough to manually add it.
2 Likes