You mean you tried this https://letsencrypt.readthedocs.org/en/latest/using.html#installation and it did not work. I made a try myself when it was just to test (few days ago). It works quite well. I am looking forward to use it on my servers. It really makes deploying https easy and free (including revocation)

I finally found the time to finish the NodeBB port. Now, before submitting it to the official port tree, I am testing it (install, upgrade, etc.). If you feel like you want to test it too, here are the instructions.

Installing NodeBB

In order to install NodeBB using pkg(8), you need to add the nodebb repository (my repository, not an official NodeBB repository as shown by the url). For this, create a nodebb.conf file in /usr/local/etc/pkg/repos/ (create this folder if it does not exist) with the following content :

nodebb: {
  url: "pkg+https://pkg.hukadan.org/${ABI}",
  mirror_type: "srv",
  signature_type  : "PUBKEY",
  pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
  enabled: yes
}

FreeBSD: {
  enabled: yes
}

Next you need to copy the public key of the nodebb repository into /usr/local/etc/ssl/certs/(create this folder if it does not exist). You can find the public key here. I will try to rebuild this repo once or twice a week.

Then, update the repository database and install NodeBB :

% pkg update
% pkg install www/nodebb-devel

It will not install any database so you will have to choose yours, for instance redis with pkg install databases/redis.

For the ones who want to use the ports(7) instead of pkg(8), here we go.

Launch NodeBB

First, launch your database with service redis onestart. Once it is done, you can launch NodeBB using the command service nodebb onestart. You can make it start at boot like any other services by adding the following lines in the /etc/rc.conf:

redis_enable=YES
nodebb_enable=YES

The ordering does not matter. These two lines will make sure that both services are started at boot. Once these lines added use start instead of onestart.

Misc

All the commands you use with the nodebb $arguments are available without modifications using service nodebb $arguments. They work in exactly the same way except for service nodebb upgrade that only update database schema.

NodeBB will be installed in the /usr/local/www/nodebb folder and will run under the unprivileged nodebb user.

For the one that test it, report any problem (or propose improvements) with the package (not NodeBB itself) here :
https://github.com/Hukadan/nodebb-devel-port/issues

Thank you for your participation.

Hello,

I am facing the same problem. Everything works fine except that users are very often having the 503 page. I tried the @AOKP solution by setting to 0ms. Since it did not work, I set both setting (loop lag and check interval) to 80000 but the 503 page showed up anyway at a moment where almost no user is browsing. I thought putting so high values was almost equivalent to disable it. I was wrong. So my question : is there a way to simply disable it ? Before, the users never complained about a laggy browsing so I would not expect this to happen in the first place.

Thanks.

@julian Sorry for the delay but I am working on a new project. For the moment it he has five different methods poo(), pee(), eat(), cry() and sleep() but at the moment the sleep() method is utterly broken and impact my other projects.

Reading the commit message, it does not affect the way the port would be handled. To be honest, I did not get what was the use case of this new flag. To be more specific, I fail to see how you can manage plugins if you do not have direct access to disk. IIRC, it is related to AWS but I am not familiar with Amazon services.

I should resume my work on the NodeBB port next week.

I don't know if it will be helpful to you but I have started to work on a small shell script to save and restore NodeBB. In my setup, NodeBB is installed using the package system so all the modules present in package.json are already present. It just make a difference between what is present and what should be present. Note also that the current version only deals with plugin. This is a bad idea and will change in a near future.

Here is the github repo : https://github.com/Hukadan/nodebbutils/blob/master/nodebbutils

this is a work in progress so use it with care on machines you do not care about (at least for the moment)

Just a shot in the dark but... have you got a npm-shrinkwrap.json file in your NodeBB folder ? If it were the case, it would prevent NodeBB to upgrade properly.

It reminds me an episode of South Park.

@rod Thank you. You can add v1.0.0 <----> 2.15.0 to your compatibility list.

@Schamper Then I had a problem on my setup and this problem is gone.

@Schamper The look and feel of this new version is really nice. Thank you for this update on the behalf of all my forum users and myself.

Just a shot in the dark but... have you got a npm-shrinkwrap.json file in your NodeBB folder ? If it were the case, it would prevent NodeBB to upgrade properly.

@yariplus Now I feel stupid because I never noticed the presence of those options on my profile... Thank you for the quick answer. I still have to check if one of the two discord plugins allow that.

I am considering installing SSO plugins (namely, Discord and Twitter ) on my NodeBB forum. But I am not quite sure about how to integrate this with existing users. My concern is the following : can an user that registered directly to NodeBB use its twitter account (e.g) to login as this specific user ?

I found this old thread on the subject :
https://community.nodebb.org/topic/3112/social-login-and-the-same-user-with-a-different-email

From what I understand, if an existing user that used to login directly to Nodebb with the email address classic.user@example.com tries to login with Twitter using the same email address, it will be authenticated as being the classic user ? Is it right ? Does it depends on the SSO implementation ?

SSO is kind of black magic to me, so bear with me if the question is stupid.

Which operating system are you using ? I had the same message using FreeBSD for no logical reason and I had to disable this functionality.

@ubern00b I think you mistake anonymity (you walking on the street) for privacy (you walking or doing whatever pleases you in your apartment). Posting on different public websites is more related to anonymity than it is to privacy.

@PitaJ , reading again the thread, I think I find the answer.

@torn2 said in [nodebb-plugin-iframely] IFramely Embeds:

@boomzilla You have options on how the card may look when you use their hosting.

So my guess is that NodeBB forum uses the Iframely service while I am self hosting.

Thank you again, your help was appreciated.

By the way, here is the link : https://forum.zqsd.fr:6664/topic/166/les-bon-plans-pc/161

In my case the only CSS (on the test server) is the one you just wrote.

I would have bet my house (if I had one) that I already tried what you just wrote. Apparently I did not. It works just fine now ! Thank you !

Now, have you got any idea why the look is still different between my forum and here ? Does it use specific CSS settings for Iframely ?

@PitaJ said in [nodebb-plugin-iframely] IFramely Embeds:

@hukadan you should be able to do something like

.iframely-link .iframely-container img.thumb {
  max-width: 21px;
}

Thank you for your answer but it did not work.

CSS follows specificity. More specific rules are given precedence.

My understanding of the !important parameter is that it breaks the cascading behaviour and that it is precisely why I can't find a way to modify this using custom CSS. Is this interpretation of the !important parameter wrong ? Why does it work properly here and not on my test forum ?