As long as you migrate the .rdb database (download, then upload to new instance) and carry over your existing redis.conf you can migrate without issue.

How to deploy Iframely API to your own servers

Self-host the open-source web embeds parsers for hundreds of domains

Iframely (iframely.com)

I still haven't worked out a few kinks, but I've been able to get it up and running on my site. It's not as effective though for normal sites. Take a look at the link above.

Here's what a non-paid embed for the same page looks like on my site:
http://prntscr.com/amjy3w

I recently posted a topic in the Testing Area with more examples - though things went as expected there.

That's an interesting undertaking. I look forward to hearing more as this project develops.

@julian said

In any case, I've used webroot with multiple -d arguments before... hopefully there are no issues with that, since I defined upwards of 20 domains for that cert!

Oh my. That's quite extensive.

I took some time tonight to test out implementing both camo and a self-hosting of iframely in a development environment. At first, I had some issues when using the NGINX config generated by this plugin (hey, if it's in plugin form, why self-install ;)). After simplifying my config to be more in line with my original (very similar to @yariplus') the plugin operated without issue.

Between camo being so easy to implement with NodeBB and Let's Encrypt, I expect that we'll see even NodeBB beginners follow security best practices more closely.