Ah, I got ya, lol. Yeah, it all came together.

Thanks. : D But... wait, I was blocked??

Hey there,
I created this plugin because I have several domains added to my GSuite account and with the current gmail provider you could only send email out through the address in which your login was, not from other domains you might have as aliases which you send and receive from in your inbox. This plugin allowed me to send out emails from other domains!

It is my first go at making a plugin, but I have been using it for 2 weeks or so without any issues. I wanted to make sure things were good first before I posted anything about it. If anyone finds anything wrong with it, definitely do let me know. I am not new to programming exactly, but I had not used NodeJS before so I had to learn it as I went along, so if anyone requests any major changes or anything, it might take me a few minutes to figure out how to do it, lol.

Thanks,
-MH

GitHub - instance-id/nodebb-plugin-emailer-gmail-oauth2: An emailer plugin for NodeBB using Gmail Oauth2 as a third party service

An emailer plugin for NodeBB using Gmail Oauth2 as a third party service - instance-id/nodebb-plugin-emailer-gmail-oauth2

GitHub (github.com)

I appreciate the reply. It looks like after a bunch of tinkering, it seems to be working. I put the plugin into one of the persistent folders, then made a script that I execute via Docker-Compose just before I call grunt which handles the actual linking and then it showed up.

Hello all,
I am running my board through docker and I have been fighting with Docker a bit trying to get things to work.

Firstly, I added a line to the Dockerfile of:

npm i grunt grunt-contrib-watch grunt-cli

Then I also have this persistence setup within compose.

volumes:
            - nodebb_dev_plugins:/usr/src/

nodebb_dev_plugins:
   driver: local
   driver_opts:
     o: bind
     device: /home/myuser/devtools/nodebb/nodebb-dev/plugins/src

This then puts my plugin just outside of the /usr/src/app folder, so then I can docker exec -it into the container and npm link my plugin into the /usr/src/app folder (which I think is the way I am supposed to do this?)

I am wondering if anyone happens to know though, how I can execute grunt watch while also having the verbosity of ./nodebb dev as I am quite new to node and working with this board, so the more output I can get as to what I mess up the better, lol.

As of now, all I was doing was starting up the container like this:

nodebb-dev:
        build: nodebb-dev/NodeBB
        container_name: nodebb_dev
        command: bash -c "grunt" 

I also don't seem to see my plugin in the forum's available plugins after I linked it. I went into my plugin folder, did 'sudo npm link', then I went into /usr/src/app and did 'sudo npm link nodebb-plugin-my-plugin', which did give me some output that didn't look erroneous, so I figured it must have been correct, but it still didn't show up, I tried to run a rebuild just to make sure to no avail. Looking back now, I do see the actual plugin within /usr/src/app/node_modules after linking.

If anyone has any suggestions, or spots anything I might have done incorrectly, I would definitely appreciate the input.
Thanks,
-MH

Hello,
I have begun work on a custom email plugin, and while looking at some others that are available to see how they went about things I noticed that all of the available plugins (at least that I have found so far) already have an entry in the email setup list, regardless of if you have downloaded the associated plugin for that service (ex. Sendgrid, Mailgun, etc).

So my questions is, if I have a custom email plugin, how exactly would I go about making it selectable / usable by the forum? Does it need to be present in the default email list? Is there a way to have my plugin inject itself into that list of providers or is there a way to override that list so that the forum knows not to use the credentials and settings in there, but instead use the ones in the plugin?

The only real switch I have found is the "Use an external email server to send emails", which I would imagine that if it is turned off, that would not be much help either.

If anyone has any insight on how the system works in regards to this and can point me in the right direction, I would appreciate it!

Thanks,
-MH

Hello,
It would be quite helpful if the plugins that were available for download from the admin panel were required to indicate the NodeBB version they were compatible with, a date of when it was last updated, or things of that nature so that quickly at a glance you can see if something is older or not compatible anymore as simply having the plugins current version is not that helpful with nothing to compare that against.

Thanks,
-MH

Oh? Is this not what you see when you click the link? I know it allows you to switch themes on the fly, but the one I was referring to was the one that came up in this link when I first went there. (looks like you have to click it, I don't think it will play the .gifv here on the board it doesn't look like)

https://i.imgur.com/pD3irV8.gifv

Hey all,
I had never used Mongoose before but I know it is used for schema and validation. I was wondering though if anyone knew off chance if it could be added to NodeBB's database without it interfering with how it currently operates? I came across this backend administrative application called ForstAdmin and I was thinking about trying to see if I could add it into my current install. The application itself is made to integrate into an application you already have up and running, but that is under the assumption you are already have Mongoose and are using Express. I might spin up another board just to give it a go and see what happens, lol.

Thanks all,
-MH

Hey there all,
I am just getting my feet wet with this amazing platform but had a quick question. Does anyone know how difficult it would be to add some slight animations upon loading / changing views, or if there are any themes out that already include this? An example of what I am looking for would be best seen here: https://demo.themehouse.com/xf2/themes/ As you click around you will notice some really nice smooth slide in type animations that cascade up/down or in from a side, etc. If anyone could point me in the right direction as to how this might be achieved in NodeBB, I would be most appreciative.

Thank you in advance for your time!
-MH

Edit Nevermind, I actually got it figured out.

@vinipereira

Sorry to necro this, but I was just looking into this repo when I came across this post. I have a wordpress site and I wanted to embed my NodeBB forum into it. I have it embeded, I was just looking for a way to resize the frame automatically when I found this. I have the wordpress side of things setup, I was just trying to see if there were any examples of this forum being in the iframe as opposed to a frame being within a post on the board.

Was anything ever figured out, or were you able to make it work at all with the way you were attempting to do it, here?

Edit : I gave it a few minutes after restarting Nginx and it looks like using the files from Github was my fix, looks to be that everything is working now!

After doing a git clone of the current repo and building with the Dockerfile as opposed to just using the currently available nodebb/docker on docker hub, it looks like those issues went away. It currently isn't displaying anything at all right now, but in the logs I see:

nodebb      | 
nodebb      | Starting NodeBB
nodebb      |   "./nodebb stop" to stop the NodeBB server
nodebb      |   "./nodebb log" to view server output
nodebb      |   "./nodebb help" for more commands
nodebb      | 
nodebb      | NodeBB v1.12.0 Copyright (C) 2013-2014 NodeBB Inc.
nodebb      | This program comes with ABSOLUTELY NO WARRANTY.
nodebb      | This is free software, and you are welcome to redistribute it under certain conditions.
nodebb      | For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
nodebb      | 
nodebb      | Clustering enabled: Spinning up 1 process(es).
nodebb      | 2019-04-04T22:33:50.921Z [4567/22] - info: Initializing NodeBB v1.12.0 https://forum.mysite.dev
nodebb      | 2019-04-04T22:33:54.634Z [4567/22] - info: [socket.io] Restricting access to origin: https://forum.mysite.dev:*
nodebb      | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "includeSubdomains" parameter is deprecated. Use "includeSubDomains" (with a capital D) instead. at node_modules/helmet/index.js:33:28
nodebb      | Thu, 04 Apr 2019 22:33:54 GMT hsts deprecated The "setIf" parameter is deprecated. Refer to the documentation to see how to set the header conditionally. at node_modules/helmet/index.js:33:28
nodebb      | 2019-04-04T22:33:54.961Z [4567/22] - info: Routes added
nodebb      | 2019-04-04T22:33:54.969Z [4567/22] - info: NodeBB Ready
nodebb      | 2019-04-04T22:33:54.976Z [4567/22] - info: Enabling 'trust proxy'
nodebb      | 2019-04-04T22:33:54.986Z [4567/22] - info: NodeBB is now listening on: 0.0.0.0:4567

Before I read this I tried a few more times to wipe out the images I had and repull them from nodebb/docker:latest but now I just get this over and over.

nodebb exited with code 1
nodebb      | module.js:550
nodebb      |     throw err;
nodebb      |     ^
nodebb      | 
nodebb      | Error: Cannot find module '../public/src/utils'
nodebb      |     at Function.Module._resolveFilename (module.js:548:15)
nodebb      |     at Function.Module._load (module.js:475:25)
nodebb      |     at Module.require (module.js:597:17)
nodebb      |     at require (internal/module.js:11:18)
nodebb      |     at Object.<anonymous> (/usr/src/app/src/utils.js:3:18)
nodebb      |     at Module._compile (module.js:653:30)
nodebb      |     at Object.Module._extensions..js (module.js:664:10)
nodebb      |     at Module.load (module.js:566:32)
nodebb      |     at tryModuleLoad (module.js:506:12)
nodebb      |     at Function.Module._load (module.js:498:3)

The time before that it kept saying:

nodebb  | /bin/sh: 1: ./nodebb: not found
nodebb  | /bin/sh: 1: ./nodebb: not found
nodebb  | /bin/sh: 1: ./nodebb: not found
nodebb  | /bin/sh: 1: ./nodebb: not found

I am trying to see if I can figure out how to build it from the github repo perhaps, instead of trying to do it from nodebb/docker repo. Not sure if that might help?

Hey all,
I have been trying to get this working using a Docker-Compose setup and have got it all working (for the most part) minus when I go to the site it only shows Login/Register and NodeBB as seen below:

The Register button works but it is cut-off:

I am not sure if perhaps it has anything to do with the persistent data volumes? When I was just using the http://ServerIP:4567 it worked fine, but then I implemented the Nginx config (using Virtualmin, PHP-FPM, I had tried FCGId first but I seem to recall something somewhere said it was best to use FPM when doing reverse-proxy and virtualhosts. It worked the same either way, though) and am now using a domain, at the same time is when I implemented the named volumes. At first I was just using:

        version: '3.7'

        services:
            nodebb:        
                image: nodebb/docker:latest
                container_name: hpcs_nodebb
                command: bash -c "./nodebb upgrade" # Used once at first because of schema/update needed 
                ports:
                    - "4567:4567"
                depends_on:
                    - mongodb
                volumes:
                    - nodebb_init:/docker-entrypoint-initdb.d/
                    # This was the original way I had them all setup
                    - /home/<user>/devtools/site_files/nodebb/nodebb-config/config.json:/usr/src/app/config.json 
                    # This was how I ended up changing it
                    - nodebb_build:/usr/src/app/build
                    - nodebb_public:/usr/src/app/public

        volumes:
            nodebb_init:
                driver: local
                driver_opts:
                o: bind
                device: /home/<user>/devtools/site_files/nodebb/nodebb-init
            nodebb_build:
                driver: local
                driver_opts:
                o: bind
                device: /home/<user>/devtools/site_files/nodebb/nodebb-data/build
            nodebb_public:
                driver: local
                driver_opts:
                o: bind
                device: /home/<user>/devtools/site_files/nodebb/nodebb-data/public

So I guess my question is, has anyone came across a similar situation or perhaps has any suggestions?
Thanks!
-MH