@gotwf
wow
"some kind of superior master ring"
the admins here stuck in the 2000's are really having a weird inferiority complex in terms of docker. Its not a master ring, its not a magic supertool, its just clever, modern technology. Its a way to maintain systems with MUCH less hassle than was needed before. not everyone needs to understand the details of installing a microservice if the person that understands BEST maintains the docker and updates frequently for security and functional updates. If running a nodeBB forum is your lifes purpose, i can understand you enjoy the full install and undertanding how everything works, to the last detail. if its just another web service you are runing among 20 others, you dont give too much of a damn, you just want it to be as easily maintainable and servicable as possible.
The religious war is started by the people hating dockers, the others just want to make their job as productive as possible.
BTW, lets see how quickly somebody gets up a server after a linux distribution change using traditional methods vs. a server thats dockerized
I just renewed one of my wildcards. You indeed need to use DNS and the TXT records need to change every time. You would need to use a script to set the TXT records for auto-renew.
You can fix the counts by running the following query in mongodb for each group that has the wrong member count.
// get number of users
db.objects.count({_key: "group:<replace_with_group_name>:members"});
// update group object
db.objects.update({_key: "group:<replace_with_group_name>"}, {$set: {"memberCount": <replace_with_value_from_previous_query>}});
Breaking change to themes https://github.com/NodeBB/NodeBB/issues/8018
This only affects custom themes on forums that are running on a subfolder. To upgrade the theme to 1.13.0 just remove {config.relative_path} from the files in this commit. https://github.com/NodeBB/nodebb-theme-persona/commit/eb33ae7fa1d59aa1fce77cea988a537e277049b5
djensen47 created this issue in NodeBB/NodeBB
closed
Welcome notification link broken
#8018
0
barisusakli committed to NodeBB/nodebb-theme-persona
https://github.com/NodeBB/NodeBB/issues/8018
Hello
Im a newbie with css so i found this code in the NodeBB Forum
ul.categories [data-cid="1"]::before {
content: "Neuigkeiten";
background: #1e1f33 url(https://i.imgur.com/liB8eUb.png) no-repeat 10px center;
}
ul.categories [data-cid="3"]::before {
content: "Blocks";
background: #1e1f33 url(https://i.imgur.com/eSUaQuV.png) no-repeat 10px center;
}
ul.categories [data-cid="1"]::before, ul.categories [data-cid="3"]::before {
color: #fff;
display: block;
position: relative;
height: 40px;
line-height: 40px;
font-size: 15px;
border-bottom: 1px #0c2b51 solid;
text-align: left;
padding-left: 70px;
font-style: normal;
text-transform: uppercase;
margin-bottom: 20px;
font-family: "Roboto","Helvetica Neue",Helvetica,Arial,sans-serif;
border-radius: 5px;
margin-left: 10px;
}
I am also shown a category above as you can see here
But my question now is how do I get more category sections? In CSS as I see it there are 2 categories defined or do I see it wrong?
can you help me?
MfG Funkel
Dear developers from nodeBB,
I'm a student at the University of Applied Sciences in Regensburg (Germany).
Currently I'm working on my master's thesis, contributing to a research project in the field quantitative software engineering.
By mining the software histories of popular open source projects, we want to get insight about current development practices and challenges. Our main focus here is to understand the co-evolution/change-coupling of software artifacts, especially in the case of database-related changes. Since there are hardly works or established tools considering the co-evolution of schema and the code accessing it, we are investigating this topic.
As nodeBB is one major project in the open-source-community and is also supporting several databases (especially of different types - RDBMS & NoSQL), I have some questions:
We found out that schema related changes were often committed together - across all databases.
So in your case, the changes were done for mongo, postgres and redis in the same commit.
Could you describe the common process of introducing these schema changes or do you have a manual for that?
Is there any tool in use, which supports this process automatically or is it done manually?
How much time is consumed when introducing schema changes in your project?
Which problems occur when changing the schema?
Hopefully you can spend some time to answer these questions, I would appreciate that!
Best regards
Atalay
@julian
Thanks. Yes it works fine. Only one problem.
Seems like
'action:ajaxify.dataLoaded'
is not called when i refresh the page. It is called only if browse the forum. I noticed it now because i use this hook to capture user counters and put them into the stats page.
It wont work also with simple code, outside or inside the document-ready function.
P.S: i just solved using directly
ajaxify.data
global variable. It is just a problem of the hook
@baris yeah it's true, but you can use transaction on a multicluster with only one node, also if with a lot of limitations.
About your command example is a good idea also if it would work only with redis and postgre, with mongodb can be used like a normal batch.
I took a look to postgreSQL module, seems it support transactions, mongodb emulate the same thing with non ACID batch. I prefer to avoid SQL databases but the way data is organized seem more suitable to a relational DB
problem solved. i have to import external script with
require([script], function(name) {
})
It seems that importing scripts in a classic way creates conflicts in nodebb
@baris Done, https://github.com/NodeBB/NodeBB/issues/7931
mattmyne created this issue in NodeBB/NodeBB
open
Notification of new topic in category
#7931
Thank you for the explanation. I will probably use a third-party database (firebase) for payments.
Using firebase, different operations can be done on the client side, without disturbing the main server. I think this is very useful for a smoother user experience.
No built in way, but there is nothing preventing you from writing your plugin to use a config file instead of settings stored in the database.
When your nodebb starts instead of loading your plugin settings from the database you would read it from the file.
I think i will use websockets, thanks for the advice. At moment i'm using callbacks only because can't do different.
Probably async/await will be available from the next version (I've read that too).
/api/categories doesn't load the data via sockets, you can check it on this forum, just check the network tab and you should see the loaded categories.
