General Discussion

Suggested Topics

  • 0 Votes
    1 Posts

    I want to upload images to S3 or CF,but there isn't plugins I found,so I store the picture locally
    How do I set images to be cleared automatically, or how do I set posts to expire and be cleared,please help me..
    The follows are not working .

  • Multiple Badge for users

    Solved General Discussion
    0 Votes
    3 Posts

    Thansk it worked.

  • How do groups work

    General Discussion
    0 Votes
    3 Posts

    We're quite literal about it. A group is literally just a collection of users. It doesn't afford them anything special beyond a badge.

    However, because it's quite low level, you can do a lot with groups. The privilege system works with groups, so you are able to restrict access to some/all categories based on user groupings.

  • 0 Votes
    10 Posts

    @PitaJ said in How do I upgrade NodeBB without destroying Data & images?:

    @dunlix you could lose installed plugins, but that's unlikely. You certainly wouldn't lose activated plugins.

    Did you lose uploads? What plugins did you lose?

    The only things that it can conceive of that are not in the database are uploads, which you can back up before an upgrade according to the documents you referenced.

  • 0 Votes
    10 Posts

    if you're trying to embed nodebb on another site (i.e., the nodebb instance domain ISN'T your website's domain), you'll have to contend with CSP headers. just a heads up.

    if you have full control of the server on which your nodebb instance is hosted, you could set up a simple reverse proxy with nginx, point it to whatever port nodebb is listening on, and set the headers to something lax that way. config below.

    server { listen localhost:4000 ssl; server_name localhost; ssl_certificate /etc/nginx/ssl/localhost.crt; ssl_certificate_key /etc/nginx/ssl/localhost.key; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers 'AES128+EECDH:AES128+EDH'; ssl_prefer_server_ciphers on; location /forum { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; client_max_body_size 100M; proxy_pass; proxy_redirect off; proxy_intercept_errors on; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_hide_header content-security-policy; proxy_hide_header x-frame-options; add_header content-security-policy "default-src * 'unsafe-eval' 'unsafe-inline' 'self' 'inline' 'http://*.*'"; } }

    you can append whatever domains you'd like to the 3rd to last line (the one that starts with add_header ...), though you shouldn't need to, since the * should whitelist all origins.

    you might ask, “what legitimate use would there be for this?!?”
    in my particular case, it's nice for local development — where your nodebb instance is already running elsewhere but you want to embed it in the site you're developing on your PC.