Buy Hosting

How to play a sound without any input

General Discussion

Suggested Topics

  • T

    Migrating forum from phpBB 3.0.9 to nodeBB 1.14.2, without migrating accounts

    General Discussion
    0 Votes
    1 Posts
    564 Views
    T

    How do I migrate a forum from phpBB 3.0.9 to nodeBB 1.14.2?

    I've found some plugins but I'm pretty sure the version differences will cause major headaches :

    (importer wrong phpBB and nodeBB verions) : https://github.com/akhoury/nodebb-plugin-import (migration exporter ? ) : https://github.com/elelel/nodebb-plugin-import-phpbb (exporter closest version match but not quite : pbpBB 3.1 ) : https://github.com/belst/nodebb-plugin-import-phpbb

    (post migration, convert to markdown ) : https://github.com/elelel/phpbb3bbcode2markdown4nodebb

    Also I'm not quite sure of the procedure?

    Is it remote connect to the phpBB server stop the forum and install the exporter plugin then start the forum and pick up the entire forum as one database file, then stop new nodeBB forum install plugin then start the new forum and import the file?

    it's unclear from what's given.

    I also have some perhaps unusual requirements :

    I'm not interested in migrating accounts, in fact I specifically do not want to migrate accounts. the migration exists only as comfort for those who want to be able to look up the old archived threads (btw I will mark them all as read-only after migration) but effectively we are starting from scratch with new accounts.

    So I'm not interested in migrating the accounts and I'm wondering if that's an issue? do posts necessarily need to be created with an account or is creating posts made by an unattributed user name possible? (if nodeBB attributes posts from the old forum archive to a new forum joinee that's perfectly fine by me, not so if nodeBB refuses that a new joinee use that name under pretext that it's already under use. New users and content must take priority)

    will nodeBB allow this or will it require a account named "archivebot" for example to be "responsible", the "author" of all these posts. I'd prefer if I could at least preserve the author names buit if I can't that's an ok sacrifice.

    Also will nodeBB allow the original dates for the posts? or will all of them be of the date of the migration?

    TLDR: I don't know how to migrate from phpBB 3.0.9 to nodeBB 1.14.2 specifically there doesn't seem to be an upgrade path for those specific version numbers.

  • D

    Why Plugin nodebb-plugin-soundpack-default not play mp3 ?

    General Discussion
    0 Votes
    5 Posts
    2k Views
    PitaJP

    Try ./nodebb build and restarting. Also make sure a soundpack plugin is enabled in the ACP.

  • N

    New installation without port 4567 in URL?

    General Discussion
    0 Votes
    3 Posts
    1k Views
    C

    I would advise using Nginx infront of it.
    You can google NodeBB Nginx Config and you'll have one you can copy/paste.

    Nginx will then be on port 80 and you can close 4567 on your FW.

  • T

    How to clone NodeBB heroku without recreating it.

    General Discussion
    0 Votes
    3 Posts
    1k Views
    julianJ

    I don't understand what you are asking, sorry 😦

  • XiphX

    JWT - it's kinda like sessions but without the sessions

    General Discussion
    0 Votes
    1 Posts
    2k Views
    XiphX

    While browsing the 'net, I found a neat little IETF draft standard called JWT (JSON Web Tokens).

    Basically, the idea is that instead of having sessions on the server and a cookie to match a HTTP request to one of those sessions, one or more claims (i.e. user ID or admin status) are stored in a JSON object which is then signed by the server. (currently through either HMAC, RSA or ECDSA)
    The client then stores this in usually either localStorage or sessionStorage and sends it along in an HTTP header with any request requiring authorization.

    For example:

    client logs in with username "Example" and password "password" server if user and password match, issue a JWT containing the payload { 'userId': 47 } and send it to the client client stores the JWT in sessionStorage (later) client creates a new topic and sends the JWT along in the Authorization HTTP header server validates the signature in the JWT from the Authorization header with their own secret/key and if it's OK, uses the data from the JWT in the processing of the request
    (in this case, the userID of 47 is used as creator of the topic)

    Pros of JWT:

    The server doesn't need to store sessions!
    => less load on the server
    & no shared session store is needed when scaling horizontally as long as all instances share a secret or public/private keypair No cookies => no CSRF!

    Cons:

    XSS becomes more dangerous - any malicious script with access to the client's localStorage or sessionStorage for a site can fully impersonate the user until the token expires or is deletes

    There might be more cons & pros, I am neither good nor experienced enough to fully understand everything 😛

    ("everything" is a lot though, I do have trouble with way less than that 😒 anyway, don't take my words for granted, do your own research, etc. etc. you know the drill 😛 )

    Some links:

    General introduction: http://angular-tips.com/blog/2014/05/json-web-tokens-introduction/ Slightly more detailed introduction with INFOGRAPHICS(ish): https://auth0.com/blog/2014/01/07/angularjs-authentication-with-cookies-vs-token/ Web-based token decoder: http://jwt.io/ Express middleware: https://www.npmjs.com/package/express-jwt
Copyright © 2023 NodeBB | Contributors