Can we create a post for vote with nodebb?

Since community.nodebb.org are for discussing the platform of NodeBB, it probably make sense to have a group that is whoever has a verified nodebb deployment and as admin. Having such group will help motivate more people to ask questions, help those site admins and also a promote a culture of community target: the "user" of NodeBB software itself: the site admins of NodeBB.

I checked the group and it seems it doesn't exist yet.

WDYT?

@baris Greetings everyone. I am new year and I am using NodeBB to build a personal forum that could in the future power a bunch of communities that I co-founded.

My nodebb instance is deployed at bbs.zzn.im

Can you also print the package-lock.json and the node --version?

@PitaJ I have not tried using a different sharp version, if you test it, please let me know. I have confirmed that using node < 12 works

Thank you for the idea of SEO.

a. I agree with @julian there are philosophical disagreement
b. agree, adding Google schema support could be built-in like we have seen FB open graph is built-in
c. not a forum, try other software
d. would be helpful, could be done by a plugin. Argueable could be built-in too, IMHO
e. I have nothing against but I think it would be a large project because I could picture some addition live ML and log mining needs to be developed for this to be generalized, and could complicate the core NodeBB a lot.
f. not a forum, sounds to me a social network
g. has been done by plugin and you could pretty much develop it yourself.
h. not thing against it, I think it currently works.
i. it's more of a site operating and community engagement strategy
j. not a forum
k. Good idea, could be done by plugin
l. This is already in place, right
m. good idea. I don't see why not but I assume it already works
n. same as k

It's ok we chat here so other people can see it and maybe benefit from our experience.

@360 said in Need help in installing NodeBB on Heroku:

SO UP UNTIL NOW - DISAPPOINTED FROM NODEBB

I was able to install it on to Heroku with this
https://docs.nodebb.org/installing/cloud/heroku/

I did get some error here an there. Follow these two posts and check if you have encountered similar issues.

• https://community.nodebb.org/topic/14676/just-setup-my-first-bbs-with-nodebb
• https://bbs.zzn.im/topic/3/new-site-setup-journal

Can you put logs here?

First of all, a new fan and really love the design principles of NodeBB!

I might be too new to comment and make suggestion, but since I encountered

• v8 issue caused by sharp incompatible with nodejs 12,
• [email protected]

I wonder is it an option for the team of NodeBB to consider locking the dependencies version or publish package-lock.json for a production version release?

@gotwf You are absolutely right. I certainly agree with you a dedicated tool instead of built-in with NodeBB will be better.

What I argue is that the platform software community like NodeBB comes up with customization or a collection of recommendation of existing tool-sets that will get the deployment security to the certain level. For example, common mistakes of new admins of NodeBB: if you've uses NodeBB default password for the admin password, or turned on Sandbox feature that's not meant for production.

And thank you for your list of tools. That's very helpful.

Reading this as a new NodeBB site admin I really appreciate the suggestion. I think it would be greatly helpful if something like NodeBB or Discourse as a platform label provide tools for scan and auditing common security breaches for new setups, mostly due to use default values in credentials and by passing firewalls etc.

I understand as open source softwares, Pull Request is better than suggestion, but let me put this suggestion here. Maybe it will encourage some white-hat hacker sometime in the future.

I am moving this to https://bbs.zzn.im/topic/3/new-site-setup-journal

I am having the same issue with Heroku deployment when using SSL (managed by Heroku).

This is now fixed by https://github.com/NodeBB/docs/pull/36 and merged

I created a PR for updating the documentation

https://github.com/NodeBB/docs/pull/36

I am following https://docs.nodebb.org/installing/cloud/heroku/#keeping-it-up-to-date to install on Heroku. And at the step

./nodebb setup

It's said that

#...
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.0/libvips-8.7.0-darwin-x64.tar.gz
prebuild-install WARN install No prebuilt binaries found (target=12.16.1 runtime=node arch=x64 libc= platform=darwin)
  TOUCH Release/obj.target/libvips-cpp.stamp
  CXX(target) Release/obj.target/sharp/src/common.o
In file included from ../src/common.cc:27:
../src/common.h:78:20: error: no member named 'Handle' in namespace 'v8'
  bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
#...

It seems because the node version I use is 12 and according to https://github.com/lovell/sharp/issues/1683, node 12 removes namespace v8. Unless sharp is upated per https://github.com/lovell/sharp/issues/1683#issuecomment-497553995, we need to make sure the node version needs to be <12

I changed to use node 10, and it works.

This issue is technically resolved in NodeBB v1.13.2

That's great! Thank you Julian. I was just wondering, has anyone ever attempted to create a DigitalOcean image or applet for easier deployment?