Conversation
Notices
-
Tried adding some plugins. Who knows if they are working ;-)
- Roland Häder likes this.
-
@gregoriosw only time will tell :P
-
@gregoriosw run this in console (shell access): php ./scripts/upgrade.php that then should make sure that the plugins are well integrated. I recommend you to set $config['db']['schemacheck'] = 'script'; to avoid long load times (as without the schema is being checked always which mostly runs tons of useless queries on your database). With this setting you have to run upgrade.php manually.
-
@gregoriosw Also recommended:
$config['queue']['enabled'] = TRUE;
$config['queue']['daemon'] = TRUE;
$config['queue']['subsystem'] = 'db';
And run:
./scripts/startdaemons.sh
Everytime you update, you have to run ./scripts/stopdaemons.sh
-
@gregoriosw This will greatly improve performance!
-
@roland what do the subsystem settings do? @gregoriosw
-
Hmm, sollte dann nicht noch ein unset von cronish und dem neuen Queue-Subsystem erfolgen?
-
@knuthollund As I know from #StatusNet times, they enable a queue daemon that you have to start in background (with the script I mentioned). If you don't set them, your instance is sending out status notifications immediately and when you have clicked on send button. @morifanty I have seen the cronish things, but no new queue subsystem?
-
"OpportunisticQM" Which is the default Queue Manager if you don't use the longrunning php-Script.
-
@morifanty Okay, then I should disable it, 2 queues for the same thing makes no sense. :)
-
@morifanty Found something: https://blog-notes.jbfavre.org/
-
Abgesehen davon, dass ich kein französisch spreche. ;-)
-
Ich auch nicht. :-)
-
@morifanty @gregoriosw The OpportunisticQM plugin is 'default' and not 'core'. So the correct line is:
unset($config['plugins']['default']['OpportunisticQM']);
-
I'm still running the QM. :)
-
With the queue daemon together?
-
No, haven't configured queue daemon yet.