Community

DO Droplet Wordpress one-click install? | Pro Install Services?

Technical Support
  • R

    I have installed a Wordpress site on DigitalOcean using their one-click install, and have a few basic questions, all likely very dumb:

    • Into which folder should I place the nodebb files? Home/username folder? Var/www folder? Does it even matter?

    • Does it matter from which folder I am working when I'm copying the install commands listed in the nodebb installation tutorials?

    • I plan on purchasing a subdomain called 'forum' (forum.example.com). How will I separate the Wordpress site from the forum when visitors go to one or the other?

    • I have installed other forums before, but am really struggling with nodebb. Are there any professional services out there (preferably within this community) that could perform this service for me for a fee if I find it's just too hard for me to figure out?

    KowlinK 1 Reply
    0
  • KowlinK

    @ron_jeremy Hi, as you have noticed NodeBB isn't your regular PHP forum, and installation can be a bit tricky at first if you have never worked with Node.JS applications before,

    • Installing NodeBB isnt recommended from /var/www/ since its an whole other port by default. Its the best to run NodeBB from a folder thats easy to access by SSH as example: /home/username/nodebb or ~/nodebb (when logged in as the user)
    • following this tutorial from the official docs, you only need to go into the NodeBB folder when doing npm install --production and onwards.
    • Once you have aquired a domain, you can setup a CNAME in your DNS manager. (A example with my domain is shown below.) With this CNAME you can make a reverse proxy in the apache config. DigitalOcean tutorial
    • You can always look into a hosted NodeBB service from NodeBB them selfs ;), else the NodeBB community can help you out.

    Hope this helps.

    R 1 Reply
    0
  • R

    @Kowlin Thank you very much for your help -- I appreciate it very much.

    I would LOVE to use the nodebb self hosted solution, but we are a non-profit off-road motorcycle club and do not have the money for that. We have fundraisers every year in order to buy equipment required to maintain our trail system, and paying $1200/year for a forum would simply put us in the red.

    I could've easily setup a BBPress or similar forum for us but I just love this forum software and know I'd regret using something else.

    I will use your input and continue plugging away.

    KowlinK 1 Reply
    0
  • KowlinK

    @ron_jeremy Feel free to send me a chat if you need help 😉

    R 1 Reply
    0
  • BriB

    If you guys are really non-profit then there's a hosting option that's $20 a month

    ... Although it's hard to put a price on the satisfaction putting it up yourself, but I'm a nerd 🙂

    R 1 Reply
    2
  • R

    @Kowlin thank you very much for that. The community here is a big reason why I walked away from Discourse.

    1
  • R

    @BDHarrington7 Yes, we are a registered (non-profit) society with the Province of British Columbia. I just assumed nodeBB was not yet offering the $20 non-profit plan because the link on the site's main page does not work. I will have to look into that, but you are right about the satisfaction of doing it myself!

    julianJ 1 Reply
    0
  • julianJ

    @ron_jeremy We do offer the non-profit plan (at the $20/mo price point), although support is not included with that plan, and is billed hourly.

    We'd need any non-profit documentation you can obtain (either provincial or federal) in order to verify eligibility 🙂

    0

Suggested Topics

  • SimosS

    Fresh install freeze after a while

    Technical Support
    0 Votes
    2 Posts
    258 Views
    SimosS

    This is the current situation after a while i'm using it https://imgur.com/a/caC0ju2

  • LethalLuigiL

    Migrating Forums from one server to another

    Technical Support
    0 Votes
    10 Posts
    1269 Views
    LethalLuigiL

    Seems to me like it worked thanks man.

  • Evgeniy OneginE

    non-working keys in ubuntu installing docs

    Technical Support
    0 Votes
    3 Posts
    512 Views
    Evgeniy OneginE

    thank you man but specify in the documentation that the keys can become obsolete for such as I xD although I took the key from here http://keyserver.ubuntu.com/ . I have some problems but more about this later

  • Marija BabovicM

    Installation service

    Technical Support
    0 Votes
    2 Posts
    747 Views
    barisB

    We do offer one-time installations. Send us an email at [email protected].

  • RichGR

    Sharing Windows Server with Nodebb and Wordpress

    Technical Support
    0 Votes
    24 Posts
    11991 Views
    RichGR

    I started off this quest with just a simple problem. To have the ability for users to address my nodebb forum (http://theamericanbulletin.com:8080) as (“http://forum.theamericanbulletin.com”). This simple problem turned into a quest through countless videos and reading ( at least fifty) mindnumbing posts on blogs and other forums. I am running a Windows server ( 2008 ) with IIS to service my Wordpress main site. My NodeBB forum is listening on port 8080. All advice was to work within the framework of Windows and IIS, using 'Rewrite', to route traffic on the Server. After days of frustration, I had to come up with a better plan. One that gets me above proprietary nuances. The only way to do that was to get hold of port 80 myself..my own proxy server.. and what better webserver than Nodejs. With little of a search I came accoss this project.

    https://github.com/nodejitsu/node-http-proxy

    I git cloned the above link. Renamed the new directory to nodeproxy e:\nodeproxy> npm install ( pulls all the needed modules) created a new directory under the new 'nodeproxy' entitled MyProxy Created the MyProxy.js file ( contents below ) Moved my WordPress to listen on port 8081 in IIS Started new proxy server (e:\nodeproxy\myproxy> node myproxy.js ) Done!

    Some notes about the js file. When I first started I used this post as a guideline. It used a routing table... exactly what I was looking for. Although I was not needing to spin-up three test servers, this provided some insight into the power if this little application. I could, if I wanted to.... spin-up as many listeners as I wanted..... listening on whatever, or as many port(s) as I wanted.

    var httpProxy = require("http-proxy"); var url = require("url"); httpProxy.createServer(function(req, res, proxy) { var hostname = req.headers.host.split(":")[0]; var pathname = url.parse(req.url).pathname; // Options for the outgoing proxy request. var options = { host: hostname }; // Routing logic if(hostname == "127.0.0.1") { options.port = 8083; } else if(pathname == "/upload") { options.port = 8082; options.path = "/"; } else { options.port = 8081; } // (add more conditional blocks here) proxy.proxyRequest(req, res, options); }).listen(8080); console.log("Proxy listening on port 8080"); // We simulate the 3 target applications var http = require("http"); http.createServer(function(req, res) { res.end("Request received on 8081"); }).listen(8081); http.createServer(function(req, res) { res.end("Request received on 8082"); }).listen(8082); http.createServer(function(req, res) { res.end("Request received on 8083"); }).listen(8083);

    I modified the above code to tailor it to my routes, but the server kept breaking. The proxy would throw a “socket hang up” when I moved between the Wordpress site and the NodeBB site. The error was not getting caught and the proxy would just break and go back to a system prompt. Another day of research lead me to this post.

    http://www.clock.co.uk/blog/preventing-http-raise-hangup-error-on-destroyed-socket-write-from-crashing-your-nodejs-server

    It was in this post where the idea of wrapping the proxy-server within a domain arose. Perfect! I can pass the error up to the domain and let it dispose of it while the proxy keeps serving ( at least that's how I think it works). Plus the added benefit of having and overlord (parent) to all the potential listeners that could be spun-up to report to. But that is a whole different subject.

    So I added a Domain to the mix and came-up with a working solution. While this only apples to those with 'full' control over their servers, it does add a layer of control over proprietary systems running on your machine, and frees the developer (to a point) from those systems. I do not have to mess with rewrite... or some Apache routine tables. This is 'clean' and simple.

    Please feel free to improve on this concept and tighten this up. There is room for lots of improvement here. Please add to the knowledge.

    Rich

    MyProxy.Js

    var util = require('util'),
    http = require('http'),
    url = require('url'),
    domain = require('domain')
    httpProxy = require('../lib/http-proxy'),
    proxy = httpProxy.createProxyServer({});
    serverDomain = domain.create();
    proxy.on('error', function(err, req, res)
    {
    console.log(err.message);
    });
    serverDomain.run(function () {http.createServer(function(req, res)
    {
    var reqd = domain.create()
    reqd.add(req)
    reqd.add(res)
    // On error dispose of the domain
    reqd.on('error', function (error) {
    console.error('Error', error, req.url)
    reqd.dispose()
    });
    var oUrl = url.parse(req.url);
    if (typeof req.headers !== 'undefined' && req.headers.host.split)
    {
    var hostname = req.headers.host.split(":")[0];
    var pathname = oUrl.pathname;
    switch(hostname)
    {
    case 'forum.theamericanbulletin.com':
    proxy.web(req, res, { target: 'http://localhost:8080' });
    break;
    default:
    proxy.web(req, res, { target: 'http://localhost:8081' });
    };
    console.log(hostname);
    console.log(pathname);
    }
    }).listen(80,function(){
    console.log('proxy listening on port 80');
    });
    });

Copyright © 2023 NodeBB | Contributors