nodeBB VS selfhost

> I'm a big fan of https://nodebb.org/

TIL to what shit Netgate moved pfSense forums to. I'm glad you are fine with it, but not only my FullHD monitor is not a smartphone, so I don't need 400% fonts on everything (and post dates on the faaaaar right clearly shows nobody ever even used the forum) and most importantly - search doesn't work. It's not like the previous forum had a good search, but at least it worked.

Bonus point: try to Ctrl+mousewheel on any NodeBB (including the official one).

NodeBB

You said it's based on. This means that there are modifications to the implementation of nodebb. So where is your modifications' source code then? stackfoss/stackfoss is just a single readme file

Obviously forums aren't as popular as they used to be, so this topic might not be of interest to many. For folks that want to run a forum, they'd most certainly go with Discourse (Ruby), Flarum (PHP), Xenforo (PHP), NodeBB (Javascript), Nimforum (Nim) and maybe Casnode (Go)

If you want to make your own app out of custom code that you will actively develop new features for, I think your points are true. But if you just wanted a modern version of the old phpBB forums, there are plenty of almost-turnkey projects/templates you can use. Check out NodeBB for instance. Maybe the barrier for entry is higher in a way, given increased complexity, but you also get more and nicer features "for free". I think it's a wash.

I was looking into actively maintained Rust based forum software similar to NodeBB (Node.js) or Discourse (Ruby on Rails) and Flaskbb (Python).

package: name: nodebb version: 2.5.3 dependencies: runtime: - nodejs environment: contents: packages: - alpine-baselayout - ca-certificates-bundle - nodejs - npm - git pipeline: - uses: fetch with: uri: https://github.com/NodeBB/NodeBB/archive/refs/tags/v${{package.version}}.tar.gz expected-sha256: 92e390d7cda190e7f098833cbbbf03fbe1c50f25653656ad589ae97dc18a7684 strip-components: 0 - runs: | mkdir -p "${{targets.destdir}}/usr/share/nodebb" cd NodeBB-${{package.version}} cp install/package.json . npm install --omit=dev cp -a ./. "${{targets.destdir}}/usr/share/nodebb"

I just started using Pyinfra to wrangle a bunch of servers and it is a breath of fresh air compared to Ansible. I moved all of my server OS installs to Fedora CoreOS which doesn't ship with Python in the OS and since Pyinfra doesn't need Python on the host node I can kick off tasks in bulk to do server things. It is great. I cannot wait to see where the Pyinfra project goes.

On a side note, one of the most hacky things I came up with to get Ansible working on Fedora CoreOS was to bind mount a container rootfs that had python 3 and then symlink it into the right spots. You can of course add Python in with rpm-ostree if you want but I wanted to avoid layering packages at the time. I wasn't proud of it. But it worked.

https://github.com/forem/selfhost/blob/main/playbooks/templa...

This is not the suggested way of deployment by the forem team, nevertheless I found it easier and smother than using the deployment selfhost, however I think it's good to know different approaches and use the one suits you the most, if you don't have time to manage a server I think using a pass like Render does the job, and it's cheaper then Heroku at the time of this post.

Forem Self-Host. You should probably know Forem. But in case you don't, just know that DEV is hosted on it.

I only use Podman for my workloads these days. Docker was always a headache for me on Linux. Podman allows me to quickly do whatever I want with containers and I can use systemd or a simple bash script to easily create services on my workstation or in production with Nomad with https://github.com/hashicorp/nomad-driver-podman

I am super thankful for the team of developers that work on Podman. It has really come a long way since 2.0 and they are very responsive to issues in my experiences. If you are using Linux as your daily driver and you use Containers give Podman a try. Here are some examples of the things I have done with Podman.

https://github.com/forem/selfhost

https://github.com/jdoss/ppngx

https://gist.github.com/jdoss/25f9dac0a616e524f8794a89b7989e...

https://gist.github.com/jdoss/ad87375b776178e9031685b71dbe37...

To automatically generate a TOC, you can use an online tool like the GitHub Wiki TOC generator. I used this tool to create the TOC in Forem’s Selfhost project when I was a developer advocate there.

Hi, everyone; I just tried the tutorial for deploying a self-hosted instance of forem (https://github.com/forem/selfhost) on AWS. A step in the tutorial asks for the creation of an AWS user with Programmatic access called forem-selfhost with the following

We (I work for Forem) have an opensource selfhost installer [0] so you can have total control over your data and community too.

[0] https://github.com/forem/selfhost

If you know what Forem you want to build, please follow the instructions and go live — again, the Self-Host instructions are available here!