is the config of themes store in the DB?

Technical Support

Suggested Topics

  • 0 Votes
    1 Posts

    Not an nginx guru so please bear with me here.

    For simplicity sake let's assume site lives at rather than a subfolder.

    Unless specified otherwise, nginx root dir is /usr/share/nginx/html

    Nodebb nginx configuration docs utilize this when describing setting up a custom error page.

    Nginx is being used exclusively as reverse proxy and not serving any additional sites. I think I read somewhere that under such configuration an explicit default server docroot should not be specified? But even in such cases I think the hard coded default /usr/share/nginx/html still serves up 50x.html error page.

    In absence of a custom error page, nodebb uses nodebb/public/503.html?

    Nginx has been configured for scaling.

    Nginx Pitfalls and Common Mistakes documentation suggest putting doc root inside a location block is bad practice even though it will work.

    Soo... now my question... taking all of above into consideration.. what is proper/correct best practice configuration for a "scaled" nginx nodebb deployment? I know what "could" work. I am curious what "should" be recommended best practice.

    (Yeah, I know I already posted this in a different thread but it was a mistake at the time not to have started a new thread because this is pretty specific w.r.t. best practices configuration rather than "why isn't my stuff isn't working" question. Apologies for that.)

  • Chat UI Persona Theme

    Technical Support
    0 Votes
    3 Posts

    Thanks. Works.

  • 0 Votes
    7 Posts

    @baris said in Changes to theme .tpl files don't show live:

    @Jarko Yes the id field in plugin.json is not used, you need to change the name field in package.json

    ...and that was the issue indeed! Thank you! 💃

  • 0 Votes
    15 Posts

    @frissdiegurke I know. That's why I started it.

  • Theme Question

    Moved Technical Support
    0 Votes
    3 Posts

    I usually make a custom.less file and put all my edits in there with or without the !important tag, as needed. @frissdiegurke 's fix should work as well.