Buy Hosting

Upvoting/Downvoting

Technical Support

Suggested Topics

  • S

    Custom topic/category icon

    Moved Technical Support
    0 Votes
    4 Posts
    134 Views
    S

    @baris thanks, for some reason a search on Github didn't find it

  • 6

    Needing a NodeBB expert in KY/OH/TN area

    Technical Support
    0 Votes
    4 Posts
    225 Views
    scottalanmillerS

    Avoiding Local Service Providers | SMB IT Journal

    favicon

    (smbitjournal.com)

    Hiring only local triggers what's known as the "church problem" in business. Hiring someone from your church statistically provides the worst work. Psychologists say that this is because of two reasons. The first is just math, you eliminate 99.9999% of the world and try to pull an expert from a tiny pool. The second is that you prioritize locality or membership in a small group over skill, reputation, or ability to do the work. That alone is bad enough, bit picking someone for that reason also tells them that their value to you is because of who they are, what they are a member of, or where they live - which is another way of telling them that doing a good job at a good price isn't important to do. When you make someone believe that their value is already provided simply because of who they are, there is literally no incentive to do a good job and, in fact, a pretty heavy suggestion that they can overcharge and under-deliver and it won't be a problem because they've provided their value already simply in being whoever they are.

  • andxblinkA

    Vanilla install - cannot post/reply > buttons don't seem to register click events

    Technical Support
    0 Votes
    3 Posts
    1k Views
    andxblinkA

    ic. thanks.

  • S

    NodeBB - MultiSite / Shared Users and/or Code

    Technical Support
    0 Votes
    2 Posts
    2k Views
    A

    For 1 I would be inclined to use clustering then reverse proxy the subdomains to categories. Rather than spooling individual instances for each. I've done this at my own site.

    dnb.35hz.co.uk will take you to the electronic category.

    You could then make a few changes to how your homepage/main website looks and do it that way.

    As an additional. Anything you're not sure exists, drop an email to sales [at]nodebb.org and they may be able to create what you need.

  • С

    Heroku setup 0.6.1 error permissions ./nodebb

    Technical Support
    1 Votes
    1 Posts
    1k Views
    С

    Hi guys!

    I have previous 0.5.0-2 version of forum on Heroku. It works fine. When I updated NodeBB to 0.6.1 version it crashed with error. Any ideas?

    2015-04-30T06:31:05.151177+00:00 heroku[web.1]: State changed from crashed to starting
    2015-04-30T06:31:12.946261+00:00 heroku[web.1]: Starting process with command npm start
    2015-04-30T06:31:16.159469+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
    2015-04-30T06:31:16.159494+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
    2015-04-30T06:31:16.817884+00:00 app[web.1]:
    2015-04-30T06:31:16.817890+00:00 app[web.1]: > [email protected] start /app
    2015-04-30T06:31:16.817892+00:00 app[web.1]: > ./nodebb start
    2015-04-30T06:31:16.817893+00:00 app[web.1]:
    2015-04-30T06:31:16.854535+00:00 app[web.1]: sh: 1: ./nodebb: Permission denied
    2015-04-30T06:31:16.873738+00:00 app[web.1]: npm ERR! Linux 3.13.0-49-generic
    2015-04-30T06:31:16.878037+00:00 app[web.1]: npm ERR! code ELIFECYCLE
    2015-04-30T06:31:16.878041+00:00 app[web.1]: npm ERR! [email protected] start: ./nodebb start
    2015-04-30T06:31:16.878043+00:00 app[web.1]: npm ERR! Exit status 126
    2015-04-30T06:31:16.878044+00:00 app[web.1]: npm ERR!
    2015-04-30T06:31:16.878046+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script './nodebb start'.
    2015-04-30T06:31:16.878048+00:00 app[web.1]: npm ERR! This is most likely a problem with the nodebb package,
    2015-04-30T06:31:16.878049+00:00 app[web.1]: npm ERR! not with npm itself.
    2015-04-30T06:31:16.878050+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
    2015-04-30T06:31:16.878052+00:00 app[web.1]: npm ERR! ./nodebb start
    2015-04-30T06:31:16.878054+00:00 app[web.1]: npm ERR! You can get their info via:
    2015-04-30T06:31:16.878693+00:00 app[web.1]: npm ERR! npm owner ls nodebb
    2015-04-30T06:31:16.878696+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
    2015-04-30T06:31:16.889120+00:00 app[web.1]:
    2015-04-30T06:31:16.899848+00:00 app[web.1]: npm ERR! /app/npm-debug.log
    2015-04-30T06:31:16.866363+00:00 app[web.1]:
    2015-04-30T06:31:16.874577+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
    2015-04-30T06:31:16.875101+00:00 app[web.1]: npm ERR! node v0.12.2
    2015-04-30T06:31:16.876089+00:00 app[web.1]: npm ERR! npm v2.7.4
    2015-04-30T06:31:16.897668+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
    2015-04-30T06:31:17.925842+00:00 heroku[web.1]: Process exited with status 1
    2015-04-30T06:31:17.938969+00:00 heroku[web.1]: State changed from starting to crashed

Copyright © 2023 NodeBB | Contributors