@tobiasdossinger The real question here is why you need javascript enabled... I am 95% certain you came here because maybe a theme of yours you have suddenly stopped working, with a cryptic error about turning javascriptEnabled on, yes? In that case, you may want to audit your theme and figure out what exactly needs javascript in your LESS... there really is no reason to that I have come across... although I could be mistaken. In Persona's case, it was the .opacity() mixin, which was not required anymore, as opacity is well supported cross-browser now: https://github.com/NodeBB/nodebb-theme-persona/commit/e14d38b827591c9681a5fcd43ca4b206297eaff5

If I am not mistaken this is the code that redirects the user after register/complete page. Maybe try modifying that?

NodeBB tests require database setup beforehand. I recommend just checking out how NodeBB currently does it with GitHub Actions or how it was done earlier with TravisCI I haven't used GitLab CI much, but I think the services part is pretty similar to GitHub Actions - there are some setup differences (per job variables instead of per service env for example), but I think just adapting the service configuration to GitLab syntax will be better than the bash based install from TravisCI