Skip to main content

Recherche logiciel de forum la suite

Ma recherche d'un logiciel de Forum continue. Ce toot a relancé ma quête. 

J'ai donc tenté de configurer NodeBB avec Postgresql en backend. Il y a même un guide pour l'installer sous FreeBSD. Malheureusement j'ai un souci encore une fois de dépendance dans npm cette fois qui fait que l'installation plante et ne se finit pas. La documentation n'est vraiment ni à jour ni complète, mais en regardant à droite et à gauche, on trouve son bonheur.

Ensuite, je me suis penché sur une version rouillée de ce type de logiciel et je suis tombé sur Freedit – qui ressemble trop à Reddit pour que je l'utilise, mais celui-ci s'étant installé convenablement, je vais continuer le de tester. Il n'y a pas à tortiller du cul pour chier droit, cargo, c'est quand même une superbe réalisation.  

Il me reste Flarum à tester. J'attends la version deux qui doit apporter en autre un support d'ActivityPub. 

Labels:

Comments

Anonymous said…
Salut,
J'ai beaucoup aimé NoNonsense Forum, malheureusement il n'est plus maintenu.
=> https://github.com/Kroc/NoNonsenseForum
Afin d'éviter l'enfer des dépendances multiples avec npm, ou plus simplement maintenir une version de PHP à jour, je préfère désormais utiliser le moteur de forum présent dans fossil. C'est à la base développé pour SQLite si je ne dis pas de bêtises :
=> https://fossil-scm.org/home/doc/trunk/www/index.wiki
Un seul binaire à tenir à jour, c'est quand même plus pratique.
Je l'héberge depuis un moment maintenant pour ce forum autour d'OpenBSD :
=> https://fr.forum.puffy.cafe/forum
1:40 PM
Ludovic Hirlimann said…
Merci, ceux-ci n'était pas dans l'écho de mon radar :p, j'ai regardé flarum de très près et il me plait beaucoup, je pense que je vais partir sur cette solution.
11:52 AM
Post a Comment

Popular posts from this blog

Firefox OS's story from a mozilla insider not working on the project

  I clearly remember, but can't date it. I was working for Mozilla messaging at the time ( momo ), being the QA lead for Thunderbird. It was at the end of one of the Mozilla All-hands, maybe in 2011 or 2012. At one of the ending keynotes, we were introduced to Boot 2 Gecko. A hack that would let US - Mozilla own the platform to run a mobile browser on. At the time, the iPhone was going strong and Google was trying to catch up with Android. MeeGo had been in development at Nokia for a while but was going nowhere even when Intel tried to help. Blackberry was slowly starting to die. In the Silicon Valley everything was about mobile, mobile, mobile and the emerging South Easter Asian market, where people would skip computers and use smartphones to join the internet revolution. We were struggling with Chrome and the massive investment by Google to take market share. Our Firefox port on Android was having loads of issues. We were denied by Apple's policies to be present on iPhones....
3 comments
Read more

Key signing party at fosdem 2024

I'm organizing a GnuPG key signing party in order to bolster our web of trust , since there is no official ksp this year. I have organized a few in the past using tools like biglumber (website is gone, if someone know of a replacement or where the source code of site is, I might end up running one again) and others tools . I've also run once the KSP at FOSDEM and helped running it a few other times.    === Details below === When, Where   We'll meet in front of the infodesk stand in building K around 12:00 Sunday Feb 4th 2024. I'll have a sing of some sort with KSP and or Key Signing Party . Once enough participants show up we will move outside to proceed with the party. What to Bring Warm cloths as the party will happen outside this year, like in the good old days. I hope it won't rain, but it might. Piece of papers with your fingerprint written on them. Each piece should look like below:  $ gpg --fingerprint 34246C61F792FBCC1F23BFF296BD1F38FEA32B4D pub ...
Post a Comment
Read more

Are mozilla's fork any good?

To answer that question, we first need to understand how complex, writing or maintaining a web browser is.  A "modern" web browser is : a network stack, and html+[1] parser,  and image+[2] decoder, a javascript[3] interpreter compiler, a User's interface, integration with the underlying OS[4], And all the other things I'm currently forgetting.   Of course, all the above point are interacting with one another in different ways. In order for "the web" to work, standards are developed and then implemented in the different browsers, rendering engines. In order to "make" the browser, you need engineers to write and maintain the code, which is probably around 30 Million lines of code[5] for Firefox. Once the code is written, it needs to be compiled [6] and tested [6]. This requires machines that run the operating system the browser ships to (As of this day, mozilla officially ships on Linux, Microslop Windows and MacOS X - community builds for *BSD do ex...
Post a Comment
Read more