@kenygamer Everything you need to know to host nodebb is written here. If this sounds too obscure or you are not willing to learn consider purchasing a nodebb hosted solution from nodebb.com or any other nodebb hosting provider.

You are right. Same with any third party hosting provider. You have to balance the cost of hosting the pictures to your own server with the risks.

On the other hand if you can't afford hosting the pictures on your own infrastructure, you have to balance the fact you have a single point of failure in imgur with the fact that without an official upload function your user would be encouraged to upload them somewhere else with the risks of broken links if said users remove the pictures later on.

FWIW there are tools to download imgur album. You could run these tools on an inexpensive NAS server at home which would give you a cheap backup and an option to host them somewhere else and convert broken links if imgur goes bankrupt in the future.

@baris First of all thanks for the great work. Is there any plan to update this plugin ? Since imgur provides way to get thumbnails link by appending a simple letter suffix to the basename, here are 3 features I can suggest.

1. Adding an option for the user to choose one of the available imgur thumbnails instead of the full size image
2. Adding an option for an admin to choose a mandatory maximum thumbnail size
3. Best would be adding an option so the plugin create a clickable thumbnail that link to the full size image, i.e. something like [![imgur](http://i.imgur.com/pictureh.jpg)](http://i.imgur.com/picture.jpg)

Surely I'm not the sole nodeBB admin with some photo heavy threads that would like to force the user to use the huge thumbnail (which in reality is only 1024x1024) instead of the full size image so that mobile and low bandwith users can load the pages faster.

For what its worth I upgraded nodebb to 1.4.4 without changing the nginx config to handle the static content. I will do it in the near future but I need to change my docker setup. So don't be afraid to migrate without changing your reverse proxy settings.

Standard recommendations about doing backups (and test restores) applies.

Hi,

I would like to know if there is a recommended way to merge two nodebb forums ?

I converted some threads using the mybb import plugin but the original db was so big I ran into issues (plugin crashing) and couldn't convert the whole forum. I limited my import to the most popular threads, keeping only posts less than 1y old and it worked. But it was so time consuming that I decided to upgrade nodebb instance and made it available to users. Since the import plugin requires nodebb v1.0.0 my idea would be to create a new nodebb instance with its own mongodb and import the remaining threads/posts, then upgrade it to the same level as our "production" one and try to merge the imported threads to the "live" nodebb.

Has any nodebb merge been done before ? Suggestions ?

Thanks
Thomas

@Florian-Müller said in Ban single Users from Category:

@julian Do you see an easy/nice way how to solve this problem?

A not very practical way would be to create a group for each category. Unless you write a plugin or script to ease the pain of management it will be headache inducing.

I would also be interested in being able to exclude a category from the new messages notifications. Our community host a "classified ad" section. It is nice but generate a lot of noise that many users would like to be able to ignore easily.

Sorry for the late reply,

I will look at creating some additionnal swap space before importation. I didn't monitor memory usage during initial attempts.

I will try first with a smaller sample and will send it to you if duplication still happens. I used asciicat's mybb exporter.

Thanks

Has anyone managed to import a fairly large mybb forum with the importer ? I wanted to migrate from an old mybb1.6 forum with ~5000threads, 15000 members and around 1.5M individual posts. I first migrated that forum to mybb1.8 then installed nodebb 1.0.0 as per the nodebb-plugin-import github readme.

The import works for a while but nodebb eventually crash before all the posts are imported.

I tried cleaning up the original database with only sticky threads + threads whose latest post was less than 2y old. Still didn't manage to do a successfull import. Sadly resuming the import creates duplicated threads.

One physical machine with 16GB of ram, original database in a mariadb docker container, destination DB on mongodb 3.4.1 running in the official docker container, nodebb on another docker container based on the official ubuntu xenial image.

Thanks
Thomas