News

Introducing New rtCamp Community Portal

Some users might have noticed, that we have moved our community support forum from bbPress to Discourse. New community support forum has its own subdomain – http://community.rtcamp.com/

rtCommunity

About Discourse (new platform)

Discourse is based on ruby-on-rails framework. It offers many out-of-the-box features like:

  1. Better built-in search. It is even better than Google Custom Search. Of course, YMMV.
  2. Reply-by-email. Also, posting by email can be opened to all or trusted users. This is useful if you like to run a mailing list which gets synced to web-based forum.
  3. Better navigation with infinite scroll. Okay this can be done with a bbPress theme but speed and reliability of Discourse is amazing.
  4. Keeping track of how many replies you have read. Good while browsing through long discussions.
  5. Bookmarking/Starring of favourite topics.
  6. Better control on how you participate in discussions using with 4-different levels/types of notifications.
  7. Better support for attachment. You can copy-paste images using CTRL+C and CTRL+V. Also much better drag-n-drop upload.
  8. Support for markdown syntax with realtime preview and a stack-overflow style minimalistic visual-editor toolbar.
  9. Starting related topics so you can go “off-topic” but still keep a reference to old/actual topic.
  10. Community wiki support so a topic can be converted to wiki.
  11. Better admin dashboard with mini analytics, backup/restore, outgoing email logs, user activities, etc.

This is just my day two on the new community portal and I am loving it. There is a lot more that Discourse offers which I haven’t explored yet. But our developers and support team are already enjoying the new platform.

What about old data?

We have moved every piece of information including…

  1. Private Replies – We were using bbpress-private-replies plugin (by Pippin) for private replies. We exported all private replies to excelsheet and replaced content of all of them with a note and post_id. This way, if we need to refer to any private reply, we can refer to it in future.
  2. rtMedia bbPress Attachment – We were using rtMedia-PRO for bbPress attachment support. We have appended links to actual attachment files towards end of content (topic/replies)
  3. Core bbPress users, forum, topics and replies – They are all exported safely. Only thing is that users will need to reset their password (using forget password option) or can use Google-login option provided on new portal.

We used bbpress-to-discourse importer by David with some changes. rtCamp allowed email addresses as username in 2009-10. Some user account from that legacy were not getting migrated.

So we updated that portion of importer and also added support for rtMedia bbPress attachment to importer. Our version of importer is here.

The only real painful point in migration was size of community. We have 17,000+ registered users and 11,000+ topics and replies. If something went wrong, I had hard time starting over again!

Credits

We are grateful to Jeff Atwood, Sam Saffron and all discourse contributors for this awesome script.

Special thanks to Arpit Jalan who helped a lot at many steps. 🙂

We also thank docker team. Running rails app is complex affair (atleast for me). Docker container made it easy. It added it’s own issues as well. Most notably aufs support issue. This issue means, if you are comfortable with Docker or Linux Kernal hacks, stick to DigitialOcean for Discourse hosting.

Docker has its own learning curve but the whole idea seems so nice that we are planning to use docker in another project of ours.

For now, enjoy new community portal and let us know your feedback. 🙂

Links: Community | Discourse | bbPress to Discourse script (with rtMedia Support)

Discuss your project
with our experts

No obligation. Limited slots.

Contact Form Business Enquiry

"*" indicates required fields

Please attach any RFP, project specification, or document that you would like to share.
Drop files here or
Max. file size: 5 GB.
    This field is for validation purposes and should be left unchanged.