@josef this is the part that should triggered the setup. We don't use docker on manage.nodebb.org.

That's interesting. Maybe you can debug here and see what it returns when running normally vs via pm2.

@[email protected] yes, because you are using NodeBB. It will send the activity to as many people as it possibly can, who have any relation to the topic.

@dawei-JOBS can you give us an overview of how you're attempting to develop a theme on your dockerized deployment?

@julian this is the standard header: [image: 1741778382478-329b1a23-2b16-4ff1-8849-02832b830354-image.png] this is the profile: [image: 1741778352271-fd5d8ced-d978-4330-8c74-9e64ef7a8fb3-image.png] We are missing the logo, the top menu, everything from the header.

Yes the checkmark is there. I have access to the PostgreSQL db, but the model is really twisted, I don't know where to find user data. Table list: legacy_hash legacy_list legacy_object legacy_set legacy_string legacy_zset searchchat searchpost searchtopic session

I'll try to look out for a new case and see if it works on my end too. Thanks!

Hi, I can not setup my smtp email account in NodeBB instance. I checked email credentials in third party apps and it works fine. I suppose it is due to NodeMailer and I can not find place to turn it off tls : { rejectUnauthorized: false } as it said in stackoverflow article. My image is ghcr.io/nodebb/nodebb:latest [image: 1741627582295-62dc7918-6e24-4072-997d-252b30eb9d15-image.png]

@smyther42 It's a mapping of ip addresses to user ids. You can safely delete those too.

@fsf good hackers support the FSF!!!

@fsf Proud Member.

@fsf I totally agree. It's a burden for the user at the very least, damaging to the environment due to the programmed obsolescency and not truly owning what one buys just so that a mega corporation can get even more money. Thanks for sharing alternatives!

Thanks for the heads-up!

@xiaoye said in How to modify the "url" item in config.json?: > I found the config.json in /opt/config, but I encountered the following problems when I edited it. > unusual, nano or vi is normally installed on most versions of linux. odds are you need to install it then if it is not showing up. Debian/Ubuntu base system sudo apt install nano or sudo apt install vim for Redhat based sudo dnf install nano or sudo dnf install vim

@julian Glad to see the issue's been recognized. I know the blind community on Mastodon's been making noise about camel casing hashtags for a long time now.

First one is the suggested way of requiring core files, require.main always references the root of the nodebb folder so you don't have to worry about the require path when moving it around. Meanwhile module.parent references the parent module that required the module so you might have to update the path if you move it into a subfolder for example.