@darkpollo that I my view defeats in entire purpose of 2fa. If your email was hacked, they'd also have the two factor which is what your are looking to secure in the first place.

Okay, thank you very much. I need your help.

I think you'll see it sooner than later. This is last stage before going gold. A week or two. Or maybe earlier. New releases are always on time.

@Tracy That is amazing! Thank you! I had it ON so that is why I was not seeing any issues. Thanks!

Just to mention, I think Amazon SES blocks sending on port 25 by default. They advise you to use 587 and StartTLS instead. If you have to use port 25 you are required to submit a request for them to allow it for you. I ran into that on helping a Xenforo admin that was wanting to use SES and was insistent that port 25 was what they wanted to use for some unknown reason.

Replying to myself, this is required when using additional locations for static files.

@julian @evanprodromou yes, that is because the plugin processes the follow synchronously 🥸thanks a lot for tweaking nodebb to be compatible and I will see how we can improve that!!!

@julian Probably we just need to upgrade to the latest version of slugify.

@Scott M. Stolz Like a diaspora* dev once said: Threads didn't "implement ActivityPub", they "implemented Mastodon".

I have seen the environment variables for reading the project, but I still need to initialize the project using these environment variables. const envConfMap = { CONFIG: 'config', NODEBB_CONFIG: 'config', NODEBB_URL: 'url', NODEBB_PORT: 'port', NODEBB_ADMIN_USERNAME: 'admin:username', NODEBB_ADMIN_PASSWORD: 'admin:password', NODEBB_ADMIN_EMAIL: 'admin:email', NODEBB_DB: 'database', NODEBB_DB_HOST: 'host', NODEBB_DB_PORT: 'port', NODEBB_DB_USER: 'username', NODEBB_DB_PASSWORD: 'password', NODEBB_DB_NAME: 'database', NODEBB_DB_SSL: 'ssl', }; What is the docker-composer.yml used for startup networks: 1panel-network: external: true services: nodebb: container_name: ${CONTAINER_NAME} deploy: resources: limits: cpus: ${CPUS} memory: ${MEMORY_LIMIT} environment: - TZ=Asia/Shanghai - NODEBB_PORT=4567 - NODEBB_URL=http://127.0.0.1:4567 - NODEBB_ADMIN_EMAIL="[email protected]" - NODEBB_ADMIN_PASSWORD="xxxxxxx" - NODEBB_ADMIN_USERNAME="admin" - NODEBB_DB="postgres" - NODEBB_DB_HOST="127.0.0.1" - NODEBB_DB_NAME="nodebb" - NODEBB_DB_PASSWORD="xxxxxxx" - NODEBB_DB_PORT=5432 - NODEBB_DB_USER="nodebb" image: ghcr.io/nodebb/nodebb:3.12.2 labels: createdBy: Apps networks: - 1panel-network ports: - 4567:4567 restart: always volumes: - ${NODEBB_ROOT_PATH}/node_modules:/usr/src/app/node_modules - ${NODEBB_ROOT_PATH}/build:/usr/src/app/build - ${NODEBB_ROOT_PATH}/uploads:/usr/src/app/public/uploads - ${NODEBB_ROOT_PATH}/config:/opt/config - ${NODEBB_ROOT_PATH}/setup.json:/usr/src/app/setup.json What I hope for is to achieve unmanned installation

@ANONYMOUSKOREAN the Dockerfile is maintained by the community, since we don't use it at NodeBB ourselves. That said, it would be very appreciated if you were to help keep the file updated

Hello friends, I am facing a big issue that is blocking me with Nodebb I tried building NodeBB using the postgress configuration with docker but I am getting this issue. I really don't know what is happening. The .docker/build folder is empty and is not generating nothing. I tried in Windows and in MacOS. The error is the same. Could somebody help me please? This issue is blocking me a lot. PD: I am using the code from github, not a modify version by me. Thanks for your help! nodebb-1 | 2025-01-08T23:33:41.761Z [4567/86] - info: 🎉 NodeBB Ready nodebb-1 | 2025-01-08T23:33:41.762Z [4567/86] - info: 🤝 Enabling 'trust proxy' nodebb-1 | 2025-01-08T23:33:41.763Z [4567/86] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 nodebb-1 | 2025-01-08T23:33:41.763Z [4567/86] - info: 🔗 Canonical URL: http://localhost nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - error: uncaughtException: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | at async open (node:internal/fs/promises:638:25) nodebb-1 | at async readFile (node:internal/fs/promises:1242:14) nodebb-1 | at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19) {"date":"Wed Jan 08 2025 23:33:42 GMT+0000 (Coordinated Universal Time)","error":{"code":"ENOENT","errno":-2,"path":"/usr/src/app/build/public/src/service-worker.js","syscall":"open"},"exception":true,"os":{"loadavg":[0.49,0.49,0.29],"uptime":8437.17},"process":{"argv":["/usr/local/bin/node","/usr/src/app/app.js"],"cwd":"/usr/src/app","execPath":"/usr/local/bin/node","gid":1001,"memoryUsage":{"arrayBuffers":714282,"external":4294458,"heapTotal":94744576,"heapUsed":64312264,"rss":192311296},"pid":86,"uid":1001,"version":"v22.13.0"},"stack":"Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js'\n at async open (node:internal/fs/promises:638:25)\n at async readFile (node:internal/fs/promises:1242:14)\n at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19)","trace":[{"column":25,"file":"node:internal/fs/promises","function":"async open","line":638,"method":null,"native":false},{"column":14,"file":"node:internal/fs/promises","function":"async readFile","line":1242,"method":null,"native":false},{"column":19,"file":"/usr/src/app/src/controllers/service-worker.js","function":"async Controller.generate","line":13,"method":"generate","native":false}]} nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - error: Error: ENOENT: no such file or directory, open '/usr/src/app/build/public/src/service-worker.js' nodebb-1 | at async open (node:internal/fs/promises:638:25) nodebb-1 | at async readFile (node:internal/fs/promises:1242:14) nodebb-1 | at async Controller.generate (/usr/src/app/src/controllers/service-worker.js:13:19) nodebb-1 | 2025-01-08T23:33:42.063Z [4567/86] - info: [app] Shutdown (SIGTERM/SIGINT/SIGQUIT) Initialised. nodebb-1 | 2025-01-08T23:33:42.064Z [4567/86] - info: [app] Web server closed to connections. nodebb-1 | 2025-01-08T23:33:42.071Z [4567/86] - info: [app] Live analytics saved. nodebb-1 | 2025-01-08T23:33:42.072Z [4567/86] - info: [app] Database connection closed. nodebb-1 | 2025-01-08T23:33:42.072Z [4567/86] - info: [app] Shutdown complete. nodebb-1 | [cluster] Child Process (86) has exited (code: 1, signal: null) nodebb-1 | [cluster] Spinning up another process... nodebb-1 | 2025-01-08T23:33:42.201Z [4567/118] - info: Initializing NodeBB v4.0.0-rc.4 http://localhost nodebb-1 | 2025-01-08T23:33:42.684Z [4567/118] - warn: [cache-buster] could not read cache buster ENOENT: no such file or directory, open '/usr/src/app/build/cache-buster' {"code":"ENOENT","errno":-2,"path":"/usr/src/app/build/cache-buster","stack":"Error: ENOENT: no such file or directory, open '/usr/src/app/build/cache-buster'\n at async open (node:internal/fs/promises:638:25)\n at async Object.readFile (node:internal/fs/promises:1242:14)\n at async read (/usr/src/app/src/meta/cacheBuster.js:31:18)\n at async Configs.init (/usr/src/app/src/meta/configs.js:90:17)\n at async start.start (/usr/src/app/src/start.js:19:3)","syscall":"open"} nodebb-1 | 2025-01-08T23:33:42.953Z [4567/118] - info: [socket.io] Restricting access to origin: http://localhost:* nodebb-1 | 2025-01-08T23:33:43.011Z [4567/118] - info: [api] Adding 0 route(s) to `api/v3/plugins` nodebb-1 | 2025-01-08T23:33:43.019Z [4567/118] - info: [router] Routes added nodebb-1 | 2025-01-08T23:33:43.025Z [4567/118] - info: 🎉 NodeBB Ready nodebb-1 | 2025-01-08T23:33:43.026Z [4567/118] - info: 🤝 Enabling 'trust proxy' nodebb-1 | 2025-01-08T23:33:43.027Z [4567/118] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 nodebb-1 | 2025-01-08T23:33:43.027Z [4567/118] - info: 🔗 Canonical URL: http://localhost

I'm not sure Sylvester speaks for everyone (or at least me), and I want to offer my perspective. Personally, I think NodeBB is an amazing product. I've probably installed it 20 times or more across various environments; Ubuntu, RHEL, OpenSUSE, and even created a Docker instance for testing. It’s a fantastic piece of software with a lot of potential. That said, my needs eventually led me in a different direction. I was looking for something more enterprise-ready, more sysadmin-oriented, and a bit more aligned with my development style. The NodeBB team is incredible, and they were very supportive during my time using it. But ultimately, time was a critical factor for me, and I needed a platform that I could build on quickly without hitting too many roadblocks. Since I had an extra $500, I decided to give Invision Board a shot. In just a few days, I was able to build a custom template in about 2 hours, create webhooks, make API calls, and develop a few applications. I even put together a IPS database viewer that interacts with a PHP script to pull database info, convert it to JSON, and display it in a way that allows me to track changes, drill down into data, and generate reports. NodeBB is definitely going places, and I still think it’s a great platform. However, for my specific use case, building features like Clubs, Articles, Blogs, Galleries, Coding Snippets, Wikipedia API integrations, and more, I needed something that offered those tools out of the box or with customization that I can develop with. I spent a week trying to build a custom template in NodeBB and couldn’t get it right, whereas I built one for Invision in just two hours, and I had my additional features up and running within four days. At the end of the day, it comes down to finding the right tool for the job. NodeBB is a fantastic project with a bright future, but Invision was a better fit for what I needed right now. Please don't hate me NodeBB peeps... I will be using this system on my clients (with a subscription so I don't have to host it ) and still give the praise!

@baris Thanks!!

You will have to modify the template for that page which is at https://github.com/NodeBB/nodebb-theme-harmony/blob/main/templates/account/posts.tpl, keep in mind you that page is showing posts and you want to change them to show as topics so you will have to add make changes to the data as well, possibly using the hook filter:account/posts.build

If you are adding a new client side js module, you need to define it in your plugin.json see the quickstart plugin https://github.com/NodeBB/nodebb-plugin-quickstart/blob/master/plugin.json#L23

thanks you so much!

Awesome, thanks for the info!

My changes and the local login privilege only applies to regular logins so should be fine.